Spec: services dependencies granularity Messaging#655
Merged
AlexanderWert merged 3 commits intoelastic:mainfrom Jul 18, 2022
Merged
Spec: services dependencies granularity Messaging#655AlexanderWert merged 3 commits intoelastic:mainfrom
AlexanderWert merged 3 commits intoelastic:mainfrom
Conversation
9 tasks
AlexanderWert
approved these changes
Jul 5, 2022
jackshirazi
approved these changes
Jul 5, 2022
trentm
approved these changes
Jul 5, 2022
basepi
approved these changes
Jul 11, 2022
gregkalapos
approved these changes
Jul 11, 2022
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Part of #646 for messaging spans.
Specify which value of
service.target.namewe should use or the following span subtypes/instrumentations:azurequeue: queue nameazureservicebus: queue or topic nameFor AWS, Azure and other cloud-based services, we DO NOT use the region name as a fallback as we do for some services, the general rule is to always use the queue or topic name if available.
CODEOWNERS)To auto-merge the PR, add
/schedule YYYY-MM-DDto the PR description.