Issues with Signoz Exceptions View and Slack Alarms in Multiple Namespaces
TLDR Juha reports issues with displaying namespaces in exceptions view and slack alarms. Srikanth confirms improvements are planned but no timetable provided.
Srikanth
Fri, 24 Feb 2023 13:29:30 UTCThere are improvements planned in this regard.
Juha
Fri, 24 Feb 2023 13:31:37 UTCAny insight on possible timetable?
SigNoz Community
Indexed 1061 threads
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
View in App
Juha
Fri, 24 Feb 2023 13:25:17 UTCHello! We are using otel collectors to gather logs, traces and metrics from our applications running in k8s. Exceptions view in Signoz if good, but there’s a small problem. We have same applications running in multiple namespaces (all are autoinstrumented) and it’s impossible to see from which namespace the exception is originated. You have to jump to trace graph in order to view k8s.namespace.name of the exception. Is there something planned which could help on this kind of use case? Another issue is the exception alarm. Alarm message about exception sent using slack webhook does not contain the information about namespace. This is something we would also like to have.