implement-observability

Name: implement-observability
Availability: InStock
Author: Firefly Framework

Configure metrics, tracing, health checks, and structured logging for Firefly Framework services.

Updated Aug 23, 2026

Search Tags:#logging #metrics #observability #tracing #opentelemetry #health #reactive

Ready to run

npx skills add https://github.com/fireflyframework/fireflyframework-claude-skills --skill implement-observability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-observability
Source: https://github.com/fireflyframework/fireflyframework-claude-skills/tree/main/skills/implement-observability
Command: npx skills add https://github.com/fireflyframework/fireflyframework-claude-skills --skill implement-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Firefly observability has been fragmented across metrics, tracing, health checks, and logs. This skill unifies auto-configuration and best practices to give you end-to-end visibility with minimal code.

Core Features & Use Cases

Auto-configured metrics with Micrometer and FireflyObservabilityAutoConfiguration
Distributed tracing via OpenTelemetry or Brave bridges with reactive context propagation
Health indicators integrated with HealthMetricsBridge and Kubernetes probes
Structured logging with Logstash-compatible JSON format including trace context
Reactive context propagation enabling MDC and baggage data across Reactor chains
OTLP/Prometheus export configuration with environment-driven behavior
Simple enablement via application properties to control observability features

Quick Start

Enable the observability module in your application properties and start your Firefly service to automatically collect metrics, traces, and health data.

Frequently Asked Questions about implement-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up distributed tracing and metrics for Firefly microservices?▼

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.

How does reactive context propagation work with MDC and tracing in Reactor chains?▼

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.

Do I need Micrometer and a tracing bridge on the classpath to enable observability?▼

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.

Can I export metrics to Prometheus and traces via OTLP from a Firefly application?▼

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.

What is the best way to integrate Kubernetes health probes with structured logging?▼

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.

Why are my OpenTelemetry traces breaking across reactive service boundaries?▼

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.