You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2018. It is now read-only.
We want to add support for events via Microsoft.Framework.Notification to various components in Hosting that can be consumed in process by diagnostic tools.
To start with we want to include data/events with known tooling experiences built around them. This isn't a complete list, but includes things we can start on.
This seems redundant, you can already put a data gathering middleware at the start of the pipeline (possibly via IStartupFilter) to get this kind of information.
Same argument could be made for the logging that is there at the moment. Leveraging Event Notifications means we can tap in in a much more consistent way and when you have multiple instrumentation providers all playing in the same sandpit, its not like you are going to end up with a bunch of profiling middleware cluttering your pipeline. Lastly, Event Notifications is going into the BLC and being leveraged by various parts of the platform (ADO, network, IO, Azure SDKs, etc), it seems weird that you can't access a notification for Begin/End Request.
We want to add support for events via Microsoft.Framework.Notification to various components in Hosting that can be consumed in process by diagnostic tools.
To start with we want to include data/events with known tooling experiences built around them. This isn't a complete list, but includes things we can start on.
Pipeline
// @rynowak @Tratcher
The text was updated successfully, but these errors were encountered: