SWAT-8663 gateway - add signalfx exporter to traces pipeline to enable correlation #1607
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:
In an Agent -> GW configuration, the traces correlations happen in 2 different places
host.name
correlation occurs at the agent/collector running on the same host as the instrumented app. (no issue here)k8s.pod.uid
occurs at the GW (k8sattributes processor on the agent is configured with passthrough set to true) . However, the GW traces pipelines is not configured with the signalfx exporter, ie: no correlation will be attempted .This PR simply adds the signalfx exporter to the traces pipeline to enable correlation at the GW level.