Changelog

Jira and Jira Service Management Ops added as new alert channels

You can now route alerts to Jira and Jira Service Management Operations from the Notification Channels tab.

Jira opens an issue when an alert fires and transitions it to done when the alert resolves. A re-fire inside the reopen window (three days by default) reopens the same issue rather than filing a new one, and every notification after the first posts a comment, so the issue carries the alert's full timeline. The issue body holds the rendered alert description and deep links back to SigNoz.

JSM Ops opens an on-call alert on fire and closes it on resolve, deduping re-fires into the same alert. The integration API key is the only thing to configure.

See the Jira Cloud and JSM Ops docs to set either one up.

Containers View in Kubernetes Infrastructure Monitoring

Infrastructure Monitoring's Kubernetes tab now has a Containers view. It breaks each pod down into the app and sidecar containers running inside it, which the Pods view rolls up into a single row. Every container gets its own row showing CPU and memory usage, utilization against its requests and limits, restarts, and health, so you can pinpoint exactly which container in a pod is throttling, leaking memory, or crash-looping.

Each row follows one container across its restarts, so a container's history stays in place even after it crashes and comes back. The view covers Kubernetes containers only. Standalone Docker, Podman, and ECS containers are not shown.

The Containers reference explains every column and chart.

Query traces by instrumentation scope

You can now query traces by instrumentation scope. For example, scope.name, scope.version are available in the Traces  query builder for filtering, grouping and aggregation, useful for things like isolating the spans your own code creates, checking which services are still on an older instrumentation version.