LoginSign Up
← Back to all sparks
S

SigNoz

INFRA · APIS
Velocity6.3

SigNoz becomes agent-native with a plugin for Claude Code, Cursor, and Copilot

agent-integrationobservabilitykubernetesaccess-controlalert-routingonboarding-integrations
◆Current state
SigNoz is an open-source observability platform that has spent the last six weeks on two parallel tracks: broadening integrations (GCP metrics, Jira, incident.io, 22+ new data sources) and hardening enterprise access controls (ingestion key-scoped RBAC, custom billing permissions). The standout move is shipping as a plugin for the Agent Skills open format — making SigNoz the first OSS observability tool to formally embed itself in the AI coding workflow layer across Claude Code, Cursor, GitHub Copilot, Devin, Gemini CLI, and others.
◆Where it's heading
SigNoz is positioning as the default observability choice for AI-native engineering teams. The agent plugin places it inside the agentic dev loop where agents can both read telemetry and act on it — cost investigation, instrumentation changes — rather than surfacing data passively to human dashboards. The Kubernetes monitoring overhaul and fine-grained RBAC are the enterprise hardening tracks needed to compete with Datadog and New Relic for production workloads beyond the OSS audience.
◆Prediction
The next move is likely deeper agent autonomy — having the SigNoz plugin not just surface telemetry but apply instrumentation and configuration changes directly, building on the cost-investigation skill they've already seeded in Noz. The ingestion key RBAC coming out of beta for Cloud and Enterprise is the near-term release most clearly telegraphed.

◆Recent moves

  1. 7d ago

    incident.io added as a new alert channel

    Adding incident.io as an alert channel closes a gap for on-call-heavy teams — SigNoz now routes directly into the workflow where pages get actioned, without a manual forwarding step. The Billing permissions addition in custom roles is the quieter but meaningful piece: finance and ops staff can now view usage and invoices without getting admin-level access.

    View source ↗
  2. 14d ago

    Jira and Jira Service Management Ops added as new alert channels

    The Containers view is the most useful addition here — Kubernetes pods often run multiple containers, and having per-container CPU/memory/restart rows surfaces throttling and crash-loops that pod-level rollups obscure. Jira and JSM Ops alert routing fills out SigNoz's incident management integrations, completing a set that now covers PagerDuty, incident.io, Jira, and JSM in the same release cycle.

    View source ↗
  3. 21d ago

    The SigNoz Plugin for AI Coding Agents

    ⚡ SPARK

    The agent plugin is the most directional move in SigNoz's recent history — shipping via the Agent Skills open format formally embeds SigNoz into the AI coding workflow where agents can both reason about telemetry and act on it. This shifts SigNoz's identity from a standalone observability dashboard to infrastructure for the agentic development loop.

    View source ↗
  4. 28d ago

    Full-Text Search in Log Records

    Full-text search via the `search()` function solves a real friction point in log exploration: knowing which field a value lives in before you can filter for it. This is most useful during incident response when field structure is uncertain — scan broadly first, then narrow to a specific field filter once oriented.

    View source ↗
  5. 1mo ago

    Metrics Support for GCP Integration

    GCP metrics with pre-built dashboards moves SigNoz from 'can work with GCP' to 'works with GCP out of the box.' Pre-built dashboards eliminate the setup overhead that otherwise makes cloud-provider metric integration a one-time investment that rarely gets maintained — a practical blocker for GCP-heavy teams evaluating SigNoz against Datadog's native GCP integration.

    View source ↗
  6. 1mo ago

    Kubernetes infra monitoring rebuilt, per-key telemetry RBAC in beta

    Scoping telemetry access by ingestion key ID is the most significant addition here — it lets teams enforce data boundaries within a shared SigNoz instance, which has been a blocker for multi-team enterprise deployments. The Kubernetes infra rebuild (query-builder search, richer tables, redesigned entity pages) brings the monitoring surface closer to standalone K8s observability tools like Lens or Pixie.

    View source ↗