Troubleshooting Namespace Issues In Alerts with Otel+Signoz
TLDR Ayushman had a query about retrieving their kubectl pod's namespace in alerts using otel+signoz. Prashant and Srikanth gave steps, but found that Ayushman's applications might not be sending the necessary attributes.
Aug 16, 2023 (3 months ago)
Ayushman
04:24 PMPrashant
05:53 PMYou can use k8s namespace in alerts using the following:
{{ .Labels.k8s_namespace_name }}
Ayushman
06:15 PMI also saw "service_namespace" and that is always "default" where as I have no services in default namespace.
Ayushman
06:16 PMsignoz_calls_total
should i be checking another metric ?Aug 17, 2023 (3 months ago)
Prashant
05:06 AMAug 18, 2023 (3 months ago)
Srikanth
04:04 PM> I also saw āservice_namespaceā and that is always ādefaultā where as I have no services in default namespace.
In both cases, it is most likely your applications are not sending the
k8s.namespace.name
, service.namespace
attributes.SigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Incorporating Namespace Metrics in a JVM Application
Soumyadeep sought advice on displaying namespace metrics in their JVM application, specifically using the java agent. Shivanshu suggested using a kubernetes namespace informer and the `pod_association` function. Ultimately, Soumyadeep resolved the issue by adding a kube manifest, and posed a new query about the "Resolved" alerts on signoz UI.
Issue with Filtering Data by Namespaces in Services Map View
Juha faced issues filtering data by namespaces in Services Map view. Srikanth suggested using `deployment.environment`, but a bug may exist, and an issue was created on GitHub.
SigNoz Production Feedback and Improvement Suggestions
Users shared their SigNoz experiences and feedback. Issues mentioned include memory consumption, UI/UX improvements, connection difficulties, and automation limitations.