Changelog

Introducing the SigNoz MCP Server

SigNoz now has an MCP server that lets AI assistants like Cursor, VS Code / GitHub Copilot, Claude, Codex, Gemini, and others query your observability data through natural language. You can search logs, query metrics, inspect traces, list alerts, and work with dashboards directly from your AI coding tool.

SigNoz Cloud users can connect to a hosted MCP endpoint directly from Settings, with client-specific setup steps and copyable configuration snippets. Self-hosted users can run the MCP server locally via binary, Docker, or by building from source. You can also explore ready-to-use workflows in the MCP use cases guide.

Better Graph Tooltips

Dashboard chart tooltips can now be pinned using a keyboard shortcut. While hovering over Time Series, Bar, or Histogram panels, users can press the P key to lock the tooltip in place and inspect values without keeping the cursor fixed on the chart.

The tooltip UI now shows clearer Live/Pinned states, contextual hints for available actions, and an Unpin action. The footer has also been polished to better distinguish drilldown and pinning interactions.

Deploy SigNoz Under a Custom URL Path

Self-hosted SigNoz deployments can now be served from a custom URL path, such as https://example.com/signoz/, instead of requiring a root domain. This gives teams more flexibility when deploying SigNoz behind reverse proxies, ingress controllers, or shared internal domains.

The external URL can be configured through the SIGNOZ_GLOBAL_EXTERNAL__URL environment variable, while the default remains unchanged for existing deployments. Once configured, SigNoz uses the custom path consistently across the application without requiring an image rebuild.

Please see the corresponding documentation for more details.