Mikel Blanchard
Mikel Blanchard
@dariogriffo Does it work if you do this? ```csharp var logger = new LoggerConfiguration().WriteTo.OpenTelemetry().CreateLogger(); builder.Services .AddOpenTelemetry().UseOtlpExporter() .AddLogging(c => c .ClearProviders() // Clear built-in ILoggerProviders and the OpenTelemetry one added by...
@davidfowl I just tested it, this seems to work fine: ```csharp builder.Logging.AddOpenTelemetry(); builder.Services.AddOpenTelemetry().UseOtlpExporter(); ``` Which is what I would expect. When using `UseOtlpExporter` you can just call: ```csharp builder.Services.AddOpenTelemetry().UseOtlpExporter(); ```...
> potentially make our our own attributes for experimental/opt-in which generate build info/warnings Just FYI .NET 8 added [ExperimentalAttribute](https://learn.microsoft.com/dotnet/api/system.diagnostics.codeanalysis.experimentalattribute).
Piggybacking on what @vishweshbankwar said above... IMO let's stick with using Enrich for now. We kind of need to wait and see what happens with .NET9 and the planned tracing...
@eerhardt How urgent is this? If we go the route of making the ctor public in SDK it will take a bit of time to get out into a stable...
Just to add some clarity here, OtlpExporter has some code to try and resolve `peer.service` from some common known attributes: https://github.com/open-telemetry/opentelemetry-dotnet/blob/a31bca866dab2f9735713e9be9bcf80d95ca0104/src/Shared/PeerServiceResolver.cs#L36-L57 My guess would be the new instrumentation on stable...
@cartersocha and I just ran into this too. In a demo we have something like... ```csharp builder.Services.AddOpenTelemetryTracing(options => { options .SetResourceBuilder(resourceBuilder) .AddSource("MyCustomSource") // Collect all traces from "MyCustomSource" //.AddAspNetCoreInstrumentation() //...
In the actual demo `AddAspNetCoreInstrumentation` is added so it actually works fine. We were just messing with it to capture some screenshots and disabled `AddAspNetCoreInstrumentation` temporarily thinking that would cause...
@simhgd If possible, could you add a couple of examples of the values you are seeing? In general, the spec is pretty clear about the names being low cardinality. Check...
Some thoughts I have on this... > Utilize the http.route, e.g. in the above example https;//www.contoso.com/users/{userId}/chat/{chatId}, and log the parameter values as separate tags i.e. in this case userId and...