quarkus-observability

Configure structured logging, tracing, and metrics for Quarkus applications.

1|5|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/mdproctor/claude-skills --skill quarkus-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quarkus-observability
Source: https://github.com/mdproctor/claude-skills/tree/main/quarkus-observability
Command: npx skills add https://github.com/mdproctor/claude-skills --skill quarkus-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about quarkus-observability

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

FAQPage Schema
How do I configure OpenTelemetry tracing and Prometheus metrics in Quarkus?

To configure observability in Quarkus, enable JSON logging, set the OTLP endpoint for OpenTelemetry tracing, and activate Micrometer Prometheus integration to expose metrics for monitoring system health and performance.

How does MDC-based correlation work for Quarkus structured logging?

MDC propagation in Quarkus correlates flow instance IDs with traces by passing MDC attributes and header metadata across services. This ensures log entries and OpenTelemetry traces share matching correlation IDs for unified debugging.

Can I use Micrometer and Prometheus to monitor quarkus-flow workflows?

Yes, Quarkus observability integrates Micrometer with Prometheus to expose built-in workflow metrics. This monitors system health and performance across development, test, and production environments for quarkus-flow applications.

What is needed to propagate trace context across Quarkus services?

Propagating trace context requires enabling OpenTelemetry and configuring proper header metadata. The setup links MDC attributes with flow instance IDs, ensuring distributed traces continue across Quarkus service boundaries.

Does Quarkus observability support distributed tracing for multi-service flows?

Yes, Quarkus observability supports distributed tracing for multi-service flows via OpenTelemetry integration. It propagates traces across Quarkus and quarkus-flow workflows, providing end-to-end visibility from API gateways through backend services.