fix: add trace settings to filter spans before export #26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cristipufu
force-pushed
the
fix/add_trace_settings
branch
2 times, most recently
from
66c6d0f to
a77f01e
Compare
cristipufu
force-pushed
the
fix/add_trace_settings
branch
from
a77f01e to
74ae729
Compare
This was referenced Jan 25, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This PR adds a filtering mechanism for OpenTelemetry spans before they are exported, allowing users to selectively control which spans are sent to exporters. The changes introduce a new
UiPathTraceSettingsclass with an optionalspan_filtercallback, update the trace processors to apply this filter, and bump the package version from 0.1.10 to 0.2.0.