-
Notifications
You must be signed in to change notification settings - Fork 881
Prometheus: Split up projects based on hosting mechanism #3057
Copy link
Copy link
Closed
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomershelp wantedGood for taking. Extra help will be provided by maintainersGood for taking. Extra help will be provided by maintainerspkg:OpenTelemetry.Exporter.Prometheus.AspNetCoreIssues related to OpenTelemetry.Exporter.Prometheus.AspNetCore NuGet packageIssues related to OpenTelemetry.Exporter.Prometheus.AspNetCore NuGet package
Description
Currently OpenTelemetry.Exporter.Prometheus contains two hosting mechanisms:
PrometheusExporterMiddleware(ASP.NET Core)PrometheusExporterHttpServer(HttpListener)
We decided on the SIG meeting today (3/15/2022) that we want to split these two hosting mechanisms into their own projects/assemblies. That should simplify configuration & documentation and also allow for the introduction of settings specific to the hosting technology (see #2882).
Proposing:
- OpenTelemetry.Exporter.Prometheus.AspNetCore
- OpenTelemetry.Exporter.Prometheus.HttpListener
Shared code should live in another project (proposing OpenTelemetry.Exporter.Prometheus.Shared) but we don't want to ship that project. Code from the shared project should be linked into the hosting-specific projects. Example of that type of sharing being done: OpenTelemetry.Contrib.Shared.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomershelp wantedGood for taking. Extra help will be provided by maintainersGood for taking. Extra help will be provided by maintainerspkg:OpenTelemetry.Exporter.Prometheus.AspNetCoreIssues related to OpenTelemetry.Exporter.Prometheus.AspNetCore NuGet packageIssues related to OpenTelemetry.Exporter.Prometheus.AspNetCore NuGet package