Skip to content

Fix SignalR server activity name #57118

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

Merged
merged 1 commit into from
Aug 1, 2024
Merged

Conversation

JamesNK
Copy link
Member

@JamesNK JamesNK commented Aug 1, 2024

Changes:

  • Activity.OperationName should be a constant.
  • Activity.DisplayName is what OpenTelemetry uses for the span name. Dynamic value moved there.
  • Minor clean up and test improvements

{
public ActivitySource ActivitySource { get; } = new ActivitySource("Microsoft.AspNetCore.SignalR.Server");
internal const string Name = "Microsoft.AspNetCore.SignalR.Server";
internal const string InvocationIn = $"{Name}.InvocationIn";
Copy link
Member

@BrennanConroy BrennanConroy Aug 1, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a convention or just a name we've landed on?
Would we have an "InvocationOut" in the future, for example if the server calls a client method?

Edit: I just saw we have InvocationOut on the client side PR so I think my guess was right.

@JamesNK JamesNK merged commit 26ee437 into main Aug 1, 2024
26 checks passed
@JamesNK JamesNK deleted the jamesnk/signalr-server-cleanup branch August 1, 2024 22:26
@dotnet-policy-service dotnet-policy-service bot added this to the 9.0-rc1 milestone Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-signalr Includes: SignalR clients and servers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants