Replies: 1 comment
-
|
It is, yes. Either you can override signal-specific environment variables:
Or you can override signal-specific options to apply overrides with code: services.AddOpenTelemetry()
.WithLogging(builder => builder.AddOtlpExporter(o => o.Endpoint = new Uri("...")))
.WithMetrics(builder => builder.AddOtlpExporter(o => o.Endpoint = new Uri("...")))
.WithTracing(builder => builder.AddOtlpExporter(o => o.Endpoint = new Uri("..."))); |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is it possible to configure separate exporters for traces and metrics? We'd like to use two instances of Application Insights and Log Analytics, one with sampling for traces, requests, errors etc. and the second one, without any limits and sampling, for metrics.
When calling AddOpenTelemetry and UseAzureMonitor mutiple times, it looks like the last configurations wins and everything is sent to the instance the was configured as the last one.
Beta Was this translation helpful? Give feedback.
All reactions