Question 1

How do I add prometheus-net to an ASP.NET Core application?

Accepted Answer

Install the prometheus-net.AspNetCore NuGet package, add app.UseHttpMetrics() in Configure, and endpoints.MapMetrics() in UseEndpoints. Refer to the Sample.Web project for a complete example.

Question 2

What's the difference between prometheus-net and OpenTelemetry for .NET metrics?

Accepted Answer

prometheus-net is optimized for Prometheus integration with higher performance for existing time series, while OpenTelemetry is vendor-agnostic but may have more overhead. Benchmarks in the README highlight these trade-offs.

Question 3

How can I secure the metrics endpoint from unauthorized access?

Accepted Answer

Use ASP.NET Core authorization policies with RequireAuthorization on MapMetrics, or expose metrics on a separate port using KestrelMetricServer, as shown in Sample.Web.DifferentPort.

Question 4

How do I handle high-cardinality labels in prometheus-net?

Accepted Answer

Use the WithManagedLifetime() factory to enable automatic expiration of metrics after a set period, or manually delete metrics to prevent memory bloat, detailed in the Deleting metrics section.

Question 5

What are exemplars and how do I use them in prometheus-net?

Accepted Answer

Exemplars attach trace IDs to metrics for distributed tracing. Enable by using OpenTelemetry or setting Activity.Current, and customize via ExemplarBehavior in metric configurations, as explained in the Exemplars section.

Question 6

Can I export metrics to Pushgateway with authentication?

Accepted Answer

Yes, use MetricPusher with a custom HttpClient that includes authentication headers, such as Basic auth, as demonstrated in the Publishing to Pushgateway with basic authentication section.

prometheus-net

What is prometheus-net?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions