Example 1: Overall print system health monitoring
Fast River School is a small school with approximately 200 students. They have a single print server and 5 printers. They would like to monitor the status of PaperCut NG/MF to minimize outages to their printing services. Fast River does not have its own IT support so would like to enlist an IT consultant to set up a basic monitoring system that will track PaperCut NG/MF’s health. The IT consultants they have hired have their own monitoring tool that can consume only HTTP response codes.
The IT consultant has recommended setting up the following:
Requirement 1: Immediate notification when PaperCut NG/MF is not functioning correctly
The IT consultant wants to receive an immediate email notification when PaperCut NG/MF has an issue preventing it from working. This will allow them to address any outages immediately rather than waiting for someone to report the issue.
Configure the following in your monitoring tool:
Event to trigger alarm state
HTTP response status code = 500
Event to trigger notification
alarm state = 10 minutes
Period during which the alarm is triggered
7 am – 10 pm
This URL returns an HTTP response status code of 500 when one or more of the following occurs:
The Application Server cannot connect to the database.
The number of active database connections is greater than 90%.
There’s less than 1 GB of available disk space.
An invalid license is in use.
The Site Server is offline.
The monitoring tool would trigger an email alert and display a visual representation of the alarm on the dashboard. An example below shows this endpoint in error.