How to setup the Crisp Status Local service?Setup the serviceGet your reporter token

Articles on: Automate

hello

Hello there

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).

A single Crisp Status Local service can run at the same time in your infrastructure. It will monitor configured

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).

nice!

this is a test

To setup the Crisp Status Local service, follow the installation instructions available on the Crisp Status Local GitHub repository.

As we know running a new service in your infrastructure can be sensitive matters, we've made Crisp Status Local open-source. You can thus review the code, modify it and compile it yourself.

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

The token is a chain of alphanumerical characters, separated by dashes.

Updated on: 13/06/2022

Updated on: 04/07/2025