Advanced Health Monitoring using PRTG

KB Home   |   Advanced Health Monitoring using PRTG

Main.AdvancedMonitorPRTG History

Hide minor edits - Show changes to output

November 16, 2018, at 06:49 AM by Aaron Pouliot - Added category - Health Monitoring
Changed lines 196-198 from:
''Categories:''
----
[-Keywords: -]
to:
''Categories:'' [[Category.HealthMonitoring|+]]
May 30, 2016, at 08:00 AM by Mel Zouzoulas -
Changed line 193 from:
For more endpoints, including printers and statistics, see the PaperCut manual.
to:
For more endpoints, including printers and statistics, see the [[https://www.papercut.com/products/ng/manual/home.html|PaperCut Manual]]. \\
May 30, 2016, at 05:30 AM by Mel Zouzoulas -
Changed lines 12-13 from:
For the experienced SysAdmin, we’ve put together a set of advanced monitoring interfaces for you to query against. \\
These advanced monitoring interfaces return JSON for your monitorng tool to parse. This lets you choose exactly when you want to be alerted to potential concerning incidents in your print environment.\\
to:
For the experienced `SysAdmin, we’ve put together a set of advanced monitoring interfaces for you to query against. \\
These advanced monitoring interfaces return JSON for your monitoring tool to parse. This lets you choose exactly when you want to be alerted to potential concerning incidents in your print environment.\\
Changed lines 12-15 from:
For SysAdmins who have not set up monitoring before, we’ve put together this simple print system monitoring article to take you through the setup. \\
This method of monitoring provides an Up/Down status by returning HTTP response status codes
*200 = OK
*500 = Error
\\
to:
For the experienced SysAdmin, we’ve put together a set of advanced monitoring interfaces for you to query against. \\
These advanced monitoring interfaces return JSON for your monitorng tool to parse. This lets you choose exactly when you want to be alerted to potential concerning incidents in your print environment.
\\
May 25, 2016, at 03:03 PM by Shane Higgins -
Changed line 200 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: -]
May 25, 2016, at 03:02 PM by Shane Higgins -
Changed line 198 from:
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
to:
''Categories:''
May 25, 2016, at 02:59 PM by Shane Higgins - Initial Document
Added lines 1-200:
(:title Advanced Health Monitoring using PRTG:)

In PaperCut 16.1, we’ve enhanced the Print System Health interface.\\

Maximize your print uptime by proactively maintaining your print environment using PRTG. You can:

*trigger alarms as soon as outages occur rather than waiting for someone to report an issue
*monitor real-time printing activity to identify changes in printing behavior
*monitor trends in printing resources and usage over time so you can plan for expansion to address bottlenecks before they occur.
*monitor printer and device inactivity

For SysAdmins who have not set up monitoring before, we’ve put together this simple print system monitoring article to take you through the setup. \\
This method of monitoring provides an Up/Down status by returning HTTP response status codes
*200 = OK
*500 = Error\\

For more information on the types and use of these URLs (endpoints), see the PaperCut manual.

To demonstrate using [[https://www.paessler.com/prtg |PRTG Network Monitor]] and the simple Print System Health interface at a high level, you will set up a sensor to monitor the overall state of your PaperCut Server license.
You should get a green [ok] or red [error] status from PRTG once you have finished.

To achieve this you need to complete a few overall tasks:
#Check your server access
#Download and install PRTG on an appropriate server.
#Create a device as a means to group your sensors.
#Create a sensor to monitor a status endpoint of the server.
#Set up notifications.
#Configure the mail server settings in PRTG if needed.

!!%maroon%Step One%%
Pick a server in your environment that has network visibility of the PaperCut server you want to monitor.\\
Put simply, the server needs to be able to successfully access this URL:
[@http://serveraddress:9191/api/health/license/status@]\\
If you’re running PaperCut 16.1 or later, the server is online, and you can’t access this URL, check that:
*The hostname can be resolved by your DNS (or that the IP address is correct)
*TCP communications over port 9191 are allowed by your firewall
*The port that the PaperCut server has been configured to use matches the port in the URL\\
\\

!!%maroon%Step Two%%
Download and install PRTG Network Monitor on this server.
When done, it should automatically open up its web interface, and start auto-discovering objects in your environment visible over the network.\\
It may look something like this:

Attach:Just_installed.png\\
\\

!!%maroon%Step Three%%

Add in a "device"  This will help to organise the interface, providing a place to add all the needed sensors.\\
Either:
*Identify your PaperCut server in this structure,\\
 or
*if the server has not been auto-detected, click Add Device to manually add it.\\

In the screenshots below, the network device (components PRTG discovers on your network) has been removed to make it cleaner to look at for this walk through.

Right-click “127.0.0.1”; then select Add Device from the menu.
\\

Attach:Add_device.png
\\

Give the new device a descriptive name, and provided the relevant IP Address/DNS Name for reaching it.
\\

Attach:Device_set-up.png
\\

Now you have added the device, it should look like this:
\\

Attach:Device_no_sensors.png
\\

!!%maroon%Step Four%%

Time to add in a sensor so we can monitor the utilization of Papercuts' allocated memory.

Click your server.\\
Click “Add Sensor”.\\
This is where you configure the particular element you want to monitor. \\
In the Search box at the top of the page,  enter XML/REST to filter the list of available sensor types down to the one you want.

Attach:xml_rest_sensor.png

Click Add this to open the sensor settings dialog.\\

The following fields will need to be filled out.\\
\\
'''''Sensor Name:-''''' The title of the sensor\\
'''''URL:-''''' The base address of the endpoint we want to monitor\\
'''''XML Node (and optional property):-''''' enter the node descriptor/property\\
'''''HTTP Headers:-'''''the Authorization key copied from copied from Options ->Advanced ->System Health Monitoring section\\
'''''Unit String:-''''' Allows us to see the value in its true form\\
\\
[+%purple%For this walk though add the following sensor settings:%%+]\\
\\
'''''Sensor Name:-''''' PaperCut Internal Memory Usage\\
'''''URL:-''''' [@http://servername:9191/api/health@]\\
'''''XML Node (and optional property):-''''' systemMetrics/jvmMemoryUsedPercentage\\
'''''HTTP Headers:-''''' add in your Authorization key\\
'''''Unit String:-''''' Change to "%"\\
\\
 See below then '''Click Continue.'''

Attach:xml_sensor_settings.png

Once added, the new sensor is gray but don't despair, that will go away.\\
After about 60 seconds, if the URL is correct, the sensor changes to green.

Attach:Adv_sensor_green.png
\\
Clicking the sensor will present you with a green meter displaying the current usage:

Attach:Adv_Sensor_no_limits.png
\\
This is not as informative as it could be.  To enhance the readability when we look at it, we need to set-up warnings and limits.
Click on the large '''''Value'''''' section of the screen
Enable the Limits section at the bottom of the screen and for our purposes change:
\\
*Upper Error Limit (%) to 95\\
*Upper Warning Limit (%) to 90\\

\\

You can also add error and warning messages in that will be meaningful to you.
\\

Attach:limits_for_advanced.png
\\

The sensor should look a little more readable, and allow you to instantly see if there is something amis.

\\

Attach:Adv_Sensor_w_limits.png



!!%maroon%Step Five%%\\

You’re doing well—it’s nearly coffee time, but before then, you had better make sure that if you’re busy doing stuff, your server will let you know that things have got rough.

Click on the PaperCut Internal Memory Usage Sensor\\
Click the Notifications tab.\\
Click Only use the triggers defined below.\\
Click the Add State Trigger button.\\

Attach:state_trigger_button.png

Set the values to meet your needs.
\\

Attach:adv_trigger_settings.png
\\

!!%maroon%Step Six%%\\

Set-up your internal email server if you need to.\\
PRTG has the ability to email you the notification above directly “out of the box”, however if you want to use your own internal SMTP server:\\

Click Setup tab.
Select System Administrator -> Notification delivery.

Attach:Notification_menu.png

In SMTP Delivery Mechanism, select Use SMTP relay server.\\
Enter your SMTP server settings in the following fields:\\
SMTP Relay Server\\
SMTP Relay SMTP Port\\
SMTP Relay Authentication\\
Adjust other fields as needed\\
\\

Attach:SMTP_settings.png
\\

You can test the new email server settings by pushing a test notification:\\
Click Setup -> Account Settings ->Notifications.\\
In the Email and push notification to admin section, click Test.\\
\\

Attach:test_notification.png
\\

If you don’t receive the test email notification, check the Logs tab to work out what might be wrong with your SMTP settings!
\\

!!%maroon%Explore more endpoints%%\\


These indepth collectors can give you unprecedented views into your system, giving you instant warnings for any major issues that might arise, along with data to allow you to analyse the working state of your system.
\\
For more endpoints, including printers and statistics, see the PaperCut manual.

----
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
----
[-Keywords: TODO keywords here if needed-]

Comments

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.

Article last modified on November 16, 2018, at 06:49 AM
Printable View   |   Article History   |   Edit Article