This document discusses .NET health checks and their importance. It provides an overview of health checks in .NET Core, how they were implemented in 2015, and how they can be used to monitor application and subsystem availability. Examples are given of how health checks integrate with Azure and Kubernetes for failover and load balancing. Resources are listed for demo code, documentation, and the community project. The presenter is available for questions on Twitter.

2. Software Engineer
at the YOO
• .NET addicted web developer
• Microsoft MVP
• https://asp.net-hacker.rocks
• Twitter: @sharpcms
• Father of three boys

3. Available next week on Packt and Amazon

4. Topics tonight
• A really small Introduction
• Code… code… code…
• Health endpoint
• Custom Health Checks
• Using Health Check results
• Third Party Health Checks
• Health Check UI

5. Health Checks
• Implementation started in fall 2015
• Publicly available with .NET Core 2.2
• Microsoft.AspNetCore.Diagnostics.HealthChecks
• Community Project:
• AspNetCore.Diagnostics.HealthChecks

6. Why Health Checks?
• Keep your application available
• Notify your users about degraded or unhealthy states
• Partially available APIs or web apps
• Knowing the health state of your application
• Knowing the health of your sub systems
• Control failover and load balancer on Azure
• Control failover and load balancer on Kubernetes

7. Resources
• Demo codes:
• https://github.com/JuergenGutsch/healthchecks-demo
• Docs:
• https://docs.microsoft.com/en-us/aspnet/core/host-
and-deploy/health-checks?view=aspnetcore-5.0
• Community:
• https://github.com/Xabaril/AspNetCore.Diagnostics.He
althChecks

8. Thank you. Ping a on Twitter @sharpcms