LoginSign Up
← Back to all sparks
S

SigNoz

INFRA · APIS
Velocity6.3

SigNoz is rebuilding its surfaces so agents can drive them, not just humans.

opentelemetryagent-nativedashboardskubernetespromql-compatibilityintegrations
◆Current state
SigNoz is in a broad platform-hardening phase: dashboards rebuilt on the CNCF Perses schema, PromQL brought into conformance with Prometheus, Infrastructure Monitoring rebuilt around Kubernetes investigation, and an integration catalog expanding almost weekly. GCP metrics now land next to the rest of a team's telemetry with pre-built dashboards rather than requiring a trip to Cloud Monitoring. The v1 alert history endpoints are being removed over a security issue, with a documented v2 migration path.
◆Where it's heading
Two threads run through the quarter. The first is compatibility as a migration argument — matching Prometheus semantics exactly and adopting an open dashboard specification both lower the cost of moving to SigNoz from whatever is already installed. The second is agent-readiness: the dashboard rebuild explicitly targets structured, token-light agent edits, and Noz keeps picking up context handling, so the operator SigNoz designs for is increasingly not a person.
◆Prediction
Expect the schema-first treatment to spread to the other configurable surfaces, with alerts and saved views the obvious candidates, and the onboarding catalog to keep growing at its weekly clip. The v1 alert history endpoints should disappear within a release or two.

◆Recent moves

  1. 7d ago

    Metrics Support for GCP Integration

    GCP metrics with pre-built dashboards close one of the remaining cloud gaps, letting a debugging session stay in SigNoz instead of bouncing to Cloud Monitoring. The twelve new onboarding sources — Open WebUI, Langflow, Cohere, and DSPy among them — show the catalog now reaching AI infrastructure alongside conventional middleware.

    View source ↗
  2. 14d ago

    ⚠️ Action required (API users) - migrate off the v1 alert history endpoints

    Removing the v1 alert history endpoints over a security vulnerability is forced work, but the v2 equivalents return the same data with authentication unchanged, so the migration is mechanical. The Infrastructure Monitoring rebuild shipping alongside it is the larger change, extending query-builder search across the whole Kubernetes investigation flow.

    View source ↗
  3. 21d ago

    A Revamped Dashboard Experience for Humans and Agents

    ⚡ SPARK

    The dashboard rebuild is where SigNoz's agent thesis becomes concrete: adopting the CNCF Perses schema gives agents a validated structure to edit against instead of freeform JSON. The human-facing additions arrive in the same release, which is precisely the argument the release title makes.

    View source ↗
  4. 28d ago

    PromQL conformance with the Prometheus specification

    Anchoring regex matchers is a breaking change that can silently alter the results of existing queries, and it is the price of being a genuine Prometheus drop-in rather than an approximation of one. The nameless selector and vector matching fixes remove a class of queries that previously returned empty results with no explanation.

    View source ↗
  5. 1mo ago

    Data export: timeseries from all explorers, download in the Trace View

    Timeseries export across all explorers and CSV or JSONL trace downloads let data leave SigNoz for analysis elsewhere, which matters for teams carrying reporting or archival obligations. The organization-scoping fix for alert rules is the more serious item sitting underneath.

    View source ↗
  6. 1mo ago

    More Onboarding Integrations

    Six more onboarding sources continue the weekly catalog expansion, while the Kubernetes navigation rework and per-mount disk usage feed the same Infrastructure Monitoring push that culminated in the August rebuild. The Noz fixes around context attachment are small but point at the assistant being wired into page state.

    View source ↗