fix: filter spans with run_type=uipath from LLM Ops export #1133
+18
−4
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
run_type="uipath") from LLM Ops exportrun_typecheck to_should_drop_span()inLlmOpsHttpExporterWhy move from uipath-agents-python?
The
run_type="uipath"filtering was previously in uipath-agents-python span_processor.py#L29, but this approach has timing issues:run_typeattribute is not yet set, so we can't filtertelemetry.filter="drop"Moving the filter to the exporter level in uipath-python:
_should_drop_span)Test plan
run_type="uipath"are not exported to LLM Opsrun_typevalues pass throughtelemetry.filter="drop"filtering still workspytest tests/tracing/test_otel_exporters.py -k TestSpanFiltering🤖 Generated with Claude Code