Loki

#What Antimetal does with Loki

• Search logs with LogQL across the window around an alert
• Pull the error and stack trace behind a failure signature
• Compare log volume and content before and after a deploy
• Tie log lines back to the trace and metric series they belong to

#Connecting Loki

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

Prerequisites

• Loki configured as a data source in Grafana Cloud or a self-hosted Grafana instance

1. Connect Grafana

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

2. Make a self-hosted instance reachable

   If Loki 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.

#Permissions and access

Antimetal reads Loki 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.