pico-otel

OpenTelemetry auto-instrumentation for the Pico ecosystem. Install it and your pico-boot app gets distributed tracing, log correlation and Prometheus metrics — wired by entry points, zero integration code.

Install

pip install pico-otel[all]      # or pick: [otlp] [prometheus] [fastapi] [sqlalchemy] [celery] [logging]

What you get

• Tracing: FastAPI requests, SQLAlchemy queries and Celery tasks become spans — whichever libraries are present get instrumented, the rest are skipped silently.
• Metrics: the OTel meter provider exports to prometheus_client's default registry — the same one pico-actuator serves at /actuator/metrics. Installing both = probes + metrics + tracing with zero config.
• Log correlation: trace/span ids injected into log records.

# application.yaml (optional — sensible defaults without it)
otel:
  service_name: my-service
  endpoint: http://otel-collector:4317   # switches export to OTLP
  traces_sample_ratio: 1.0

traces_exporter: auto (OTLP if endpoint is set, console otherwise), otlp, console or none. Setup is idempotent per process.

Documentation

Full docs at dperezcabrera.github.io/pico-otel.

Built for AI-assisted development

pico-otel is part of an ecosystem designed for humans and coding agents building software together. Every package ships AGENTS.md working conventions, an llms.txt machine-readable docs index and documented behaviour pinned by regression tests; pico-testing gives agents a verification loop for their own changes, and releases are gated by the whole ecosystem booting together against real infrastructure. The full story: Built for AI-assisted development.

Install the agent skills for Claude Code or OpenAI Codex:

curl -sL https://raw.githubusercontent.com/dperezcabrera/pico-skills/main/install.sh | bash

The pico-conventions skill teaches the assistant this module's API surface and invariants; /add-component and /add-tests scaffold components and tests that use it.

License

MIT