[CIAPP] Avoid sending non-CIVisibility traces if CIVisibility
mode is enabled.
#3223
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.
This PR adds a new
CiVisibilityTraceInterceptor
that applies the following changes:test
, the entire trace is dropped.test
, we ensure all spans have the CI Visibility origin metadata.Context:
The
CI Visibility
mode can use the same integrations used by theTracing
mode to have the same visibility in end-to-end tests. That means a test span potentially can have HTTP, SQL, Kafka, etc. children spans. This fact may have implications with Billing.We want to ensure that all generated traces are billed by CI App and not by APM if CI Visibility is enabled.