A liveness and health check library for ASP.NET Core applications with out-of-box enterprise service checks.
BeatPulse is a liveness and health check library for ASP.NET Core applications that allows load balancers and orchestration systems to verify application and dependency health. It provides a suite of pre-built checks for databases, caches, message brokers, and cloud services, ensuring traffic is only directed to fully operational components.
ASP.NET Core developers and DevOps engineers building microservices or distributed applications that require robust health monitoring for load balancing, Kubernetes liveness probes, and dependency status tracking.
Developers choose BeatPulse for its extensive collection of out-of-box enterprise health checks, integrated UI dashboard, and failure notification system, offering a comprehensive monitoring solution before Microsoft's native health checks were available.
Liveness, health check library for ASP.NET Core Applications
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers out-of-box liveness libraries for over 15 systems including SQL Server, Redis, Kafka, and Azure services, as listed in the installation steps, reducing development time for common dependencies.
BeatPulse.UI provides a minimal web interface to visualize health results from multiple endpoints, configurable via JSON settings for centralized monitoring.
Supports webhooks to send notifications to services like Microsoft Teams or Slack when checks fail, with customizable payloads and failure details, as shown in the webhooks documentation.
Allows saving liveness data to external services like Application Insights and Prometheus via trackers, enhancing production monitoring capabilities.
The project is marked as deprecated, with no new features being added, and the team is focusing on Microsoft's health checks library, limiting future support and compatibility.
Only supports up to .NET Core 2.1 in version 3.0, making it incompatible with newer .NET versions without migration to the successor library, as stated in the README.
Requires installing separate NuGet packages for each type of health check (e.g., BeatPulse.SqlServer, BeatPulse.Redis), increasing setup overhead and potential version conflicts.