Mapping enrichers with Resource attributes

[cecilphillip]

Given a configuration similar to the following, would it possible to flow enriched properties to OTEL Resource attributes. For instances, I'd want to be able to set the host.name attribute with the value from WithMachineName.

Log.Logger = new LoggerConfiguration()
    .MinimumLevel.Information()
    .Enrich.FromLogContext()
    .Enrich.WithThreadId()
    .Enrich.WithEnvironmentName()
    .Enrich.WithMachineName()
    .WriteTo.Console(outputTemplate: outputTemplate)
    .WriteTo.OpenTelemetry(opts =>
    {
        opts.ResourceAttributes = new Dictionary<string, object>
        {
            ["service.name"] = "BackendApiService"
        };
    })
    .CreateLogger();

[nblumhardt]

I think this is ultimately where we're heading, but I'm not sure what the mechanics should be.

Since resource attributes are expected to be static for the life of the application it's a bit of a waste to use an enricher in this case, but on the other hand, it leaves nice friendly-named properties for other sinks to consume 🤔

Resource attributes are also shared across the entire batched OTLP payload, so we'd need to think about what happens when multiple values show up for a RA.