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
We need the ability to filter traces by build/app version for both internal and external agents.
This is critical when an agent’s source changes and users want to understand how a specific version affected agent behavior, compare regressions, or validate improvements.
Proposed Approach
Internal agents:
Use the build-version from builds to tag and filter traces.
External agents:
Introduce an explicit configuration that allows users to define and attach an application version to traces.
This keeps version-based trace analysis consistent across internal and external agents.
This discussion was converted from issue #280 on February 12, 2026 10:56.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
We need the ability to filter traces by build/app version for both internal and external agents.
This is critical when an agent’s source changes and users want to understand how a specific version affected agent behavior, compare regressions, or validate improvements.
Proposed Approach
Internal agents:
External agents:
This keeps version-based trace analysis consistent across internal and external agents.
Beta Was this translation helpful? Give feedback.
All reactions