You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/asciidoc/modules/opentelemetry.adoc
+50Lines changed: 50 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,6 +168,56 @@ Additional integrations are provided via `OtelExtension` implementations. Many o
168
168
**Lifecycle & Lazy Initialization:** Although `OtelModule` must be installed at the very beginning of your application, its extensions are **lazily initialized**. They defer their execution to the application's `onStarting` lifecycle hook. This ensures that all target components provided by other modules (like database connection pools or background schedulers) are fully configured and available in the service registry before the OpenTelemetry extensions attempt to instrument them.
169
169
====
170
170
171
+
==== Apache Camel
172
+
173
+
Seamlessly integrates OpenTelemetry with Apache Camel. By combining Camel's native OpenTelemetry component with Jooby's `OtelModule`, it automatically instruments your Camel routes. It ensures distributed trace contexts remain unbroken whether you are triggering routes synchronously from Jooby HTTP endpoints or consuming messages asynchronously from background brokers (like Kafka, ActiveMQ, or RabbitMQ).
<1> Initializes the global OpenTelemetry SDK. It must be installed at the very beginning of your application setup.
214
+
<2> Registers the Camel module. Because `camel.opentelemetry2.enabled` is set to true, Camel will automatically detect the active tracer provided by `OtelModule` and weave it into your route lifecycle.
215
+
216
+
[NOTE]
217
+
====
218
+
Installation order is critical. `OtelModule` must be installed **before** `CamelModule` so that the global OpenTelemetry SDK is fully initialized before Camel attempts to attach its route interceptors.
219
+
====
220
+
171
221
==== db-scheduler
172
222
173
223
Automatically instruments the `db-scheduler` library. It tracks background task executions, measuring execution durations and recording successes and failures.
0 commit comments