[Chapter 09 - MicroProfile Telemetry 2.1] Updating chapter 08 for MicroProfile Telemetry 2.1#67
Open
ttelang wants to merge 5 commits into
Open
[Chapter 09 - MicroProfile Telemetry 2.1] Updating chapter 08 for MicroProfile Telemetry 2.1#67ttelang wants to merge 5 commits into
ttelang wants to merge 5 commits into
Conversation
Updated sections on telemetry data exporting, metrics, and logs. Added new content for MicroProfile Telemetry 2.1 features.
- Clarified OpenTelemetry and MicroProfile Telemetry Integration. - Fixing grammatical & styling issues to ensure adherence to Eclipse Foundation Writing Style Guide throughout this chapter.
ttelang
changed the title
Emily-Jiang
reviewed
Apr 27, 2026
Emily-Jiang
requested changes
Apr 27, 2026
- Replace Telemetry 1.1 dependency with MicroProfile 7.1 BOM + OpenTelemetry API 1.48.0 - Remove outdated Jaeger docker run; add LGTM stack setup section with port table, Grafana data source config, and per-signal verification steps - Add Meter/LongCounter instrumentation to match actual PaymentService code - Add otel.metrics.exporter and otel.logs.exporter to config (all three signals) - Update PaymentService example to use makeCurrent(), setStatus(), addEvent(), recordException() as implemented in code/chapter09 - Remove duplicate paragraphs and redundant section - Fix "Graphana Tempo" typo and unclosed string literal in code snippet
Contributor
Author
|
@Emily-Jiang - As adviced, I have now updated the chapter to use lgtm to view Metrics, Traces and logs. Please review and merge this chapter content. |
fmhwong
reviewed
Jun 9, 2026
| |Record structured application log events correlated with traces | ||
| |=== | ||
|
|
||
| Because MicroProfile Telemetry is vendor-neutral, you can switch between observability backends (Jaeger, Grafana Tempo, Zipkin, commercial APM tools) without changing application code. |
There was a problem hiding this comment.
Jaeger, Tempo and Zipkin are all tracing backends. Since we mentioned logs, traces and metrics. We should mention observability backends that accept all 3 signals. For example, Grafana Cloud, Grafana LGTM, or Datadog, etc.
fmhwong
reviewed
Jun 9, 2026
| <6> `recordException` captures the exception stack trace inside the span for trace-based debugging. | ||
| <7> Always end the span in `finally` to guarantee trace completeness even on exceptions. | ||
|
|
||
| == Types of Telemetry |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated sections on telemetry data exporting, metrics, and logs.
Added new content for MicroProfile Telemetry 2.1 features.