#support

Resolving Cluster Name Issue in AWS EKS with SigNoz

TLDR 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.

Powered by Struct AI
Sep 28, 2023 (2 months ago)
Ajay
Photo of md5-2a438b840cf368cec4a883b3bba5961c
Ajay
06:59 AM
Hello Team
1. I have multiple AWS EKS cluster, sending logs,metrics and traces to signoz cluster using below command
helm install my-release signoz/k8s-infra --set otelCollectorEndpoint=<IP>:4317
2) created a dashboard using below json
https://raw.githubusercontent.com/SigNoz/dashboards/main/k8s-infra-metrics/kubernetes-metrics.json

The cluster name are not populated, but namespace are populated
Image 1 for Hello Team
1. I have multiple AWS EKS cluster, sending logs,metrics and traces to signoz cluster using below command
helm install my-release signoz/k8s-infra  --set otelCollectorEndpoint=<IP>:4317
2)  created a dashboard using below json
<https://raw.githubusercontent.com/SigNoz/dashboards/main/k8s-infra-metrics/kubernetes-metrics.json>

The cluster name are not populated, but namespace are populated
Sep 29, 2023 (2 months ago)
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
01:47 AM
The cluster name will not be available because it doesn’t exist from k8s API response. You should set the clusterName in values.yaml https://github.com/SigNoz/charts/blob/c6897fe95a54df8b80fd163b9d8b5e62d0898514/charts/k8s-infra/values.yaml#L29
Ajay
Photo of md5-2a438b840cf368cec4a883b3bba5961c
Ajay
07:08 AM
Thank you
Prashant
Photo of md5-1899629483c7ab1dccfbee6cc2f637b9
Prashant
04:34 PM
It is recommended to use global.clusterName
04:34
Prashant
04:34 PM
Global configuration would be set for all otel-collectors from both signoz and k8s-infra charts.