Enhance Synthetic Span Service Representation #635
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.
What does this PR do?
CONFIRM COLD START VAR IS BOOLEAN
Rollout of span naming changes to align serverless product with tracer to create streamlined Service Representation for Serverless
Key Changes:
Change service name to match instance name for all managed services (aws.lambda -> lambda name, etc) (breaking)
Add
span.kind:server
on synthetic spans made via span-inferrerMotivation
Improve Service Map for Serverless. This allows for synthetic spans to have their own service on the map which connects with the inferred spans from the tracer side.
Testing Guidelines
Unit and Integration tests updated accordingly.
Matching the service name to the instance name essentially removes the need for a base_service tag in some instances due to essentially removing service overrides
Additional Notes
Types of Changes
Check all that apply