From 18698692aee69b261977790359d32f2301559970 Mon Sep 17 00:00:00 2001 From: Aristotelos Date: Mon, 17 Oct 2022 08:30:21 +0200 Subject: [PATCH] Link to .NET docs about different ports Document the solution described in #3608 with a link to .NET documentation how to do this, because it seems a best practice to expose the Prometheus scraping endpoint on a different port. Signed-off-by: Aristotelos --- src/OpenTelemetry.Exporter.Prometheus.AspNetCore/README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/OpenTelemetry.Exporter.Prometheus.AspNetCore/README.md b/src/OpenTelemetry.Exporter.Prometheus.AspNetCore/README.md index 1c039277b03..25fd1a85134 100644 --- a/src/OpenTelemetry.Exporter.Prometheus.AspNetCore/README.md +++ b/src/OpenTelemetry.Exporter.Prometheus.AspNetCore/README.md @@ -66,6 +66,10 @@ dotnet add package --prerelease OpenTelemetry.Exporter.Prometheus.AspNetCore && context.Connection.LocalPort == 5067); ``` + This can be used in combination with + [configuring multiple ports on the ASP.NET application](https://learn.microsoft.com/aspnet/core/fundamentals/servers/kestrel/endpoints) + to expose the scraping endpoint on a different port. + ## Configuration The `PrometheusExporter` can be configured using the `PrometheusExporterOptions`