Skip to main content
The Tempo integration gives sureops agents access to your Tempo instance for distributed trace search, individual trace retrieval, and TraceQL metric queries — used during diagnosis to identify where in a request path a failure or latency spike originates.
Unlike Prometheus and Loki, Tempo should be connected even if Grafana is already configured. The Grafana MCP server does not expose Tempo’s full TraceQL surface (trace search, get-trace, and traceql-metrics). Connect Tempo directly to give agents the full distributed tracing capability.

​
What this integration enables

  • Trace search — agents search for traces matching service name, span attributes, error status, and time range
  • Individual trace retrieval — agents pull the complete trace waterfall for a specific trace ID to identify the failing span
  • TraceQL metric queries — agents use Tempo’s traceql_metrics API to aggregate trace data into rate, error, and duration metrics
  • Multi-tenant support — if you run a multi-tenant Tempo, configure the Tenant ID to scope queries to the correct org

​
Prerequisites

  • An environment selected in the top-right context switcher — Settings → Environment → Integrations is scoped to that environment and stays disabled until one is selected
  • A running Tempo instance reachable from your network
  • The tempo-mcp server running and reachable from sureops
Integration connections are per-environment. Connecting Tempo here only applies to the environment that was selected in the context switcher at the time — it does not carry over to your other environments. Repeat this connect flow for each environment that needs Tempo.

​
Setup

1

Stand up tempo-mcp

Tempo 2.9 and later ships a built-in MCP server at /api/mcp — if you’re on Tempo 2.9+, you can likely point sureops directly at that endpoint without deploying a separate proxy. If you’re using the sureops demo environment, tempo-mcp is already provisioned in-cluster — you can skip this step.On an older Tempo version, deploy a standalone MCP server that speaks TraceQL against your Tempo instance’s base URL.
2

Connect in sureops

In sureops, go to Settings → Environment → Integrations and click Connect next to Tempo.Fill in:
  • MCP Server Endpoint — the URL of your running tempo-mcp server (e.g. https://tempo-mcp.internal.company.com/mcp)
  • Authentication Method — Bearer Token, API Key, or Basic Auth, matching how your tempo-mcp deployment expects inbound requests to be authenticated
  • Token — labeled Bearer Token, API Key, or Password depending on the method you selected above
Click Save & Connect.
3

Configure Tenant ID (after connecting, if needed)

Once connected, reopen the Tempo integration from Settings → Environment → Integrations. If you run a multi-tenant Tempo, a Settings section appears below the connection status with a Tenant ID field — set it there, not on the connect form. When set, it’s sent as the X-Scope-OrgID header. There’s no system default — single-tenant is just an example value, not something to type in unless it’s genuinely your tenant ID. Leave it blank for single-tenant Tempo.

​
Required credentials

Fields collected when you connect the integration: Field configured afterward, via the integration’s Settings section once connected:

​
Common errors

​
Official documentation