-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
EventCounters event is written to an EventListener that never subscribed to it #31500
Comments
Do you know if there any EventPipe/ETW session that subscribed to System.Runtime? EventCounters are not session-aware so if an out-of-proc session has been started it is possible for EventListeners to start receiving payloads from EventSource that another session started. |
I'm using ApplicationInsights in the same app so maybe. |
AFAIK AppInsights does have an EventListener that turns on |
That issue seems to be about refresh rates of event counters and subscibing to the same event source with different set of parameters. I don't see how it correlates with event being sent to the wrong eventlistener. |
Ah, sorry I should've clarified myself. To be more precise your issue is related to filtering on EventListener side - EventListener doesn't have the ability to filter on For example, this EventSource will start spewing events out to any EventListener instance if there is a session that enables it:
The culprit is here: https://github.com/dotnet/coreclr/blob/master/src/System.Private.CoreLib/shared/System/Diagnostics/Tracing/TraceLogging/TraceLoggingEventSource.cs#L684 I thought we had an issue tracking this but I couldn't find any, so I'll use this issue as tracking this work item. Thanks! |
Duplicate to #31927 |
We have an EventListener listener where the subscription is guarded by a trait that System.Runtime event source doesn't have (
TraitName = "AzureEventSource"
)Somehow without subscribing to System.Runtime event source we get EventCounters events with the following stack:
EventData:
Runtime version: 3.0.0
cc @noahfalk
The text was updated successfully, but these errors were encountered: