Logfire integration. Find failing routes and the span that threw from your Logfire traces.
Praxen Inc. triages Logfire alerts as they fire, ranks your routes by errors and latency, and follows a bad route down to the span that threw and its exception.
Get started for freeWhat Praxen Inc. 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 issue, 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.
Logfire tools.
The calls Praxen Inc. can make to Logfire when it looks into an issue.
Logfire -
logfireListServicesList the services that sent spans or logs to Logfire in a time window -
logfireSearchSpansSearch Logfire spans and logs by service, name, route, level, exception, or HTTP status -
logfireGetTraceRead one Logfire trace as a parent/child span tree with durations -
logfireRouteSummaryPer-route request counts, error rates, and p50/p95 latency from Logfire -
logfireQueryRun a read-only SQL query against a Logfire project's records and metrics tables
Common questions.
Does Praxen Inc. replace Logfire?
No. Your Logfire setup stays where it is. Praxen Inc. connects to it and adds the triage, root cause and fixes on top.