How do you know if your web application is healthy? Sure, you can check to be sure your site is running, but is that enough?

For instance, maybe your database is responding slowly, or your logging has crashed, or maybe your server is about to run out of hard drive space. How would you know that?

Well, the answer, it turns out, is with Health Checks. Health checks are built into .NET Core web applications.

Purchase Courses: https://iamtimcorey.com
Source code: https://leadmagnets.app/?Resource=Hea...

Newsletter signup: https://signup.iamtimcorey.com/

Breakdown courtesy of Ralfs HBK
0:00 - Intro
1:46 - Creating a demo Blazor Server App
3:27 - About Application Health
5:35 - Adding Health Check NuGet packages
6:53 - Configure Health Checks : Health states
15:03 - Configure Health Checks: Advanced info
18:41 - Configure Health Checks: Overall application check
21:27 - Side note: Lamda expression break down
23:37 - Configure Health Checks: Tags
28:21 - Better Health Checks data view: app setup (quick NuGet references)
32:47 - Better Health Checks data view: configuration
34:02 - Better Health Checks data view: appsettings.json;
38:21 - Better Health Checks data view: running the app
40:58 - Implementing Health Checks in application: MVC app setup
46:04 - Custom App Health Check: Practical Health Checks
55:07 - Implementing Custom App Health Checks
1:02:29 - Health Checks: Recap
1:03:50 - What are health checks for and what should you check?
1:10:44 - Security concerns
1:12:35 - Concluding remarks