I don't feel so well… Integrating health checks in your .NET Core solutions
summary
Shows how ASP.NET Core 2.2 health checks are wired: AddHealthChecks registers checks and exposes /health and /ping endpoints that return 200/503/500; default aggregator marks the whole service unhealthy if any check fails. Demonstrates custom checks (memory, DBContext, a 15s slow task), Polly circuit breakers inspected via a health check, and publishing to Application Insights or Prometheus pushgateway with Grafana dashboards and Slack alerts. Demo uses Docker Compose and a working metrics pipeline; note a .NET Core 2.2 IHostedService registration ordering bug to watch.
AI-written summary · about
chapters (13)
- 0:00Introduction and context
- 1:02Health checks in distributed systems
- 8:51Health checks in .NET Core
- 12:45Basic health check setup
- 24:30Building health checks into apps
- 28:44Advanced health check patterns
- 36:17Health check publishers
- 39:03Integrating with Prometheus
- 48:01Self-healing and resilience
- 52:21Health checks in Kubernetes
- 55:34Demo rolling updates
- 59:16Securing health endpoints
- 1:00:44Summary and Q&A
related talks
16mInterview Speaker
48mHandling non-functional requirements in .NET Core microservices
16mASP.NET Core 2.2
28mApplication Health Checks Done the Right Way
01h 01mLogging, tracing and metrics: instrumentation in .NET and Azure
21mHealth Checks: A Boon or a Curse?
01h 00mWhat's New in ASP.NET Core?
54mLogging, Metrics and Events in ASP NET Core