Skip to content
Liveness, health check library for ASP.NET Core Applications
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
AzureDevOpsTasks Fix broken image in Feb 18, 2019
build Increment UI version package Jan 14, 2019
doc Added change log Sep 26, 2018
docker-images/BeatPulseUI-Image Set docker image as 2.1 project Jun 10, 2018
docker-services IMAP liveness with initial SSL tests and docker-compose mail server Aug 29, 2018
samples Remove new creation in each request for HttpClient Dec 21, 2018
src Typo fixture Dec 31, 2018
tests Merge branch 'master' of into… Jan 12, 2019
.env Merge conflicts and minor changes Nov 20, 2018
.gitattributes Added initial files for appveyor Jan 22, 2018
.gitignore Azure DevOps Release Gate extension for Xabaril BeatPulse (#104) Feb 6, 2019
BeatPulse.sln Fix issues with merge and added packages to ps1 Nov 20, 2018
Directory.Build.props Added Directory.Build.pros and variables unto dependencies.props Feb 17, 2018
LICENSE Initial commit Jan 22, 2018 Minor readme change Dec 12, 2018
appveyor.yml AppVeyor - Skip symbols on nuget Dec 8, 2018
build-docker-images.ps1 Timeout is on each liveness and not on middleware. Review DetailedOup… Apr 30, 2018
build.ps1 Fix issues with merge and added packages to ps1 Nov 20, 2018
docker-compose.yml Merge conflicts and minor changes Nov 20, 2018
global.json Port filter: Added port option in BeatPulseOptions to filter in wich … Sep 12, 2018
package-lock.json Merge master Jun 9, 2018

Build status NuGet

Build history

Beat Pulse


Beatpulse project was created to fill a gap in Asp.Net Core ecosystem when no health checks libraries were available.

Now that Microsoft is rolling out their own health checks integration, the Beatpulse project will be focused in contributing towards this library.

All liveness, UI and Beatpulse features are already available as extensions for the new Microsoft health checks package in this repository:

Xabaril - AspNetCore.Diagnostics.HealthChecks


The team will continue to provide support to Beatpulse until version 3.0 with .Net Core version 2.1 but no new features will be added in this repository.

What is Health Checking?

Health checking is the process where load balancers or application delivery controller does periodic checks on our applications to make sure that they are up and responding without any problems. If our applications are down for whatever reason or any of the systems that our applications depends on (A database, a distributed cache, web service, ect) are down, the load balancer, k8s, should detect this and stop sending traffic its way trying to restore services manually or automatically.

BeatPulse is a powerfull liveness, readiness library for .NET Core Applications with many out of box enterprise health check services.

Getting Started

This documentation is for BeatPulse latest version, you can check changes and package compatibility on ChangeLog.

  1. Install the Nuget Package into your ASP.NET Core application.
Install-Package BeatPulse
  1. Install the liveness libraries that you need on your project. At this moment BeatPulse contains NuGet libraries for:
  • System (Disk Storage, Memory)
  • Network (Tcp, Ftp, Sftp, Imap, Smtp, Dns resolve)
  • Redis
  • Elasticsearch
  • SqlServer
  • MongoDb
  • Postgress Sql
  • EventStore
  • Oracle
  • Azure Storage (Blobs, Tables and Queues)
  • Azure Service Bus (Event Hub, Service Bus queues and topics)
  • DocumentDb
  • MySQL
  • SqLite
  • Kafka
  • RabbitMQ
  • Identity Server
  • AWS DynamoDB
  • Custom lambda liveness.
Install-Package BeatPulse.System
Install-Package BeatPulse.Network
Install-Package BeatPulse.SqlServer
Install-Package BeatPulse.MongoDb
Install-Package BeatPulse.Npgsql
Install-Package BeatPulse.Elasticsearch
Install-Package BeatPulse.EventStore
Install-Package BeatPulse.Redis
Install-Package BeatPulse.AzureStorage
Install-Package BeatPulse.AzureServiceBus
Install-Package BeatPulse.MySql
Install-Package BeatPulse.DocumentDb
Install-Package BeatPulse.SqLite
Install-Package BeatPulse.Kafka
Install-Package BeatPulse.RabbitMQ
Install-Package BeatPulse.IdSvr
Install-Package BeatPulse.DynamoDB
Install-Package BeatPulse.Oracle
  1. Add BeatPulse into your ASP.NET Core project. UseBeatPulse is a new IWebHostBuilder extension method to register and configure BeatPulse.
 public static IWebHost BuildWebHost(string[] args) =>
                   options.ConfigurePath(path:"health") //default hc
                        .ConfigureTimeout(milliseconds:1500) // default -1 infinitely
                        .ConfigureDetailedOutput(detailedOutput:true,includeExceptionMessages:true); //default (true,false)
  1. Add BeatPulseService and set the liveness libraries to be used.
    services.AddBeatPulse(setup =>
        //add sql server liveness
  1. Request BeatPulse to get liveness results.
curl http://your-domain/hc 
GET /hc HTTP/1.1
Host: your-domain
User-Agent: curl/7.49.0
Accept: */*
HTTP/1.1 200 OK

For more information about BeatPulse configuration and other features ( configuration, cache, authentication, etc ) see the specific documentation section.

Tracking pulses

With TrackingPulses you can save liveness information in external services. Currently we have developed different trackers you can use:

Application Insights Tracker

Prometheus Tracker

StatusPage Tracker


The project BeatPulse.UI is a minimal UI interface that stores and shows the liveness results from the configured liveness uri's. To integrate BeatPulse.UI in your project you just need to add the BeatPulse.UI services and middlewares.

    public class Startup
        public void ConfigureServices(IServiceCollection services)

        public void Configure(IApplicationBuilder app, IHostingEnvironment env)

This automatically registers a new interface on /beatpulse-ui.

Optionally, UseBeatPulseUI can be configured with different UI response path.


BeatPulseUI is also available as a docker image You can read more about beat pulse ui docker image.


The liveness to be used on BeatPulse-UI are configured using the BeatPulse-UI settings.

  "BeatPulse-UI": {
    "Liveness": [
        "Name": "HTTP-Api-Basic",
        "Uri": "http://localhost:6457/health?DetailedOutput=true"
    "Webhooks": [
        "Name": "",
        "Uri": "",
        "Payload": "",
    "EvaluationTimeOnSeconds": 10,
1.- Liveness: The collection of liveness uris to watch.
2.- EvaluationTimeOnSeconds: Number of elapsed seconds between liveness checks.
3.- Webhooks: If any liveness return a *Down* result, this collections will be used to notify the error status. (Payload is the json payload and must be scape. For mor information see Notifications section)
4.- MinimumSecondsBetweenFailureNotifications: The minimun seconds between failure notifications in order not flooding the notification receiver.

All liveness results are stored into a SqLite database persisted to disk with livenessdb name.

Failure Notifications

If the WebHooks section is configured, BeatPulse-UI automatically posts a new notification into the webhook collection. BeatPulseUI uses a simple replace method for values in the webhook's Payload property. At this moment we support two bookmarks:

[[LIVENESS]] The name of the liveness that returns Down.

[[FAILURE]] A detail message with the failure.

The web hooks section contains more information and webhooks samples for Microsoft Teams, Azure Functions, Slack and more.


BeatPulse wouldn't be possible without the time and effort of its contributors. The team is made up of Unai Zorrilla Castro @unaizorrilla, Luis Ruiz Pavón @lurumad, Carlos Landeras @carloslanderas and Eduard Tomás @eiximenis.

Our valued committers are: Hugo Biarge @hbiarge, Matt Channer @mattchanner, Luis Fraile @lfraile, Bradley Grainger @bgrainger,Mahamadou Camara @poumup.

If you want to contribute to a project and make it better, your help is very welcome. You can contribute with helpful bug reports, feature request and also new features with pull requests.

  1. Read and follow the Don't push your pull requests
  2. Build.ps1 is working on local and AppVeyor.
  3. Follow the code guidelines and conventions.
  4. New features are not only code, tests and documentation are also mandatory.
You can’t perform that action at this time.