SkillMaxx / Monitoring / Logfire

Logfire logo

Logfire

Add Logfire observability to Python applications with auto-instrumentation for FastAPI, httpx, asyncpg, SQLAlchemy, and more

PluginMonitoringSource ↗Claude marketplace ↗

Stars
★ 143
Last updated
Hands-on tests
Tested ✓ in 2 of 5

Install

Tested ✓✓ Verified from docsOfficial docs ↗
/plugin install logfire@claude-plugins-official

Tested ✓ on 2026-10-16: installed and loaded in a throwaway sandbox with no credentials.

Log excerpt
Installing plugin "logfire@claude-plugins-official"...✔ Successfully installed plugin: logfire@claude-plugins-official (scope: user)
$ verify:
  ❯ logfire@claude-plugins-official
    Status: ✔ enabled
1 run, latest 2026-10-16

logfire

Add Logfire observability to Python applications.

Features

  • /logfire:connect - connect Claude's MCP client and optionally set up native session telemetry
  • /logfire:status - check MCP access, native telemetry configuration, and delivery evidence separately
  • /logfire:disconnect - stop native Claude telemetry while keeping MCP and skills
  • logfire-coding-agents skill - configure Claude/Codex recording or coding-agent Gateway routing
  • logfire-frontend skill - set up browser errors, Web Vitals, and session replays
  • logfire-gateway skill - route application model calls through Pydantic AI Gateway
  • /instrument - detect frameworks and add Logfire instrumentation
  • logfire-setup skill - authenticate, inspect the repository, and route to the right setup workflow
  • logfire-infrastructure skill - monitor hosts, containers, Kubernetes, databases, and cloud infrastructure
  • logfire-evals skill - add dataset-based evaluations for AI and agent behavior
  • /debug - investigate errors using Logfire traces via MCP
  • /query - query traces, logs, and metrics interactively or add query capabilities to code
  • logfire-ui skill - open Logfire project pages, live views, traces, and Explore filters directly in Codex
  • SKILL.md with core Logfire patterns (configure, instrument, structured logging, AI/LLM instrumentation)
  • MCP server for querying Logfire data

Query vs UI Routing

The Codex Logfire plugin uses one primary workflow per request:

User intent Route
Analyze, query, count, summarize, compare, or find root cause Use logfire-query and return analysis in chat.
Open, show in browser, live view, Explore, Logfire UI, or give a link Use logfire-ui and open or return a Logfire URL without querying first.
Ambiguous prompts like "show recent errors" or "view logs" Ask whether the user wants a UI view or query analysis.
Explicit combined prompts like "analyze this and give me a link" Do the requested query work, then provide the relevant Logfire link.

For UI requests that omit the organization/project, the agent should resolve the current project through Logfire MCP auth/current-project metadata before asking the user. Environment values such as LOGFIRE_BASE_URL, LOGFIRE_URL, and exporter config identify the platform/API base only; they are not enough to infer the target organization/project.

Read the full README on GitHub →

Preview from the source repo. Images are removed.

Similar alternatives

Honeycomb

Plugin · Monitoring

Skills, agents, and workflows for Honeycomb observability — query patterns, production investigations, SLOs,...

★ 27Tested ✓ in 2

Dynatrace

Plugin · Monitoring

Dynatrace observability skills: DQL query patterns, application and infrastructure monitoring, log analysis,...

★ 164Tested ✓ in 2

Axiom

Plugin · Monitoring

Official Axiom observability integration (MCP Server + Skills). Query logs and metrics with APL, run...

★ 16Tested ✓ in 2

Datadog

Plugin · Monitoring

Use Datadog directly in Claude Code through a preconfigured Datadog MCP server. Query logs, metrics, traces,...

★ 1Tested ✓ in 3

↑↓ to move · Enter to open · Esc to close