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

Allow usage of trackAvailability() to use CUSTOM web tests in ApplicationInsightsPublisher #2373

Open
R3d-Dragon opened this issue Feb 10, 2025 · 0 comments

Comments

@R3d-Dragon
Copy link

The current implementation of the ApplicationInsightsPublisher publishes healthCheck results through the TelemetryClient.TrackEvent() method.
As a result, healthCheck metrics are stored within the "customEvents" table of application insights. The built-in web-test (availability) functionality of Azure ApplicationInsights cannot be used with this approach.

What would you like to be added:
Provide an option to publish healthCheck metrics through the TelemetryClient.TrackAvailability() method.

Why is this needed:
With this approach, healthCheck metrics are stored within the "AvailabilityResults" table in application insights.
In addition, a CUSTOM web-test will automatically be created in Azure Application Insights which allows to monitor your application easily.

For more details, please have a look at the official documentation: https://learn.microsoft.com/en-us/azure/azure-monitor/app/availability?tabs=track#create-an-availability-test

R3d-Dragon added a commit to R3d-Dragon/AspNetCore.Diagnostics.HealthChecks that referenced this issue Feb 10, 2025
R3d-Dragon added a commit to R3d-Dragon/AspNetCore.Diagnostics.HealthChecks that referenced this issue Feb 10, 2025
R3d-Dragon added a commit to R3d-Dragon/AspNetCore.Diagnostics.HealthChecks that referenced this issue Feb 10, 2025
R3d-Dragon added a commit to R3d-Dragon/AspNetCore.Diagnostics.HealthChecks that referenced this issue Feb 19, 2025
R3d-Dragon added a commit to R3d-Dragon/AspNetCore.Diagnostics.HealthChecks that referenced this issue Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant