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

@nitya-signoz may have more insights here

I think things have changed in the helm chart, @Prashant Shahi can you help here, this issue was reported by another user as well.

@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

Cluster name configuration has been moved to global scope to keep consistent with SigNoz and K8s-Infra charts.

@Prashant Shahi I have this architecture setup So in each signoz-client signoz/k8sinfra override-values.yaml i have to set

global.clusterName

Am i correct

Not across each signoz-client, but across each independent k8s infra chart installation and 1 for signoz chart cluster.

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

yes, it looks good, except for the indentation for

presets

section

yeah, its a typo thanks