implement-observability

Distributed tracing and metrics for Firefly microservices are set up by wiring Micrometer and OpenTelemetry bridges with FireflyObservabilityAutoConfiguration, providing end-to-end observability across service boundaries with minimal code.

Reactive context propagation enables automatic MDC and baggage data transfer across Reactor chains, ensuring trace context remains intact during asynchronous operations. It requires optional configuration to maintain distributed tracing continuity in reactive code.

Yes, enabling end-to-end observability requires Micrometer on the classpath and a tracing bridge such as OpenTelemetry or Brave. Health indicators configuration is also needed, with reactive context propagation being optional for Reactor-based applications.

Yes, Firefly observability supports OTLP and Prometheus export configuration driven by environment variables. You can control these export behaviors and observability features through simple application properties.

The best way to integrate Kubernetes health probes with structured logging is using HealthMetricsBridge to wire health indicators, while outputting Logstash-compatible JSON logs that include trace context for unified production visibility.

Traces break across reactive service boundaries without reactive context propagation configured. Enabling automatic MDC and trace propagation in Reactor-based code ensures distributed tracing continuity and baggage data transfer across asynchronous chains.