https://signoz.io logo
Title
s

Shravan Kgl

03/19/2023, 7:23 PM
I have upgraded signoz from 0.14.0 to 0.17.0 In logs i see k8s_cluster_name as empty k8s_cluster_name was not there in 0.14.0
p

Pranay

03/20/2023, 2:53 AM
@nitya-signoz may have more insights here
n

nitya-signoz

03/20/2023, 4:40 AM
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

Shravan Kgl

03/20/2023, 5:14 AM
@nitya-signoz In Helm 0.12.0 OTEL collector has these values
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

Prashant Shahi

03/20/2023, 5:38 AM
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

Shravan Kgl

03/20/2023, 5:43 AM
@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

Prashant Shahi

03/20/2023, 5:46 AM
Not across each signoz-client, but across each independent k8s infra chart installation and 1 for signoz chart cluster.
s

Shravan Kgl

03/20/2023, 5:48 AM
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

Prashant Shahi

03/20/2023, 5:50 AM
yes, it looks good, except for the indentation for
presets
section
s

Shravan Kgl

03/20/2023, 5:58 AM
yeah, its a typo thanks