exporter/elasticexporter: translate semantic conventions to Elastic destination fields #671
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:
Translate
http.*
,net.peer.*
, anddb.*
semantic conventions to Elastic's equivalentdestination.*
fields. This is necessary to add external (non-instrumented) destination services to the service map.Testing:
I've added unit tests, and performed manual testing with a Jaeger-instrumented test application:
Test code