> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://staging.chrisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

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

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

# Setup the service

**To setup the Crisp Status Local service, follow the installation instructions available on the [Crisp Status Local GitHub repository](https://github.com/crisp-im/crisp-status-local).**

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

# 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:**

1. Go to your [Crisp Dashboard](https://app.crisp.chat/)  
2. Go to Settings, then click on Status Page  
3. Open the "Configure your Status Reporter" section  
4. Copy your secret token

|| The token is a chain of alpha-numerical characters, separated by dashes.