Use this chapter to choose the right package family first, then open the package references for package-specific defaults and code samples.
Naming convention
- Health check packages use the
DotNetDiag.HealthChecks.<Provider>convention. - UI packages use the
DotNetDiag.HealthChecks.UI.*convention and are covered in the UI manual. - Publisher packages use the
DotNetDiag.HealthChecks.Publisher.*convention and are covered in publishers and metrics.
Core and platform checks
- Application Status
- OpenID Connect Server
DotNetDiag.HealthChecks.KubernetesDotNetDiag.HealthChecks.NetworkDotNetDiag.HealthChecks.SignalRDotNetDiag.HealthChecks.SystemDotNetDiag.HealthChecks.Uris- HashiCorp Vault
AWS packages
Azure packages
- Azure Application Insights
- Azure Data Tables
- Azure IoT Hub
- Azure Key Vault Secrets
- Azure Event Hubs
- Azure Blob Storage
- Azure File Shares
- Azure Queue Storage
- Azure Digital Twin
- Azure Key Vault
- Azure Service Bus
DotNetDiag.HealthChecks.AzureSearch
Databases, search, and messaging systems
- ActiveMQ
- ArangoDb
- Artemis
- ClickHouse
- CockroachDB
- Cosmos DB
DotNetDiag.HealthChecks.Dapr- DuckDB
- etcd
DotNetDiag.HealthChecks.ElasticsearchDotNetDiag.HealthChecks.EventStoreDotNetDiag.HealthChecks.EventStore.gRPC- Firebird
DotNetDiag.HealthChecks.Gcp.CloudFirestore- Google Cloud Storage
- Grafana
DotNetDiag.HealthChecks.GremlinDotNetDiag.HealthChecks.Hangfire- IbmMQ
- InfluxDB
DotNetDiag.HealthChecks.Kafka- Apache Pulsar
- Memcached
DotNetDiag.HealthChecks.Milvus(preview)- MinIO
- MongoDB
- MySQL
- NATS
- Neo4j
- PostgreSQL
- OpenSearch
DotNetDiag.HealthChecks.OracleDotNetDiag.HealthChecks.Qdrant- RabbitMQ
- RabbitMQ v6
DotNetDiag.HealthChecks.RavenDBDotNetDiag.HealthChecks.Redis- Valkey
DotNetDiag.HealthChecks.SendGridDotNetDiag.HealthChecks.SolrDotNetDiag.HealthChecks.SqliteDotNetDiag.HealthChecks.SqlServer- SurrealDB
- ZooKeeper
How to use this catalog effectively
- Start with this chapter when you are selecting a provider package.
- Open the package references when you need overload-specific behavior such as credentials, region selection, or connection pooling.
- Use the getting started chapter for common registration patterns that apply across packages.
- Use the UI manual and publishers and metrics chapters for dashboard and observability components.