Cijo Thomas

Removing this from 1.3.0 milestone and moving to 1.4.0. 1.3.0 is releasing shortly, and want to allow bake time for the new feature.

> Hi, the previous PR seems to be closed due to inactivity. I am just wondering if I could take that over? If @mic-max is not planning to work on...

@alanwest might be able to recommend the options, if any. I believe this is same as https://github.com/open-telemetry/opentelemetry-dotnet/issues/2009 Maybe related is https://github.com/open-telemetry/opentelemetry-dotnet/issues/2120

> TelemetrySpan.UpdateName() changes the name of the ActivitySource ^ This is incorrect. UpdateName() updates span name (aka activity.DisplayName).

When you say "log messages", do you mean the standalone logs generated from `ILogger`, or the `ActivityEvent` which are embedded logs inside Activity?

The embedded logs, (AKA, ActivityEvents) are already supported in OTLP, Jaeger exporters. The OTLP Log Exporter is for exporting the "standalone logs".

There is a contrib package, capable of taking ILogger logs, and attaching them to to Activity as ActivityEvent, (which would then be exported to Jaeger.) https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Contrib.Preview (Its preview package. And...

> We're using Serilog. If you are using Serilog's logging API, then not much can be done here. If you use the `ILogger` from `Microsoft.Extensions.Logging.Abstrations`, but use Serilog as a...

@fschmied There is a preview package, which allows ILogger logs to be attached to Activity Events, (which will then be exported to Jaeger.) https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Extensions

@fschmied AzMonExporter already supports iLogger logs (package may not be released yet to nuget.org). Please use AzMonitor repos for questions about that.