https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
p
@nitya-signoz may have more insights here
n
I think things have changed in the helm chart, @Prashant Shahi can you help here, this issue was reported by another user as well.
s
@nitya-signoz In Helm 0.12.0 OTEL collector has these values
Copy code
extract:
          metadata:
            - k8s.namespace.name
            - k8s.pod.name
            - k8s.pod.uid
            - k8s.pod.start_time
            - k8s.deployment.name
            - k8s.node.name
do i have to add cluster meta data here
p
Cluster name configuration has been moved to global scope to keep consistent with SigNoz and K8s-Infra charts.
You can set cluster name meta using 
global.clusterName
global configuration.
It is recommended to be set to identify source cluster of the telemetry data (traces, metrics, and logs).
s
@Prashant Shahi I have this architecture setup

https://signoz.io/assets/images/n_collectors-af31d02c2a41866aca6410976c4e4c86.png▾

So in each signoz-client signoz/k8sinfra override-values.yaml i have to set 
global.clusterName
Am i correct
p
Not across each signoz-client, but across each independent k8s infra chart installation and 1 for signoz chart cluster.
s
Copy code
global:
  clusterName: "stage"
k8s-infra:
presets:
  logCollection:
    # whether to enable log collection
    enabled: true
    blacklist:
      # whether to enable blacklisting
      enabled: true
      # which pods to exclude
      pods:
          my-app
@Prashant Shahi is this correct
p
yes, it looks good, except for the indentation for 
presets
section
s
yeah, its a typo thanks
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by