You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (Jira)" <ji...@apache.org> on 2026/07/24 07:13:00 UTC

[jira] [Resolved] (CAMEL-24221) Camel JBang MCP Server - Add camel_runtime_ai_trace tool for AI exchange tracing

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

Andrea Cosentino resolved CAMEL-24221.
--------------------------------------
    Resolution: Fixed

> Camel JBang MCP Server - Add camel_runtime_ai_trace tool for AI exchange tracing
> --------------------------------------------------------------------------------
>
>                 Key: CAMEL-24221
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24221
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Andrea Cosentino
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 4.22.0
>
>
> Add a new MCP tool that traces AI-specific exchange flow in running Camel routes. While camel_runtime_trace exists for general tracing, it does not surface AI-specific metadata.
> Scope:
> - New tool: camel_runtime_ai_trace
> - Captures: token usage per LLM call, latency per AI component, model ID used, guardrail outcomes, streaming chunk counts
> - Input: route ID or pattern filter, optional time window
> - Output: structured trace with AI-specific metrics per exchange step
> - Leverages existing Camel exchange headers (CamelAwsBedrockTokenCount, etc.)
> Location: dsl/camel-jbang/camel-jbang-mcp/



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