SigNoz vs Vercel

SigNoz's recent stream pairs an AI-side play with steady core-product work. The headline move is the SigNoz MCP Server: a hosted endpoint (plus a self-host option) that lets Cursor, GitHub Copilot, Claude, Codex, and Gemini search logs, query metrics, inspect traces, and work with alerts and dashboards through natural language. Around it, the core product keeps polishing: trace details have been rebuilt with funnel-aware navigation, Query Builder v5 lands in Infrastructure Monitoring, dashboards gain per-panel cursor-sync modes, ingestion-limit alerts are now one click with a default name, and native Azure monitoring covers VMs, App Service, AKS, Container Apps, Functions, SQL Database, and Blob Storage. Service accounts replace the legacy API Keys page, with RBAC and a clearer invite-expiry UI.

SigNoz is positioning itself in the 'AI-queryable observability' lane — open-source Datadog with an MCP front door. The MCP server makes the data queryable by every major coding assistant simultaneously, which is the right move for a tool whose primary buyer is the engineer at the IDE. The parallel work — Azure breadth, service accounts, faster query builder — looks like ground prep so that the MCP-mediated queries land on a faster, broader, more access-controlled backend.

Expect the MCP server to gain write actions (silence alert, acknowledge incident, snapshot a query) so AI assistants move from read-only investigators to incident-response participants. Cloud breadth is likely to keep growing — GCP-native monitoring would be the obvious next addition after Azure.