Skip to content

Commit 81223d4

Browse files
actions-useractions-user
committed
Sync working groups
1 parent 97ccf66 commit 81223d4

File tree

1 file changed

+77
-77
lines changed

1 file changed

+77
-77
lines changed

‎_data/wg.yaml‎

Lines changed: 77 additions & 77 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,82 @@
11
---
22
working-groups:
3+
- title: "Observability.Next"
4+
board-url: "https://github.com/orgs/quarkusio/projects/42"
5+
short-description: |
6+
Observability.Next is a strategic initiative to modernize the observability stack within the Quarkus framework, aiming to streamline and enhance its ability to monitor and manage distributed systems.
7+
readme: |
8+
<h2>Overview</h2>
9+
<p>Observability.Next is a strategic initiative to modernize the observability stack within the Quarkus framework, aiming to streamline and enhance its ability to monitor and manage distributed systems. Currently, Quarkus (3.16.x) leverages the following components for observability:
10+
Metrics: Managed through <a href="https://micrometer.io/">Micrometer</a>, which supports multiple registries (e.g., Prometheus) to expose application metrics.
11+
Tracing: Handled via the OpenTelemetry (OTEL) SDK, enabling distributed tracing data to be exported to an OTEL collector.
12+
Logging: JBoss's LogManager with a handler forwarding logs with OTEL.</p>
13+
<p>While OpenTelemetry is the industry standard for observability, both in protocol and format, the OTEL SDK has proven challenging to adapt due to its design for agent-based observability. In a framework like Quarkus, more granular and direct control over observability is required to monitor application performance, reliability, and user experience effectively.</p>
14+
<p>Micrometer, the de-facto Java standard for metrics, has recently proposed an enhanced, global approach to observability with the new Observation API. Expanding Micrometer’s role in Quarkus’ observability stack represents an opportunity to simplify implementation and maintenance while preserving compatibility with leading observability tools.</p>
15+
<h2>Objectives</h2>
16+
<p>The Observability.Next initiative seeks to strengthen the integration of Micrometer’s evolving Observability API within Quarkus, aligning it with OpenTelemetry’s protocol standards. Key objectives include:</p>
17+
<ul>
18+
<li>Enhanced Observability Control: Implement a framework-native, Micrometer-centric approach to metrics, traces, and logs, ensuring developers have more refined control over observability components without the limitations of the OTEL SDK.</li>
19+
<li>Broader Metrics and Tracing Compatibility: Continue exposing metrics to various registries, including Prometheus, while maintaining OTEL compatibility for metrics and tracing protocols.
20+
Improved Performance and Reliability: Define and measure performance baselines of the current observability setup and compare them against the next-to-be Micrometer Observation API and OTEL bridge integration to ensure tangible performance and reliability improvements.
21+
Continue to support components using Micrometer metrics API or Open * Telemetry SDK (like Pulsar)</li>
22+
</ul>
23+
<h2>Scope</h2>
24+
<p>Observability.Next will unfold across multiple phases, each handled by specialised working groups. The scope of the initial working group will include:</p>
25+
<ul>
26+
<li>Micrometer Observation API Integration: Introduce and integrate Micrometer’s observability API as a foundational layer</li>
27+
<li>Transformation to OTEL Protocols: Develop a mechanism to translate Micrometer-collected observations into OTEL-compatible metrics, traces, and logs, ensuring smooth interoperability with OTEL-based tools and collectors.</li>
28+
<li>Performance Benchmarking: Establish a performance baseline for Quarkus’ current observability model, comparing it against the new Micrometer-based observability API and OTEL bridge to quantify gains and identify areas for further optimisation.</li>
29+
</ul>
30+
<h2>Expected Outcomes</h2>
31+
<ul>
32+
<li></li>
33+
<li>Improved Developer Experience: More intuitive, refined control over observability for Quarkus developers, reducing complexity and overhead associated with setting up and maintaining observability.</li>
34+
<li>Ecosystem Compatibility: Continued compatibility with existing observability tools such as Prometheus and OTEL collectors, ensuring interoperability with common enterprise monitoring solutions.</li>
35+
<li>Less breakage due to the OTEL SDK</li>
36+
<li>More control over the semantic convention in span and metric tags</li>
37+
<li>Performance Gains: Potentially lower latency and resource consumption in observability operations, contributing to Quarkus’ goal of high-performance, cloud-native applications.</li>
38+
</ul>
39+
<p>Some concrete features we would get at the framework level:</p>
40+
<ul>
41+
<li>Instrument once, plug different frameworks later</li>
42+
<li>Better support of scopes than the one we have today. See:
43+
https://github.com/quarkusio/quarkus/issues/25102 and
44+
https://github.com/quarkusio/quarkus/issues/37140</li>
45+
<li>Auto-generate metrics documentation from source code instrumented with it.</li>
46+
<li>A way to manage semantic conventions</li>
47+
</ul>
48+
<p>Users would benefit from:</p>
49+
<ul>
50+
<li>A way to manage their metrics schemas.</li>
51+
<li>Yet a new framework is available if they want to use it.</li>
52+
</ul>
53+
<hr />
54+
<ul>
55+
<li>
56+
<p>Point of contact: @brunobat
57+
(@<strong>Bruno Baptista</strong> on Zulip)</p>
58+
</li>
59+
<li>
60+
<p>Proposal: https://github.com/quarkusio/quarkus/discussions/44423</p>
61+
</li>
62+
<li>
63+
<p>Related Reading:</p>
64+
<ul>
65+
<li>Micrometer, Observation API and OpenTelemetry roadmap: https://groups.google.com/g/quarkus-dev/c/y5-ojIVsa_M/m/4wquJi4bBQAJ</li>
66+
</ul>
67+
</li>
68+
</ul>
69+
status: on track
70+
lts: false
71+
completed: false
72+
last-activity: 2025-10-21
73+
last-update-date: 2025-09-08
74+
last-update: |
75+
In the last month, the WG - Observability.Next focused on improving the observability stack within the Quarkus framework. The group successfully closed several issues, addressing duplicated OpenTelemetry metrics messages and resolving test failures related to constructor injection in @GrpcService-annotated classes. Additionally, they worked on enhancing documentation regarding the differences in semantic conventions between Micrometer and OpenTelemetry. Notably, a new documentation issue was opened to further refine the precision of this section, reflecting ongoing efforts to clarify and improve resources for users.
76+
77+
(This status update was automatically generated using AI.)
78+
point-of-contact: "@brunobat"
79+
proposal: https://github.com/quarkusio/quarkus/discussions/44423
380
- title: "Spring-Style Testing"
481
board-url: "https://github.com/orgs/quarkusio/projects/60"
582
short-description: |
@@ -487,83 +564,6 @@ working-groups:
487564
488565
(This status update was automatically generated using AI.)
489566
point-of-contact: "@ia3andy (@<strong>Andy Damevin</strong> on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong> on Zulip)"
490-
- title: "Observability.Next"
491-
board-url: "https://github.com/orgs/quarkusio/projects/42"
492-
short-description: |
493-
Observability.Next is a strategic initiative to modernize the observability stack within the Quarkus framework, aiming to streamline and enhance its ability to monitor and manage distributed systems.
494-
readme: |
495-
<h2>Overview</h2>
496-
<p>Observability.Next is a strategic initiative to modernize the observability stack within the Quarkus framework, aiming to streamline and enhance its ability to monitor and manage distributed systems. Currently, Quarkus (3.16.x) leverages the following components for observability:
497-
Metrics: Managed through <a href="https://micrometer.io/">Micrometer</a>, which supports multiple registries (e.g., Prometheus) to expose application metrics.
498-
Tracing: Handled via the OpenTelemetry (OTEL) SDK, enabling distributed tracing data to be exported to an OTEL collector.
499-
Logging: JBoss's LogManager with a handler forwarding logs with OTEL.</p>
500-
<p>While OpenTelemetry is the industry standard for observability, both in protocol and format, the OTEL SDK has proven challenging to adapt due to its design for agent-based observability. In a framework like Quarkus, more granular and direct control over observability is required to monitor application performance, reliability, and user experience effectively.</p>
501-
<p>Micrometer, the de-facto Java standard for metrics, has recently proposed an enhanced, global approach to observability with the new Observation API. Expanding Micrometer’s role in Quarkus’ observability stack represents an opportunity to simplify implementation and maintenance while preserving compatibility with leading observability tools.</p>
502-
<h2>Objectives</h2>
503-
<p>The Observability.Next initiative seeks to strengthen the integration of Micrometer’s evolving Observability API within Quarkus, aligning it with OpenTelemetry’s protocol standards. Key objectives include:</p>
504-
<ul>
505-
<li>Enhanced Observability Control: Implement a framework-native, Micrometer-centric approach to metrics, traces, and logs, ensuring developers have more refined control over observability components without the limitations of the OTEL SDK.</li>
506-
<li>Broader Metrics and Tracing Compatibility: Continue exposing metrics to various registries, including Prometheus, while maintaining OTEL compatibility for metrics and tracing protocols.
507-
Improved Performance and Reliability: Define and measure performance baselines of the current observability setup and compare them against the next-to-be Micrometer Observation API and OTEL bridge integration to ensure tangible performance and reliability improvements.
508-
Continue to support components using Micrometer metrics API or Open * Telemetry SDK (like Pulsar)</li>
509-
</ul>
510-
<h2>Scope</h2>
511-
<p>Observability.Next will unfold across multiple phases, each handled by specialised working groups. The scope of the initial working group will include:</p>
512-
<ul>
513-
<li>Micrometer Observation API Integration: Introduce and integrate Micrometer’s observability API as a foundational layer</li>
514-
<li>Transformation to OTEL Protocols: Develop a mechanism to translate Micrometer-collected observations into OTEL-compatible metrics, traces, and logs, ensuring smooth interoperability with OTEL-based tools and collectors.</li>
515-
<li>Performance Benchmarking: Establish a performance baseline for Quarkus’ current observability model, comparing it against the new Micrometer-based observability API and OTEL bridge to quantify gains and identify areas for further optimisation.</li>
516-
</ul>
517-
<h2>Expected Outcomes</h2>
518-
<ul>
519-
<li></li>
520-
<li>Improved Developer Experience: More intuitive, refined control over observability for Quarkus developers, reducing complexity and overhead associated with setting up and maintaining observability.</li>
521-
<li>Ecosystem Compatibility: Continued compatibility with existing observability tools such as Prometheus and OTEL collectors, ensuring interoperability with common enterprise monitoring solutions.</li>
522-
<li>Less breakage due to the OTEL SDK</li>
523-
<li>More control over the semantic convention in span and metric tags</li>
524-
<li>Performance Gains: Potentially lower latency and resource consumption in observability operations, contributing to Quarkus’ goal of high-performance, cloud-native applications.</li>
525-
</ul>
526-
<p>Some concrete features we would get at the framework level:</p>
527-
<ul>
528-
<li>Instrument once, plug different frameworks later</li>
529-
<li>Better support of scopes than the one we have today. See:
530-
https://github.com/quarkusio/quarkus/issues/25102 and
531-
https://github.com/quarkusio/quarkus/issues/37140</li>
532-
<li>Auto-generate metrics documentation from source code instrumented with it.</li>
533-
<li>A way to manage semantic conventions</li>
534-
</ul>
535-
<p>Users would benefit from:</p>
536-
<ul>
537-
<li>A way to manage their metrics schemas.</li>
538-
<li>Yet a new framework is available if they want to use it.</li>
539-
</ul>
540-
<hr />
541-
<ul>
542-
<li>
543-
<p>Point of contact: @brunobat
544-
(@<strong>Bruno Baptista</strong> on Zulip)</p>
545-
</li>
546-
<li>
547-
<p>Proposal: https://github.com/quarkusio/quarkus/discussions/44423</p>
548-
</li>
549-
<li>
550-
<p>Related Reading:</p>
551-
<ul>
552-
<li>Micrometer, Observation API and OpenTelemetry roadmap: https://groups.google.com/g/quarkus-dev/c/y5-ojIVsa_M/m/4wquJi4bBQAJ</li>
553-
</ul>
554-
</li>
555-
</ul>
556-
status: on track
557-
lts: false
558-
completed: false
559-
last-activity: 2025-09-09
560-
last-update-date: 2025-09-08
561-
last-update: |
562-
In the last month, the WG - Observability.Next focused on improving the observability stack within the Quarkus framework. The group successfully closed several issues, addressing duplicated OpenTelemetry metrics messages and resolving test failures related to constructor injection in @GrpcService-annotated classes. Additionally, they worked on enhancing documentation regarding the differences in semantic conventions between Micrometer and OpenTelemetry. Notably, a new documentation issue was opened to further refine the precision of this section, reflecting ongoing efforts to clarify and improve resources for users.
563-
564-
(This status update was automatically generated using AI.)
565-
point-of-contact: "@brunobat"
566-
proposal: https://github.com/quarkusio/quarkus/discussions/44423
567567
- title: "Quarkus to the CommonHaus Foundation"
568568
board-url: "https://github.com/orgs/quarkusio/projects/38"
569569
short-description: |

0 commit comments

Comments
 (0)