Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AzureMonitorExporter] Favor RPC over HTTP spans #378

Merged
merged 1 commit into from
Jan 12, 2021

Conversation

pcwiese
Copy link
Owner

@pcwiese pcwiese commented Jan 12, 2021

Description:
Some instrumentation libraries are sending an RPC server span with both RPC and HTTP semantic attributes present (dotnet). In these cases we should favor the RPC attributes when figuring the Span type.

Testing:
E2E tests performed.

Some instrumentation libraries are sending an RPC server span with both RPC and HTTP semantic attributes present (dotnet). In these cases we should favor the RPC attributes when figuring the  Span type.
@pcwiese pcwiese requested a review from vangarp January 12, 2021 18:56
@pcwiese pcwiese merged this pull request into skyman/master Jan 12, 2021
@pcwiese pcwiese deleted the pwiese/prioritize-rpc-over-http branch January 12, 2021 19:17
pcwiese added a commit that referenced this pull request Jan 12, 2021
Some instrumentation libraries are sending an RPC server span with both RPC and HTTP semantic attributes present (dotnet). In these cases we should favor the RPC attributes when figuring the  Span type.
pcwiese added a commit that referenced this pull request Jan 14, 2021
Some instrumentation libraries are sending an RPC server span with both RPC and HTTP semantic attributes present (dotnet). In these cases we should favor the RPC attributes when figuring the  Span type.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant