Logfire
MCPLogfire is OpenTelemetry-native observability from the Pydantic team. Antimetal queries its traces, logs, and metrics to follow a request to the point it failed.
#What Antimetal does with Logfire
- Query OpenTelemetry traces, logs, and metrics
- Inspect spans to find where time or correctness was lost
- Find application errors and their surrounding context
- Correlate a regression with a recent deploy
#Connecting Logfire
-
Open Integrations in the Antimetal dashboard
Go to Integrations in the Antimetal dashboard and find Logfire.
-
Authorize Antimetal in Logfire
Click Connect and follow the prompt. Depending on the tool this is either an OAuth handoff or a read-only credential you generate in Logfire and paste into Antimetal.
-
Confirm the connection
Once Logfire shows as connected, Antimetal begins pulling from it during investigations. No further configuration is required.
#Permissions and access
Antimetal connects over MCP with read-only access and performs no write operations. The exact scopes depend on the credential you issue in the vendor tool — grant read access only.
All tenant data is processed in isolated environments. See security and compliance for details.
Contact us via Slack or at support@antimetal.com.
Related integrations
Track application errors to their source.
Distributed tracing, telemetry queries, alerts, and dashboards.
Dashboards, alerting, Prometheus, Loki, OnCall, and incidents.
