Runner.Featured workflow
Application Monitoring and Incident Response
Incident triage starts with context instead of a scramble across monitoring tools.
CONNECTOR
LogfireLogfire connector
Trace requests, search spans, and debug production issues from the workflow.
Runner uses Logfire through a native MCP server for OpenTelemetry trace search, span analysis, and SQL-based observability queries.
Logfire in real workflows
The app page is only useful if it shows how Logfire fits into a real job. This preview is pulled from the live workflow pages that already use the connector.
+New Session
Sessions
Connected appsLogfire
Slack
Linear
LogfireSlackLinear+
Connect a new appWhat would you like to do?
Connected apps
Apps used with Logfire
Why it's better
Logfire is more useful inside a workflow
- Search spans by operation name, error status, and time range.
- Fetch full trace chains to understand distributed call flows.
- Use SQL queries for aggregations like error rates and latency percentiles.
Common pairings
Logfire often works with
Related workflows
Public workflow pages where Logfire is part of the connected stack.
What Runner can do with Logfire
These examples are grounded in the real Runner backend connector definitions and connector guidance docs, not generic marketing filler.
Logfire
Search for error spans
"Find failed spans in the auth service from the last 2 hours."
Production issues surface in the workflow without switching to the observability dashboard.
Logfire
Trace a specific request
"Pull the full trace for this slow request and show me where the latency is."
Runner maps the call chain so you can see where things broke down.
Logfire
Query error rates with SQL
"Run a SQL query to show the error rate by endpoint over the last 24 hours."
Custom observability queries run inside the workflow instead of requiring a dashboard switch.
How this connector is wired in Runner
Provider
Pydantic
Category: Observability.
Backend
Native MCP server
Backed by the Logfire MCP server at `https://logfire-us.pydantic.dev/mcp`, with guidance for trace search, span analysis, and SQL aggregations.
What to expect when Runner uses Logfire
Operational note
Logfire
Always scope queries to a time window — unbounded queries are slow and noisy.
Operational note
Logfire
Start broad with span search, then drill into specific traces.
Testimonials
People using Runner to get more done with Logfire
The value is the same across connectors: real context in, real work out, no copy-paste operating model.
“I got hours back every week. Runner handles the follow-through work that used to sit open across tabs and docs.”
Jordan Rogers
@jordanrogers
“It gives me one place to work across email, calendar, and docs. The time savings are real.”
Lynn Marshall
@lynnmarshall
“I stopped losing deals to slow follow-up. Runner drafts the reply and schedules the next step before I forget.”
Danielle Okafor
@danielleokafor
“Runner connects my CRM, email, and meeting notes so I actually prep for calls instead of winging it.”
Aisha Patel
@aishapatel
“What used to take half a day now takes one focused pass in the morning.”
Rajat Singh
@rajatsingh
“Meeting follow-up used to die in my notebook. Now the recap, emails, and calendar items happen before I leave the room.”
Ethan Park
@ethanpark
“I tried every productivity tool on the market. Runner is the first one that actually finishes work instead of just organizing it.”
James Wright
@jameswright
“Board prep went from a full Sunday to a one-hour Monday morning workflow. The context is already assembled.”
Priya Nair
@priyanair
“The morning briefing workflow changed how I start every day. I see blockers, priority threads, and follow-ups before the first meeting.”
Sarah Kim
@sarahkim
“The double opt-in intro workflow is the single most useful thing I have run this quarter. Warm intros used to take 20 minutes each.”
Marcus Chen
@marcuschen
“Investor updates that used to take a full day now come together in 45 minutes from real data.”
Oliver Reeves
@oliverreeves
Use Logfire inside a real workflow
Download Runner to connect Logfire to the rest of your workflow instead of treating it like another isolated tab.