observability-bundle

You can correlate FastAPI request logs with distributed traces by injecting OpenTelemetry Trace/Span IDs into structlog JSON logs, enabling Loki↔Tempo derived fields to jump between log queries and trace spans during incident troubleshooting.

Adding Sentry error tracking to FastAPI with OpenTelemetry involves capturing unhandled exceptions and breadcrumbs while coordinating trace sampling between Sentry and OpenTelemetry to maintain consistent distributed tracing visibility.

The best way to enable distributed tracing across httpx and SQLAlchemy in FastAPI is using OpenTelemetry auto-instrumentation, which automatically captures HTTP client calls and database queries within the same request lifecycle trace span context.

Yes, the observability setup requires Prometheus FastAPI metrics alignment to ensure metrics, logs, and traces share the same request lifecycle, eliminating fragmented observability during production incidents.

Yes, you can use Grafana datasource provisioning to configure Loki and Tempo together, including derived fields that enable jumping from Loki log entries directly into corresponding Tempo distributed traces.

You need controlled sampling for OpenTelemetry instrumentation in production FastAPI to manage trace volume and cost, ensuring Sentry error tracking and distributed traces remain coordinated without overwhelming backend storage systems.