Tempo

Monitoring & Observability 2 steps

Tempo holds the traces that show where a request actually spent its time and where it died. Antimetal reaches Tempo through your Grafana connection, so it comes online alongside your other Grafana data sources.

01 Capabilities

What Antimetal does with Tempo

  • Follow a trace across service boundaries to the failing span
  • Identify which downstream dependency introduced latency
  • Correlate a slow trace with the logs and metrics from the same moment
  • Distinguish a broad regression from a single slow code path
02 Setup

Connecting Tempo

Tempo is connected through Grafana. Follow the Grafana setup and Antimetal picks up Tempo automatically as one of its data sources.

Prerequisites

  • Tempo configured as a data source in Grafana Cloud or a self-hosted Grafana instance
  1. 01

    Connect Grafana

    Follow the Grafana setup for whichever deployment you run. Antimetal queries the data sources wired into Grafana, so no Tempo-specific credential is needed.

  2. 02

    Make a self-hosted instance reachable

    If Tempo and Grafana run inside your own network, review the self-hosted requirements — Antimetal needs an HTTPS endpoint and a read-only token to query it.

03 Access

Permissions and access

Antimetal reads Tempo through Grafana using the same read-only credential. It issues queries only — no writes or ingestion.

All tenant data is processed in isolated environments. See security and compliance for details.

Need help?

Contact us via Slack or at support@antimetal.com.

Product

  • Agentic Production Engineering

Compliance

All systems normalBuilt in NYC

The autonomous system for production.
SOC 2, GDPR, and HIPAA compliant.