Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

CUPS

This SAM application monitor template assesses the status and performance of a CUPS service installed on a Linux/Unix system. Perl scripts are used for retrieving performance data.

This template supports the SolarWinds Platform Agent for Linux.

Prerequisites

SSH and Perl are installed on the target server.

The user account used to monitor CUPS must have read access (generally restricted to root access) to the following files:

  • /var/log/cups/page_log
  • /var/log/cups/error_log

Credentials

Root credentials on the target server.

Component monitors

Daemon CUPS status

Returns the status of a Linux/Unix print server daemon.

Possible values:

  • 0 - CUPS daemon is stopped.
  • 1 - CUPS daemon is running.

Print queue

Returns the current length of the default print queue.

Total pages printed

Returns the number of printed pages by retrieving data from the CUPS page_log file.

New emergency messages in CUPS error log

Returns the number of new emergency messages by retrieving data from the CUPS error_log file. All emergency events begin with the “X” symbol.

This monitor should be zero all times. If it is not, you should manually examine this log file.

New warning messages in CUPS error log

Returns the number of new warning messages by retrieving data from the CUPS error_log file. All emergency events begin with the “W” symbol.

This monitor should be zero all times. If it is not, you should manually examine this log file.

New alert messages in CUPS error log

Returns the number of new alert messages by retrieving data from the CUPS error_log file. All emergency events begin with the “A” symbol.

This monitor should be zero all times. If it is not, you should manually examine this log file.

New critical error messages in CUPS error log

Returns the number of new critical error messages by retrieving data from the CUPS error_log file. All emergency events begin with the “C” symbol.

This monitor should be zero all times. If it is not, you should manually examine this log file.

CUPS listening TCP port

Tests the ability of a CUPS service to accept incoming sessions.

By default, it monitors the TCP port 631. If your CUPS server listens on another port, you should manually change it.