Timothy Mothra

/AzurePipelines run

@MariiaHubenko Please review our documentation on TelemetryChannels here: https://docs.microsoft.com/azure/azure-monitor/app/telemetry-channels#built-in-telemetry-channels The `InMemoryChannel` is intended for synchronous workloads whereas the `ServerTelemetryChannel` is for asyncronous workloads. Also, you're using very old versions of...

`ServerTelemetryChannel` is in a different package: https://www.nuget.org/packages/Microsoft.ApplicationInsights.WindowsServer.TelemetryChannel/ The timeout is not configurable, but you can provide your own `CancellationToken` to the `FlushAsync` methods: https://github.com/microsoft/ApplicationInsights-dotnet/blob/ba9fc0e274fab6f7632cd0bc8650b4bddfd0e803/BASE/src/Microsoft.ApplicationInsights/TelemetryClient.cs#L681-L690 https://github.com/microsoft/ApplicationInsights-dotnet/blob/ba9fc0e274fab6f7632cd0bc8650b4bddfd0e803/BASE/src/ServerTelemetryChannel/ServerTelemetryChannel.cs#L343-L350

We don't have any recommendations for disposing the SDK. It's only necessary to call `Flush` or `FlushAsync` when your application is shutting down. I believe the timeout was set to...

Adding this for context: https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.trace.autoflush?view=netframework-4.8

We're working on doc improvements to clearly describe flushing recommendations. If you're using the latest version of the SDK, you can `await FlushAsync()`

Hi @sirsendu-mukherjee, Thanks for the detailed explanation! There's a lot of information to break down, forgive me if I miss something. ### You referenced: 1. AspNetCore application with the 'Microsoft.ApplicationInsights.AspNetCore'...

Regarding the self-diagnostics, change the log level to Warning. You're looking for the internal logs from this class, but specifically the "TransmissionSendingFailed" message. https://github.com/microsoft/ApplicationInsights-dotnet/blob/2f10802f443cb6cdd2cafe8af26ad060eaeee822/BASE/src/ServerTelemetryChannel/Implementation/TelemetryChannelEventSource.cs#L172-L173 Regarding your comment; `this same setup...

"No such host is known" - this may be a DNS related issue in the App Service environment. If that's the case, I won't be able to help you with...

Hi @arturohernandez10, your issue sounds different than this one. I recommend creating a new Issue with some examples so we don't confuse these two.