CompanyServicesBlogDownloads
Search…
1.12.3
Welcome
Getting Started
Downloads
VerneMQ / MQTT Introduction
Installing VerneMQ
Installing on Debian and Ubuntu
Installing on CentOS and RHEL
Running VerneMQ using Docker
Configuring VerneMQ
Introduction
The VerneMQ conf file
Auth using files
Auth using a database
MQTT Options
MQTT Listeners
HTTP Listeners
Non-standard MQTT options
Websockets
Logging
Consumer session balancing
Plugins
Shared subscriptions
Advanced Options
Storage
MQTT Bridge
VerneMQ Clustering
Introduction
Inter-node Communication
Dealing with Netsplits
Live Administration
Introduction
Inspecting and managing sessions
Retained messages
Live reconfiguration
Managing Listeners
HTTP API
Tracing
Monitoring
Introduction
$SYSTree
Graphite
Netdata
Prometheus
Health Checker
Status Page
Plugin Development
Introduction
Session lifecycle
Subscribe Flow
Publish Flow
Enhanced Auth Flow
Erlang Boilerplate
Lua Scripting Support
Webhooks
Misc
Loadtesting VerneMQ
Not a tuning guide
Change Open File Limits
Guides
A typical VerneMQ deployment
VerneMQ on Kubernetes
Loadtesting VerneMQ
Clustering during development
Not a tuning guide
Change Open File Limits
Powered By GitBook
Health Checker
The VerneMQ health checker
A simple way to gauge the health of a VerneMQ cluster is to query the /health path on the HTTP listener.
The health check will return 200 when VerneMQ is accepting connections and is joined with the cluster (for clustered setups). 503 will be returned in case any of those two conditions are not met.
Monitoring - Previous
Prometheus
Next - Monitoring
Status Page
Last modified 5mo ago
Export as PDF
Copy link
Edit on GitHub