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.
Sep 28, 2023 (2 months ago)
Ajay
06:59 AM1. 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
01:47 AMAjay
07:08 AMPrashant
04:34 PMglobal.clusterName
Prashant
04:34 PMSigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Updating signoz to 0.17.0 - Adding k8s_cluster_name
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`.
Error Installing K8s-Infra Chart for SigNoz on EKS Cluster
Emmanuel encountered an installation error for K8s-Infra chart while setting up SigNoz on their EKS cluster. They found a workaround using otel-collector-k8s.
Deploying SigNoz in AKS Production Cluster with Sample Application
Koushik asks about using SigNoz in an AKS production cluster and wants a sample app. Prashant provides instructions for setting up SigNoz in AKS and suggests HotROD and other sample applications for testing.