Get started Dashboard
← All integrations
Logfire

Logfire integration: connect Logfire to Polylane

Connect Pydantic Logfire traces, logs and metrics to Polylane with project and organization keys. Follow exception spans to explain failing request paths.

Get started for free

What Polylane does with Logfire.

Route health in one question

Agents rank your routes by request count, error rate, and p95 latency straight from the spans your services already send to Logfire, so "what is failing" gets a numbered answer.

From an error rate to the failing span

Agents pull the requests behind a bad route and open one trace as a parent/child tree, naming the child span that threw and what its exception said.

Your traces mid-investigation

Agents search spans and logs by service, route, level, and status while they work an incident, and every finding is cited back to the query behind it.

SQL when the question is unusual

For anything the curated tools do not cover, agents run bounded read-only SQL over your Logfire records and metrics, with the engine's own error messages guiding the next attempt.

How it works.

01

Connect

Paste a project API key and an organization API key, each created with Read-only access and Manage project and org. Credentials are encrypted before they're stored, and agents only ever query with the project key.

02

Checks take the watch

Request error rate, volume, and p95 latency run as checks on a cadence, project-wide and per service; agents flag results that stray from normal.

03

Agents map your services

Every thread can discover which services report to the project and how each route is behaving right now.

04

Agents investigate

Investigations move from route summaries to individual spans to full trace trees, inside a bounded time window.

Tools for the investigation.

What Polylane can do with Logfire while it investigates. Every call is recorded in the transcript.

logfireListServices

List the services that sent spans or logs to Logfire in a time window

logfireSearchSpans

Search Logfire spans and logs by service, name, route, level, exception, or HTTP status

logfireGetTrace

Read one Logfire trace as a parent/child span tree with durations

logfireRouteSummary

Per-route request counts, error rates, and p50/p95 latency from Logfire

logfireQuery

Run a read-only SQL query against a Logfire project's records and metrics tables

Common questions.

Does Polylane replace Logfire?

No. Your Logfire setup stays where it is. Polylane connects to it and adds the triage, root cause and fixes on top.

Connect it once. Then get back to shipping.