Croway opened a new pull request, #2111:
URL: https://github.com/apache/camel-spring-boot/pull/2111

   ## Description
   
   [CAMEL-27133](https://issues.apache.org/jira/browse/CAMEL-27133), the Spring 
Boot side of [CAMEL-27131](https://issues.apache.org/jira/browse/CAMEL-27131) 
(apache/camel#30291 and #30339):
   
   - `camel-ai-observability-starter` depended on `camel-ai-observability-api` 
only, so adding it recorded no GenAI span or metric ("camel-ai-observability is 
not on the classpath"). It now brings `camel-ai-observability`.
   - The new options of CAMEL-27131 are exposed: `camel.aiobservability.level` 
(`basic`, `detailed` or `full`), `camel.aiobservability.content-max-length` and 
`camel.aiobservability.defer-to-framework`. As `enabled` since #2106, they are 
handed to Camel as override properties under the `camel.aiObservability.*` 
keys, so the AI producers see them on every thread; a key set directly under 
`camel.aiObservability.*` wins over the relaxed binding, as in Camel Main.
   
   GenAI observability stays opt-in: `camel-observability-services-starter` 
does not include this starter, as `camel-observability-services` does not 
include `camel-ai-observability` (apache/camel#30339). The starter page says to 
add it.
   
   The catalog entry and the starter page are regenerated (the catalog takes 
the description and label of `camel-ai-observability` now that the starter 
brings it).
   
   ## Tests
   
   All 15 tests of the starter pass against the Camel snapshot of today 
(4.24.0-20261118.091006): new `AiObservabilityAutoConfigurationOptionsTest` 
(binding of the new options and hand-over to Camel), and unit tests for the 
defaults, relaxed and canonical keys, the visibility of the options from 
another thread, and the presence of the implementation.
   
   _Claude Code on behalf of Croway_
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to