observability-instrumentation

To add OpenTelemetry tracing to microservices APIs and background jobs, instrument endpoints and asynchronous workers to capture telemetry. This applies end-to-end tracing across inbound requests, outbound calls, and key domain operations without requiring unnecessary refactors.

The best way to enforce low-cardinality metrics and structured logs across services is to apply consistent instrumentation patterns. This ensures metrics labels remain low-cardinality and logs are structured with correlation IDs while preventing secrets from being logged.

Yes, you can propagate trace context safely across external integrations and redact PII. The instrumentation applies safe trace propagation across outbound calls and enforces PII redaction within structured logs aligned with OpenTelemetry patterns.

To verify telemetry exports and configure health checks, instrument your services and check local export paths. This setup implements health and readiness checks that accurately reflect real dependencies alongside your observability dashboards.