skills.rest
baldimir
baldimirCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

quarkus-observability

Configure structured logging, OpenTelemetry tracing, and Micrometer metrics for Quarkus services.

Updated Mar 31, 2026
Search Tags:#logging#metrics#observability#tracing#quarkus#opentelemetry#mdc
One-click install
npx skills add https://github.com/baldimir/bob-skills --skill quarkus-observability-baldimir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quarkus-observability
Source: https://github.com/baldimir/bob-skills/tree/main/.bob/skills/quarkus-observability
Command: npx skills add https://github.com/baldimir/bob-skills --skill quarkus-observability-baldimir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quarkus and quarkus-flow projects often struggle to implement consistent, production-grade observability. This skill provides a unified pattern to configure structured logging with MDC, distributed tracing via OpenTelemetry, and metrics with Micrometer, enabling reliable debugging and performance insights.

Core Features & Use Cases

  • Structured logging with JSON output and MDC for correlation across services
  • OpenTelemetry tracing integrated with quarkus-flow workflows
  • Metrics exposure via Micrometer/Prometheus for workflow and service health
  • Correlation and request tracing using flow instance IDs to enable end-to-end observability

Quick Start

Configure your Quarkus project to emit JSON logs, enable MDC-based correlation IDs, enable OpenTelemetry tracing, and expose 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 structured JSON logging and MDC in Quarkus?▼

Structured logging in Quarkus uses JSON output and MDC to inject correlation IDs, enabling reliable debugging by linking log entries across distributed services.

How does OpenTelemetry tracing integrate with quarkus-flow workflows?▼

OpenTelemetry tracing integrates with quarkus-flow workflows by using flow instance IDs as correlation and request tracing identifiers to enable end-to-end observability.

Can I use Micrometer and Prometheus for Quarkus metrics collection?▼

Yes, you can expose Prometheus metrics in Quarkus using Micrometer integrations with appropriate Quarkus extensions to monitor workflow and service health.

Do I need specific Quarkus extensions for distributed tracing and metrics?▼

Yes, enabling end-to-end observability requires OpenTelemetry and Micrometer integrations configured through their appropriate Quarkus extensions for tracing and metrics.

What is the best way to achieve end-to-end observability in Quarkus services?▼

The best way to achieve end-to-end observability in Quarkus is combining structured JSON logging, MDC correlation IDs, OpenTelemetry tracing, and Micrometer metrics.

Related Skills

Explore More Software Engineering Skills→
mdproctormdproctor
1

quarkus-observability

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

Community
Advanced
thc1006thc1006
20

service-mesh-observability

Implement full-stack observability for service mesh deployments with metrics, traces, and logs.

Community
Advanced
vecearvecear

structured-logging-standardizer

Enforce a consistent structured log schema with correlation IDs across services.

Community
Advanced
ngxtmngxtm

Tracing Observability

Enables Rust apps to implement structured logging and distributed tracing with the tracing ecosystem.

Community
Intermediate