Dotnet 6 Configuration

[hughesjs]

Dotnet 6 does away with the need for complex nested lambdas etc for configuration (let's be real, that was always a terrible API).

The new hotness WebApplication rather than Host or WebHost is great. Unfortunately, the existing ConfigureMetricsWithDefaults() doesn't work with this pattern at all.

We need to update things to work better with dotnet 6

[krzysiek-b]

+1

[Simonl9l]

@hughesjs & @krzysiek-b - What no Program or Startup!

Just in case you have not figured it out - this seems to work:

var builder = WebApplication.CreateBuilder();

builder.Services
    .AddMetrics(metrics)
    .AddAppMetricsSystemMetricsCollector()
    .AddAppMetricsCollectors();
           
builder.Host
    .ConfigureMetrics(builder =>
        {
            builder.Configuration.Configure(options =>
                {
                    options.DefaultContextLabel = "default";
                 });
         })
    .UseMetrics(options =>
        {
            options.EndpointOptions = endpointsOptions =>
                {
                    endpointsOptions.MetricsTextEndpointOutputFormatter =
                            new MetricsPrometheusTextOutputFormatter();
                };
        });
            
var web = builder.Build();
web.Urls.Add($"http://localhost:{port}");
web.UseMetricsTextEndpoint();
await web.RunAsync(_source.Token);

[hughesjs]

Yeah, I got it to work, but that's not really my point. A large part of the changes to dotnet 6 startup were driven by a desire to simplify things and reduce the need for chains of nested lamdas.

I feel like that's something we should aspire to support.

[gjemp]

@hughesjs can u share some example how did you get it working and for some reasons the metrics endpoint started to serve the data in binary format when i started to use AsPrometheusPlainText or AsPrometheusProtobuf as explained here: https://www.app-metrics.io/reporting/reporters/prometheus/