Connecting Grafana

Optional observability context — logs, metrics, and alerts related to the ticket.

What you need

Your Grafana MCP server's endpoint URL
Optionally, a service account token — leave it blank if the server is only reachable from inside your own network and has no auth in front of it

What this actually queries

When a fix attempt runs, this connector asks the Grafana MCP server for whatever it can find related to the ticket's summary — recent logs, metrics, and firing alerts. It's a Model Context Protocol client, not a Grafana API integration, so it works with whatever tools your MCP server advertises rather than a fixed set of dashboards.

This is additive only. A ticket resolves the same way with or without Grafana connected — if the server is unreachable or a query fails, that shows up as a note in the gathered context, never as a failed fix attempt.

Set it up

Connectors → Add connector → Grafana
Enter the MCP endpoint, and paste the service account token if your server requires one
Click Test connection — it shows the server name and the tools it advertises