Traces - Options to customize trace listeners

Adding options to customize Trace listeners for our traces when running on NET Core environment would be great, and also, to disable all trace listeners (including DefaultTraceListener).

If users want to send traces to a particular sink, in NET Core, today it’s extremely complex. When running in NETFX, this can be achieved by web.config/app.config.

It requires some weird hack like:

Type defaultTrace = Type.GetType("Microsoft.Azure.Cosmos.Core.Trace.DefaultTrace,Microsoft.Azure.Cosmos.Direct");
TraceSource traceSource = (TraceSource)defaultTrace.GetProperty("TraceSource").GetValue(null);
traceSource.Switch.Level = SourceLevels.All;
traceSource.Listeners.Clear();
traceSource.Listeners.Add(... my desired listener);

Ideally, we could expose some config APIs like:

• CosmosClientOptions.DiagnosticOptions.DisableTraces: It would disable all tracing and any machine wide default trace listeners from the SDK trace source.
• CosmosClientOptions.DiagnosticOptions.AttachTraceListeners(IEnumerable<TraceListener>): Would attach the listeners to our trace source programmatically.

For performance reasons, any application that does not want to collect traces can disable them to avoid any lock contention on the default machine-wide tracing.

[ealsur]

@RamenTurismo not implemented. The team is working on AI (Application Insights) and Open Telemetry integration, PRs for that are in progress.

[j82w]

I think there is some confusion. This is not related to CosmosDiagnostics. This is only referring to the DefaultTrace inside the SDK as part of the .NET framework. CosmosDiagnostic levels will need to be handled separately. I think the naming will need to be clear to avoid confusion.