builder.Services.AddOpenTelemetry()
.UseOtlpExporter(OtlpExportProtocol.Grpc, new Uri("http://endpoint"))
.ConfigureResource(...)
.WithMetrics(...)
.WithTracing(...);
But as of now seq require a distinct endpoint for logs and traces (and probably metrics in the future). This complicates the setup since each endpoint must be configured separately. It would be nice to support a unified endpoint so that the above code would be sufficient to cover all three.
Seq follows the OTEL standard. When using gRPC (as in your example) logs and traces use the same endpoint. When using HTTP/protobuf then endpoints are /ingest/otlp/v1/logs and /ingest/otlp/v1/traces.
There's a extension method to export OTLP for logs, traces and metrics:
But as of now seq require a distinct endpoint for logs and traces (and probably metrics in the future). This complicates the setup since each endpoint must be configured separately. It would be nice to support a unified endpoint so that the above code would be sufficient to cover all three.