Skip to main content
Cachet’s “beacon” system is an optional telemetry system that allows you to send anonymous usage data to Cachet. This data helps us understand how you use Cachet and how we can improve it.

​
Configuration

Cachet’s beacon is enabled by default. If you’d prefer not to send any usage data, you can opt out by setting the CACHET_BEACON environment variable to false.
.env
If you’re limiting outbound requests on your server and you’d like to keep the beacon enabled, you’ll need to allow outbound requests to https://cachethq.io.

​
Configuring the scheduler

Cachet automatically registers the cachet:beacon command to run daily at 00:00. You will need to configure your server to run the scheduler every minute using a cron job. To do so, add the following cron entry:
/etc/crontab
Be sure to replace /path/to/cachet with the actual path to your Cachet installation.

​
What data does Cachet collect?

The beacon collects the following data:
  • Install ID: An anonymous identifier for your Cachet installation.
  • Cachet Version: The version of Cachet you’re running.
  • Docker: Whether you’re running Cachet in a Docker container.
  • Database: The type of database you’re using.
  • Usage Data: How you’re using Cachet, such as the number of incidents, components, subscribers, etc.