Skip to main content

Process Monitoring

Read our Process Monitoring documentation for more information on how AppSignal Process Monitoring works.
By default, appsignal-wrap will not send any process monitor events. You can use the --cron or --heartbeat command-line options to enable cron or heartbeat process monitors respectively. The appsignal-wrap tool will use the name provided as the first argument as the process monitor identifier. For example, to report cron process monitor events with backup-script as the process monitor identifier:
appsignal-wrap backup-script --cron -- bash /var/app/backup.sh

Cron process monitors

When using --cron to send cron process monitors, appsignal-wrap will send a start cron process monitor event when the process starts, and a finish cron process monitor event if the process finishes successfully. If the process exits with a failure exit status, appsignal-wrap will not send a finish cron process monitor event.

Heartbeat process monitors

When using --heartbeat to send heartbeat process monitors, appsignal-wrap will send heartbeat process monitor events continuously during the lifetime of the process.

Custom identifier

To send process monitor events to AppSignal with an identifier different from the name provided as the first argument, you can pass a different identifier as an argument to the --cron or --heartbeat command-line options. For example:
appsignal-wrap backup --cron daily-backup -- bash /var/app/backup.sh
In the above example, appsignal-wrap will send cron process monitor events with daily-backup as the process monitor identifier, but will still use backup as the name to identify the process when reporting logs and errors.