You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs package in to OpenTelemetry.Exporter.OpenTelemetryProtocol.
Finalize dotnet.ilogger.category, logRecord.EventId.Id and logRecord.EventId.Name attribute names.
Post stable release
By following the plan above we would be able to release stable OtlpLogExporter. However, we will still have a feature gap of supporting signal specific environment variables i.e. OTEL_EXPORTER_OTLP_SIGNAL_*. Supporting this may require adding signal specific option classes. We will explore the design for this at later time.
The text was updated successfully, but these errors were encountered:
Proposal
Resolve 4388 by adding a new extension method:
In addition to this we will have following extension methods as well for users who would like to use the default settings.
New class
In favor of moving towards a consistent experience between logs and traces we will add the following extension method for traces:
New class
Merge
OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs
package in toOpenTelemetry.Exporter.OpenTelemetryProtocol
.Finalize
dotnet.ilogger.category
,logRecord.EventId.Id
andlogRecord.EventId.Name
attribute names.Post stable release
By following the plan above we would be able to release stable
OtlpLogExporter
. However, we will still have a feature gap of supporting signal specific environment variables i.e.OTEL_EXPORTER_OTLP_SIGNAL_*
. Supporting this may require adding signal specificoption
classes. We will explore the design for this at later time.The text was updated successfully, but these errors were encountered: