How to setup the Crisp Status Local service?
If you're using Crisp Status to monitor nodes in local
mode, you will need to run a Crisp Status Local service on your own infrastructure.
Crisp Status Local is a daemon that you need to install on a server of yours in the event you have local nodes to monitor (ie. private HTTP, TCP or ICMP hosts).
local
nodes altogether. Do not run multiple instances of Crisp Status Local with the same token
, as it will result in a complete monitoring mess (ie. nodes going up and down in a row).Setup the service
To setup the Crisp Status Local service, follow the installation instructions available on the Crisp Status Local GitHub repository.
Get your reporter token
When configuring your Crisp Status Local service, you'll need your private token
value. It lets your service access the Crisp Status Reporter API, to retrieve the list of node replicas to check, and report health status.
You can retrieve the token from your Crisp Status settings here:
- Go to your Crisp Dashboard
- Go to Settings, then click on Status Page
- Open the "Configure your Status Reporter" section
- Copy your secret token
Updated on: 03/03/2025
Thank you!