Pulsar Heartbeat monitors Pulsar cluster availability, tracks latency of Pulsar message pubsub, and reports failures of the Pulsar cluster. It produces synthetic workloads to measure end-to-end message pubsub latency.
It is a cloud native application that can be installed by Helm within the Pulsar Kubernetes cluster.
Here is a list of features that Pulsar Heartbeat supports.
- monitor Pulsar admin REST API endpoint
- measure end-to-end message latency from producing to consuming messages
- for latency measure, it can produce a list of messages with user specified payload size and the number of messages
- measure average latency over a list of messages
- detect out of order delivery of a list of generated messages
- measure a single message latency over the websocket interface
- measure message latency generated by Pulsar function
- monitor instance availability of broker, proxy, bookkeeper, and zookeeper in a Pulsar Kubernetes cluster
- monitor individual Pulsar broker's health
- Pulsar function trigger over HTTP interface
- incident alert with OpsGenie with automatic alert clear and deduplication
- customer configurable alert threshold and probe test interval
- tracking analytics and usage
- dead man's snitch heartbeat monitor with OpsGenie
- alert on Slack
- monitor multiple Pulsar clusters (with no kubernetes pods monitoring)
- co-resident monitoring within the same Pulsar Kubernetes cluster
This is a data driven tool that sources configuration from a yaml or json file. Here is a template. The configuration json file can be specified in the overwrite order of
- an environment variable
PULSAR_OPS_MONITOR_CFG - an command line argument
./pulsar-heartbeat -config /path/to/pulsar_ops_monitor_config.yml - A default path to
../config/runtime.yml
This tool exposes Prometheus compliant metrics at \metrics endpoint for scraping. The exported metrics are:
| Name | Type | Description |
|---|---|---|
| pulsar_pubsub_latency_ms | gauge | end to end message pub and sub latency in milliseconds |
| pulsar_pubsub_latency_ms_hst | summary | end to end message latency histogram summary over 50%, 90%, and 99% samples |
| pulsar_websocket_latency_ms | gauge | end to end message pub and sub latency over websocket interface in milliseconds |
| pulsar_k8s_bookkeeper_offline_counter | gauge | bookkeeper offline instances in Kubernetes cluster |
| pulsar_k8s_broker_offline_counter | gauge | broker offline instances in the Kubernetes cluster |
| pulsar_k8s_proxy_offline_counter | gauge | proxy offline instances in the Kubernetes cluster |
| pulsar_k8s_bookkeeper_zookeeper_counter | gauge | zookeeper offline instances in the Kubernetes cluster |
| pulsar_monitor_counter | counter | the total number of heartbeats counter |
| pulsar_tenant_size | gauge | the number of tenants that can be used as a health indicator of admin interface |
Pulsar heartbeat can be deployed within the same Pulsar Kubernetes cluster. Kubernetes monitoring and individual broker monitoring are only supported within the same Pulsar Kubernetes cluster deployment.
Pulsar Heartbeat's official docker image can be pulled here
$ docker-compose upThe runtime.yml/yaml or runtime.json file must be mounted to /config/runtime.yml as the default configuration path.
Run docker container that exposes Prometheus metrics for collection.
$ docker run -d -it -v $HOME/go/src/github.com/datastax/pulsar-heartbeat/config/runtime-astra.yml:/config/runtime.yml -p 8080:8080 --name=pulsar-heartbeat datastax/pulsar-heartbeat:latestFor the following commands, Helm version 3 is supported.
Pulsar Heartbeat can be installed as part of Pulsar cluster in this Helm chart.
Pulsar Heartbeat can be directly enabled inside the DataStax Pulsar chart.
This script builds the Pulsar Heartbeat Go application, runs code static analysis(golint), runs unit tests, and creates a binary under ./bin/pulsar-heartbeat.
$ ./scripts/ci.sh
This command runs a multi stage build to produce a docker image.
$ make