The OpenTelemetry project integrates tightly (and nicely) with ASP.NET Core, however there are other more complex systems built on top of Kestrel as well. To support those projects, its often as simple as allowing a request to be passed off from Kestrel directly to OpenTelemetry without integrating into ASP.NET's more feature rich components like request routing.
By marking PrometheusExporterMiddleware as public, more advanced use cases can be served (e.g. telemetry aggregation services) and other routing frameworks can be easily supported.
Additional Context
For additional context, I am selfishly interested in being able to use my Routable library with OpenTelemetry - but this seems that it would benefit the community as a whole by exposing this component to be leveraged as a building block in a larger whole with greater flexibility.
This issue was marked stale due to lack of activity and will be closed in 7 days. Commenting will instruct the bot to automatically remove the label. This bot runs once per day.
Feature Request
The OpenTelemetry project integrates tightly (and nicely) with ASP.NET Core, however there are other more complex systems built on top of Kestrel as well. To support those projects, its often as simple as allowing a request to be passed off from Kestrel directly to OpenTelemetry without integrating into ASP.NET's more feature rich components like request routing.
By marking
PrometheusExporterMiddleware
as public, more advanced use cases can be served (e.g. telemetry aggregation services) and other routing frameworks can be easily supported.Additional Context
For additional context, I am selfishly interested in being able to use my Routable library with OpenTelemetry - but this seems that it would benefit the community as a whole by exposing this component to be leveraged as a building block in a larger whole with greater flexibility.
Happy to submit a PR if it will help :)