feat: disable custom instrumentation filtering for coded agents #1187
+169
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR removes custom instrumentation filtering for coded agents while maintaining it for low code processes (agent.json). Previously, all agents had filtering applied, which meant coded agents only exported spans with
uipath.custom_instrumentation=True. Now, coded agents export all spans, providing full tracing visibility.Changes
is_low_codeparameter toLlmOpsHttpExporterto distinguish between agent types_should_drop_spanmethod to:agent.json): Whitelist filtering - only spans withuipath.custom_instrumentation=Trueare exportedrun,eval,debug) to detect agent type based on entrypointTesting
TestSpanFilteringByAgentTypewith comprehensive coverage:Impact
🤖 Generated with Claude Code
Development Package
uipath pack --nolockto get the latest dev build from this PR (requires version range).Low Code

Coded