Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide FlushAsync in ServerTelemetryChannel #482

Closed
cesarblum opened this issue Mar 23, 2017 · 5 comments
Closed

Provide FlushAsync in ServerTelemetryChannel #482

cesarblum opened this issue Mar 23, 2017 · 5 comments

Comments

@cesarblum
Copy link

I'm not sure why that class doesn't expose a FlushAsync() method. Please explain if there's a rationale for that.

We've recently dealt with a customer issue where their service's performance was severely degraded due to calls to ServerTelemetryChannel.Flush() blocking their threads. Ideally they should be able to call an async method and not block when flushing.

@muratg
Copy link

muratg commented Mar 23, 2017

👀

@pandianrb
Copy link

Hi @cijothomas ,

do we need manual code for tracking the exception for application insights ?

client.TrackException(new Exception("Demo exception."));
client.TrackTrace("Demo application exiting.");

do we have any configuration to track the exception across the console application ?

@paulomorgado
Copy link

This should be the API:

Task FlushAsync(CancellationToken);

You can await it, Wait it or cancel it.

@github-actions
Copy link

github-actions bot commented Jan 4, 2022

This issue is stale because it has been open 300 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@PawelAdamczuk
Copy link

For what it's worth, I faced this issue today and it made me decide to not use NLog in my project altogether.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants