[exporter/datadog]: Add datadog span operation name remapping config option #3444
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 address discussion in #1909 , in which users generally find the converted Datadog Span Operation Name to be unhelpful, verbose, or otherwise difficult to work with. This PR adds a configuration option
span_name_remappings
which allows a user to pass a list of strings formatted<previous_span_operation_name> <updated_span_operation_name>
so that they can convert their datadog span operation name to one they'd prefer.Link to tracking Issue: #1909
Testing: Added unit tests and updated current tests
Documentation: This is documented in our example yaml configuration