Add OpenTelemetry Tracing to Your App with Claude
OpenTelemetry has great docs but a steep setup curve — SDK init, auto-instrumentation packages, exporter config, span naming conventions. Claude knows all of this and can wire it up in one session.
Add OpenTelemetry tracing to this Express.js API. Instrument all HTTP routes,
database queries via Knex, and outbound HTTP calls via axios.
Export traces to an OTLP endpoint configured via environment variables.
Use meaningful span names and add custom attributes for user ID and tenant ID.
Claude picks the right auto-instrumentation packages for your stack, sets up the tracer provider correctly, and adds custom spans for business-critical operations you want to measure. It also knows to propagate trace context across service boundaries via W3C TraceContext headers.
# Laravel / PHP
Add OpenTelemetry tracing to this Laravel app using the open-telemetry/opentelemetry-php SDK.
Instrument Eloquent queries, Redis calls, and outbound Guzzle requests.
Export to a Jaeger collector at OTEL_EXPORTER_OTLP_ENDPOINT.
# Python / FastAPI
Instrument this FastAPI application with OpenTelemetry.
Use opentelemetry-instrumentation-fastapi and opentelemetry-instrumentation-sqlalchemy.
Add a custom span for the payment processing flow in app/services/payments.py.
Observability is the difference between guessing and knowing — let Claude set it up in one session.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.