Skip to content

Prometheus: Split up projects based on hosting mechanism #3057

@CodeBlanch

Description

@CodeBlanch

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.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestgood first issueGood for newcomershelp wantedGood for taking. Extra help will be provided by maintainerspkg:OpenTelemetry.Exporter.Prometheus.AspNetCoreIssues related to OpenTelemetry.Exporter.Prometheus.AspNetCore NuGet package

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions