All 15 Background Tasks & Hosted Services questions
More in Background Tasks & Hosted Services
How would you configure a BackgroundService to fail fast and crash the host if a critical startup dependency (like a message broker) is unreachable? How does graceful shutdown work for a BackgroundService, and how should ExecuteAsync respect the CancellationToken? How would you implement a producer-consumer background processing pipeline using System.Threading.Channels alongside a BackgroundService? How would you implement a cron-like scheduled background job (e.g., 'run daily at 2 AM') without a third-party scheduling library? How would you implement retry logic with exponential backoff for a background service that calls a potentially-flaky external API? How would you implement a background task queue accepting ad-hoc work items dynamically at runtime, rather than a fixed polling loop? How do you test a BackgroundService's business logic without waiting for its actual polling interval, keeping tests fast?
Advertisement
ASP.NET Core › Background Tasks & Hosted Services

How do background services interact with health checks to signal their operational status to an orchestrator like Kubernetes?

Advanced

Answer

A background service can expose its health via a custom IHealthCheck that inspects shared state (like a 'last successful run' timestamp the service updates on each cycle), letting the health endpoint report unhealthy if the background work has stalled or crashed -- crucial because a web server can still respond to HTTP requests perfectly fine even while its background processing has silently died, so relying solely on basic liveness (process is running) wouldn't catch this failure mode.
public class QueueProcessorHealthCheck : IHealthCheck {
    public Task<HealthCheckResult> CheckHealthAsync(HealthCheckContext context, CancellationToken ct) {
        var elapsed = DateTime.UtcNow - QueueProcessor.LastSuccessfulRun;
        return Task.FromResult(elapsed < TimeSpan.FromMinutes(5)
            ? HealthCheckResult.Healthy()
            : HealthCheckResult.Unhealthy("Queue processor stalled"));
    }
}

builder.Services.AddHealthChecks().AddCheck<QueueProcessorHealthCheck>("queue-processor");
Real-world example A Kubernetes liveness probe automatically restarts a pod whose background queue processor has been silently stuck for over 5 minutes, detected via a custom health check monitoring the processor's last successful iteration timestamp.

Common follow-ups: How do you distinguish liveness from readiness for a background-service-heavy application?;What's the risk of a health check that restarts too aggressively?

Health Checks;Hosting Models: Kestrel IIS & Reverse Proxies
All 15 Background Tasks & Hosted Services questions