Logfire. Query traces, metrics, and logs from Pydantic Logfire.
Connect your Pydantic Logfire project to let agents query traces, explore metrics, and search structured logs, and to have its alerts reach Polylane the moment they fire. Agents can analyze your OpenTelemetry data to troubleshoot issues and understand application behavior.
Join the waitlistWhat 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.
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.
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.
Agents map your services
Every thread can discover which services report to the project and how each route is behaving right now.
Agents investigate
Investigations move from route summaries to individual spans to full trace trees, inside a bounded time window.
The tools agents get.
What an agent can do with Logfire mid-investigation. Every call lands in the thread transcript, cited.
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
Questions.
Is Polylane an AI SRE for Logfire?
It's what most people mean by the term: agents that read your Logfire metrics, logs and traces during investigations and triage its alerts the moment they fire. Alongside every other provider in your workspace, they investigate issues and fix what they can. We call it self-operating software rather than an AI SRE: the point is that your software looks after itself, not that a bot joins the on-call rotation.
Does Polylane replace Logfire?
No. Your Logfire setup stays exactly where it is. Polylane connects to it, uses it during investigations and adds the triage, root cause and fixes on top.