Prtg Network Monitor Documentation

[Walda Caesar]

SpecificallyI'm looking for information about the functions in the PRTG Python library. The example script located within the PRTG installation imports two functions (prtg.sensor.result.CustomSensorResult and prtg.sensor.units.ValueUnit) but are there more? Does documentation exist for the two functions mentioned?

To answer my specific question regarding CustomUnits, I found this: @param unit: The sensor value's unit. If the unit is not a known PRTGunit, the unit is set to CUSTOM and the custom unit isset to the string in unit. Default is CUSTOM with customunit set to '#'.@type unit: ValueUnit or str I also realised after posting, the value of "unit" is only read on the first scan. I was able to define the value in the PRTG management interface afterwards.

we have no documentation from more functions build in our Python library. However, we have an guide how to import modules in python scripts which will access you to write modules or import existing one to receive more function.

PRTG Network Monitor monitors your network and requires no third party software. Conducting a quick ad-hoc download, you do not need to fill web forms and will not have any registration hassles. The installation process requires only a few minutes, as well as the first configuration which is mainly done automatically. The initial setup is achieved by an interactive guidance by the software.

PRTG Network Monitor supports monitoring up to 20,000 thousand sensors per installation. It can optionally work with multiple remote probes to monitor multiple sites or network segments from one central core installation, and to distribute high loads. You can also configure fail-safe monitoring using a cluster installation to perform automatic failovers. Single failover installations are allowed with every PRTG license.

The software is based on Paessler's reliable monitoring technology, which has been constantly improved since 1997 and is already used by more than 150,000 users around the world every day. An outstanding support ensures that your inquiries are answered within one business day to ensure best possible network monitoring. Attractive licensing packages from freeware (up to 100 sensors) to enterprise level (with thousands of sensors) make sure that every user finds the proper solution.

This manual section provides an overview about the structure of PRTG's web interface. The main focus is on the Devices view which you can select via the main menu bar, because there you see your monitoring results at a glance so you will widely use it.

Once you have run through the Configuration Guru, you will see PRTG's welcome page as default after you log in to the web interface. You can set another homepage in your account settings, section Web Interface.

The header area of the web interface is both base for the most important information of your installation and starting point for all actions. You can view the global status and navigate through the web interface using the main menu.

Note: This documentation refers to the PRTG System Administrator user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default.

This area shows the aggregated status of all sensors you have configured for monitoring, divided into different sensor states. Depending on the sensors' status you will see colored boxes with numbers which symbolize the sensors. For example, you can see how many sensors are in Up, Down, or Warning state. Click on a box to view a list of all sensors in the respective status. For a detailed description, please see Sensor States section.

In the page header under the global header area, you see the name of the current object and the page content underneath. When displaying a group, aggregated sensor states are shown in a sensor bar and there is an option to change the tree view. Furthermore, various information about the current object is reported here.

On the right side are icons which allow you to perform several actions. Depending on the currently viewed page within PRTG, you can pause (and resume) or delete this object, add another object (for example, a sensor to a device), send a link to the current page per email, perform an immediate scan, open a related ticket, and show the corresponding object history page. On device lists, there is also a button to open the QR codes of all devices in this list in a printable layout.

This element is the QR code for the current page. If you have PRTG for Android, you can scan the code to get the current object directly on your mobile device. Click on it to open a printable version.

Depending on the selected object type, the page header bar shows additional information. All objects underneath the Root group indicate their dependency, groups and devices show the past time since the last auto-discovery was run on the selected object (hover to show the exact date and time), and devices show their respective DNS/IP address as defined in the device settings. Sensors show additional monitoring statistics.

Using the different circle symbols in the page header bar, you can define how much space is used to show devices and sensors in a hierarchical tree structure. In four steps, you can switch from a very condensed view (small circle; marked with 1 in the screenshot) up to an extra large view (big circle; marked with 4 in the screenshot).

There are two additional options to the simple tree views which enable you to display the status of all sensors of your entire installation in a single overview. Click on one of the icons to change the view:

Sunburst View (5)

The sunburst view shows your entire installation in one circle diagram. The groups are represented as inner circles, and all devices contained within a group are shown as 'cake slices' attached to the outside of a circle element.

The page content of the general layout varies dependent on the selected object. It shows information about the current object and all other objects underneath in the tree hierarchy. The deeper down in the hierarchy you select an object, the more detailed is the displayed information.

By default, a Probe Device is created in the device tree on the local probe. It represents the probe system running with your PRTG installation. PRTG automatically monitors the system health of the core server and each probe in order to discover overloading situations that may distort monitoring results. To monitor the system status of the probe computer, PRTG automatically creates a few sensors. These include a Core/Probe Health Sensor, a WMI sensor that measures disk usage, and a bandwidth sensor for all installed network cards. It is recommended to keep these sensors, but you can optionally remove all except the Core/Probe Health sensor. In a cluster installation, PRTG also creates a Cluster Probe Device with a Cluster Probe Health Sensor that monitors the cluster's system health.

Another one-click option for adding/removing favorites or setting the priority for a selected device or sensor is given in the page header bar right to the object name (please see screen number 1 in that subsection). Simply click on the flag for favorites or on a star for priority.

A black flag means that the respective object is a favorite already; clicking on the black flag will remove the object from favorites. A gray flag indicates that it is not a favorite yet. Please see also Priority and Favorites for this concern.

I've enabled SNMP in Organization>Settings, enabled SNMP Traps in Alerts, and opened the port in the firewall but whatever I do I cannot get the PRTG instance to register that the devices exist expect for the default ping sensor. I've tried following the instructions in the Meraki KB article on the subject, ( _Administration/Monitoring_and_Reporting/SNMP_Overview_and_C...) but PRTG still cannot communicate with any of my devices.

I am really confused where Meraki says "by default Meraki devices cannot be polled via SNMP from outside the local IP network" but yet earlier in the documentation it says that the hostname for all SNMP requests should be "snmp.meraki.com" so I can't see how those two statements can match up?

Either way, using the MIB file downloaded from the portal and uploaded into the PRTG system, or using the built-in MIB's doesn't work and I just get errors. I've even tried to test the devices from a PC within the network by using Paessler SNMP Tester. This is what I get each time:

The access points don't give much of anything for SNMP, the switches are even less. If you snmp walk them you will see the return list is very short. Might be able to get more with the dashboard api but I haven't attempted it yet with PRTG.

PRTG Network Monitor is a server up-time and utilization, networkmonitoring, and bandwidth usage software package for serverinfrastructure. It can monitor and classify bandwidth usage in anetwork using SNMP, packet sniffing, and Netflow. The following guidewalks you through installing and configuring this integration.

Make sure you have the latest version of Powershell running in your PRTG environment for the integration script to workbest. You can check which version of Powershell you currently have byrunning the following command line:

3a8082e126