#support

Updating signoz to 0.17.0 - Adding k8s_cluster_name

TLDR Shravan upgraded to signoz 0.17.0 and noticed k8s_cluster_name as empty. Prashant explained that the cluster name configuration has moved to global scope and suggested setting it using global.clusterName.

9mo

Join the chat

Mar 19, 2023 (9 months ago)

Photo of md5-23d9a9ef8569484aba646a65ec1dc58f

Shravan

07: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

Mar 20, 2023 (9 months ago)

Photo of md5-8df7ce0274b2473ec07403336e48b574

Pranay

02:53 AM

nitya-signoz may have more insights here

Photo of md5-a52b9d6c34f193d9a1ff940024f36f77

nitya-signoz

04:40 AM

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

Shravan

05: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

Photo of md5-1899629483c7ab1dccfbee6cc2f637b9

Prashant

05:38 AM

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

05:39

Prashant

05:39 AM

You can set cluster name meta using global.clusterName global configuration.

05:40

Prashant

05:40 AM

It is recommended to be set to identify source cluster of the telemetry data (traces, metrics, and logs).

Shravan

05:43 AM

Prashant 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

Prashant

05:46 AM

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

Shravan

05: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 is this correct

Prashant

05:50 AM

yes, it looks good, except for the indentation for presets section

Shravan

05:58 AM

yeah, its a typo thanks

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Extracting Custom Fields as Attributes from Log in SigNoz

Harald wants to have custom fields from their body parsed as attributes in the SigNoz logger. They have tried implementing suggestions from nitya-signoz and Prashant, but the issue remains unsolved due to a potential race condition encountered while executing the code. They have provided a full example using Kind for further assistance.

209

5mo

JSON Parsing Issue with Logs in Signoz

Androw had trouble parsing logs with JSON in Signoz. nitya-signoz suggested changes to config, which resolved the issue after Androw added the missing field 'logsCollection'.

7mo

Troubleshooting Signoz Deployment for Log Collection on OCI k8s Cluster

sudhanshu faces issues with log collection despite successful application performance monitoring after deploying Signoz on OCI k8s cluster. Prashant suggests updating paths used for log collection and verifying container logs on the nodes. Log files' paths seem correct, but issues persist. Further solutions are needed.

1mo

Resolving Cluster Name Issue in AWS EKS with SigNoz

Ajay had an issue with SigNoz not populating cluster names in AWS EKS. Srikanth and Prashant suggested settings in the values.yaml and `global.clusterName` respectively.

2mo

Troubleshooting K8s-infra Blacklist Issues

Saad reported a problem where unwanted logs from namespaces were still appearing. Prashant identified a typographical error with 'logCollection' needing to be 'logsCollection'.