You can use 3rd party monitoring tools (such as, Nagios, Pingdom, Zabbix) to monitor the PaperCut MF application server status. PaperCut MF provides a System Health API that exposes a REST API endpoint, which monitors the current state of the database. To perform a status check, configure the 3rd party tool to send an HTTP GET request to the following Ping URL: http://[primary_server]:[port]/rpc/api/rest/public/status. This test performs a server check to test if the back end database is available. If the status check succeeds, an HTTP response status 200 is sent back with the following JSON response:
if the database is available
{
"database": {
"online": true,
"reason": ""
}
}
if the database is unavailable (the actual reason might be different to the one in this example)
{
"database": {
"online": false,
"reason": "Cannot connect to the database."
}
}
For more information about the System Health API, see Monitoring Your Servers using the System Health API.
For customers using Site Servers, you can reference those servers directly: http://[site_server]:[port]/rpc/api/rest/public/status
For customers using external tools (such as Pingdom), open the relevant ports in your firewall.
© Copyright 1999-2015. PaperCut Software International Pty Ltd. All rights reserved.