How kritultrathod/dotnetcorehealthchecks works
The repository contains two ASP.NET Core applications: a health-check UI host and a sample service exposing health checks and a weather API. The main user workflow is to request the UI or service endpoints; the service’s health endpoint runs registered checks and returns their status, while its controller serves generated forecasts. The UI host maps the HealthChecks UI and configures in-memory storage. The README gives only a high-level description, so no UI-to-probe target relationship is inferred.
Main entry points: DotNetCoreHealthChecks/Startup.cs Service configuration · AspNetCoreHealthChecker/Startup.cs UI configuration · WeatherForecastController.cs Weather API · HomeController.cs Home routes
Components 13
Health UI host
- UI configuration
AspNetCoreHealthChecker/Startup.cs - Health UI endpoint
AspNetCoreHealthChecker/Startup.cs - In-memory storage
AspNetCoreHealthChecker/Startup.cs - Home routes
AspNetCoreHealthChecker/Controllers/HomeController.cs
Health-check service
- Service configuration
DotNetCoreHealthChecks/Startup.cs - Health endpoint
DotNetCoreHealthChecks/Startup.cs - Random status check
DotNetCoreHealthChecks/HealthChecks/RandomResponseTimeChecker.cs - Weather API
DotNetCoreHealthChecks/Controllers/WeatherForecastController.cs - Forecast model
DotNetCoreHealthChecks/WeatherForecast.cs - Swagger setup
DotNetCoreHealthChecks/Startup.cs
Application runtime
- UI host
AspNetCoreHealthChecker/Program.cs - Service host
DotNetCoreHealthChecks/Program.cs
Other components
- HTTP client
Connections 15
- HTTP client → Health UI endpoint: requests UI
AspNetCoreHealthChecker/Startup.cs - HTTP client → Home routes: requests pages
- UI host → UI configuration: starts with
AspNetCoreHealthChecker/Program.cs - UI configuration → Health UI endpoint: maps endpoint
AspNetCoreHealthChecker/Startup.cs - UI configuration → In-memory storage: configures storage
AspNetCoreHealthChecker/Startup.cs - UI configuration → Home routes: maps routes
AspNetCoreHealthChecker/Startup.cs - HTTP client → Health endpoint: requests status
DotNetCoreHealthChecks/Startup.cs - HTTP client → Weather API: requests forecasts
DotNetCoreHealthChecks/Controllers/WeatherForecastController.cs - Service host → Service configuration: starts with
DotNetCoreHealthChecks/Program.cs - Service configuration → Health endpoint: maps endpoint
DotNetCoreHealthChecks/Startup.cs - Service configuration → Random status check: registers check
DotNetCoreHealthChecks/Startup.cs - Health endpoint → Random status check: runs registered checks
DotNetCoreHealthChecks/Startup.cs - Service configuration → Weather API: maps controllers
DotNetCoreHealthChecks/Startup.cs - Weather API → Forecast model: creates forecasts
DotNetCoreHealthChecks/Controllers/WeatherForecastController.cs - Service configuration → Swagger setup: configures docs
DotNetCoreHealthChecks/Startup.cs