[jira] [Resolved] (CAMEL-24562) Evaluate optional camel-ai-observability-otel-latest module

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-24562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-24562.
---------------------------------
    Resolution: Won't Fix

> Evaluate optional camel-ai-observability-otel-latest module
> -----------------------------------------------------------
>
>                 Key: CAMEL-24562
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24562
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Omar Atie
>            Assignee: Ramu
>            Priority: Major
>
> h2. Background
> Original CAMEL-23861 planning included an optional camel-ai-observability-otel-latest module to align with latest OpenTelemetry GenAI semantic conventions without forcing all users onto bleeding-edge OTel APIs. Phase 1–3 shipped a single camel-ai-observability module tied to camel-telemetry / current OTel conventions.
> h2. Problem
> As OTel GenAI semantic conventions evolve, a single module may either lag behind spec updates or introduce breaking attribute changes for stable users. An optional "latest conventions" module was planned but not delivered.
> h2. Proposed scope
> * Re-evaluate need vs maintaining conventions in camel-ai-observability directly
> * If proceeding: create optional camel-ai-observability-otel-latest module with:
> ** Latest gen_ai.* attribute names / experimental conventions
> ** SPI or classpath selection so users opt in explicitly
> ** Documentation on which module to depend on
> * If not proceeding: close as Won't Do with rationale in CAMEL-23861 comment
> h2. References
> * Parent: CAMEL-23861
> * components/camel-ai/camel-ai-observability
> * OpenTelemetry GenAI semantic conventions (stable vs incubating)
> h2. Acceptance criteria
> * Decision recorded: implement module OR document why single module is sufficient
> * If implemented: optional Maven dependency, no impact when absent
> * Docs explain stable vs latest convention module choice
> * At least one test validates latest module loads and emits expected attributes



--
This message was sent by Atlassian Jira
(v8.20.10#820010)