You are here: Administration > Tools - database, server-command scripting, and APIs (Advanced) > Monitor print system health > Example 1: Overall print system health monitoring

Example 1: Overall print system health monitoring

Fast River School is a small school with approximately 200 students. They have a single print serverA print server is a system responsible for hosting print queues and sharing printer resources to desktops. Users submit print jobs to a print server rather then directly to the printer itself. A print server can be a dedicated server but on many networks this server also performs other tasks, such as file serving and 5 printers. They would like to monitor the status of PaperCut NG to minimize outages to their printing services. Fast River do not have their own IT support so would like to enlist an IT consultant to set up a basic monitoring system that will track PaperCut NG'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:


Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.