quarkus-observability
CommunitySeamless tracing, logging, and metrics for Quarkus.
System Documentation
What problem does it solve?
Quarkus and quarkus-flow observability often require cohesive configuration across structured logging, MDC-based correlation, distributed tracing, and metrics to enable effective debugging and performance insight. This guide helps you configure and use these observability primitives in a unified pattern.
Core Features & Use Cases
- Structured logging with JSON output and MDC-based correlation IDs to enable log correlation across services.
- OpenTelemetry tracing integration to create and propagate traces across Quarkus/quarkus-flow workflows for end-to-end visibility.
- Micrometer/Prometheus metrics exposure with built-in workflow metrics to monitor system health and performance.
- Correlation between flow instance IDs and traces via MDC attributes and header propagation.
- Use Case: In a multi-service flow, trace a user request from API gateway through backend services.
Quick Start
Use the Quarkus observability pattern to enable structured logging, tracing, and metrics in your application by turning on JSON logs, configuring the OTLP endpoint, and enabling Prometheus metrics.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: quarkus-observability Download link: https://github.com/mdproctor/claude-skills/archive/main.zip#quarkus-observability Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.