Quartz.AspNetCore

Quartz.AspNetCore adds the two things a Quartz.NET scheduler wants from an ASP.NET Core application: an HTTP API that exposes scheduler management endpoints, and a health check that reports unhealthy when the scheduler is not running or cannot reach its store.

Hosting itself is in the core Quartz package — AddQuartz and AddQuartzHostedService need no extra reference. Quartz 3's AddQuartzServer, which registered the hosted service and a health check together, is gone.

Installation

dotnet add package Quartz.AspNetCore

Usage

WebApplicationBuilder builder = WebApplication.CreateBuilder(args);

builder.AddQuartz();
builder.Services.AddQuartzHttpApi();
builder.AddQuartzHostedService(options => options.WaitForJobsToComplete = true);
builder.Services.AddHealthChecks().AddQuartz();

WebApplication app = builder.Build();

app.MapQuartzHttpApi().RequireAuthorization();
app.MapHealthChecks("/healthz");

The API manages jobs and triggers, so authorize it: MapQuartzHttpApi returns the endpoint convention builder to say so on. The health check takes tags, so it can be filtered into separate liveness and readiness probes, and a named scheduler gets a check of its own.

Documentation

• ASP.NET Core integration
• HTTP API
• Quartz.NET documentation