LoginSign Up
← Back to all sparks
S

SigNoz

INFRA · APIS
Velocity6.3

SigNoz extended observability into AI agent toolchains via an MCP plugin while steadily broadening alert routing and access controls.

observabilityalertingmcp-integrationrbacagentic-devtools
◆Current state
SigNoz has been adding alert routing integrations at a steady clip—incident.io, Jira, and Jira Service Management—while tightening enterprise access controls with dashboard-level RBAC in custom roles. The most directional move was shipping as an Agent Skills MCP plugin, making SigNoz data queryable from AI coding environments like Claude Code and Cursor without switching to the SigNoz UI. A forced security migration off v1 alert history endpoints signals legacy debt being cleared.
◆Where it's heading
The product is pulling in two directions simultaneously: deeper enterprise controls (RBAC, PromQL conformance, access policies) and presence in agentic developer toolchains (MCP plugin, agent-friendly APIs). The MCP plugin move is the more architecturally significant—it repositions SigNoz from standalone observability dashboard to context-provider inside AI development loops.
◆Prediction
Expect a richer MCP skill set that lets agents not just read SigNoz data but act on alerts—acknowledging incidents, modifying thresholds, or kicking off runbooks without leaving the coding environment.

◆Recent moves

  1. 3d ago

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

    A forced migration off v1 alert history endpoints by October 15 is a security housekeeping move with a hard deadline—the underlying vulnerability triggered the removal, not a planned deprecation cycle. API integrations relying on those endpoints need updating; it fits the pattern of SigNoz clearing legacy debt as it positions for enterprise use.

    View source ↗
  2. 10d ago

    Dashboards added as a resource in custom roles

    Dashboard permissions in custom roles closes an RBAC gap where dashboards were excluded from fine-grained access control—a real limitation for teams where different engineers own different service dashboards. This lands as SigNoz pushes toward enterprise multi-team deployments.

    View source ↗
  3. 17d ago

    incident.io added as a new alert channel

    The incident.io alert channel integration lets SigNoz alerts feed directly into on-call workflows without extra routing logic, eliminating the manual step of monitoring both systems. It's the third major alert channel addition in this stretch (after Jira and Jira Service Management), signaling a deliberate push to connect SigNoz to wherever incident response already lives.

    View source ↗
  4. 24d ago

    Jira and Jira Service Management Ops added as new alert channels

    Jira and Jira Service Management integrations route SigNoz alert fires to issue creation and resolves to ticket closure automatically. Part of a steady push to reduce the manual layer between observability and incident response tooling.

    View source ↗
  5. 1mo ago

    The SigNoz Plugin for AI Coding Agents

    ⚡ SPARK

    Shipping as an Agent Skills MCP plugin is SigNoz's first move into the agentic developer toolchain, making live observability data queryable from AI coding environments without switching to the SigNoz UI. This is a directional shift: SigNoz as context-provider for agents, not just a standalone observability dashboard.

    View source ↗
  6. 1mo ago

    Full-Text Search in Log Records

    Full-text search across all log fields using the new search() function removes the requirement to know which field a value lives in—practically this means faster triage on novel errors where the schema isn't obvious. A real quality-of-life upgrade for anyone debugging unfamiliar services.

    View source ↗