Omar Atie created CAMEL-24561:
---------------------------------
Summary: Integrate GenAI observability with Micrometer
ObservationRegistry
Key: CAMEL-24561
URL: https://issues.apache.org/jira/browse/CAMEL-24561
Project: Camel
Issue Type: New Feature
Reporter: Omar Atie
h2. Background
Original CAMEL-23861 design mentioned Micrometer Observation API integration
for parity with Spring Boot / Spring AI observability patterns. Current
implementation uses direct OpenTelemetry spans (camel-telemetry) and optional
Micrometer MeterRegistry counters/timers via GenAiMicrometerSupport — not
ObservationRegistry / Observation API.
h2. Problem
Applications using camel-micrometer-observability or Spring Boot's
ObservationRegistry do not get GenAI observations through the standard
Micrometer Observation pipeline. Dual instrumentation paths may be harder to
unify in Spring Boot deployments.
h2. Proposed scope
* Evaluate integration with io.micrometer.observation.ObservationRegistry
* Consider reuse of patterns from camel-micrometer-observability module
* Define whether GenAI observations become Observation instances with gen_ai.*
low-cardinality keys
* Optional dependency — must not force ObservationRegistry on all AI users
* Document when to use direct OTel path vs Observation path
* Tests with ObservationRegistry mock or test implementation
h2. References
* Parent: CAMEL-23861
* components/camel-ai/camel-ai-observability (GenAiMicrometerSupport)
* Original JIRA CAMEL-23861 design notes
* camel-micrometer-observability module (if present on main)
h2. Acceptance criteria
* Design decision documented (adopt, defer, or hybrid)
* If implemented: GenAI operations register Observation when
ObservationRegistry is available
* Backward compatible with current OTel + MeterRegistry path
* Tests prove Observation lifecycle (start/stop/error) for at least one producer
* No mandatory new dependency for users who only want OTel spans
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
