PRTG Manual: SNMP Custom Table Sensor
The SNMP Custom Table sensor monitors entries from a table that is provided via the Simple Network Management Protocol (SNMP). You can create one new sensor per table row. For each sensor, you can define up to ten channels. Each channel shows the value of one defined table column.
The SNMP Library sensor automatically creates SNMP Custom Table sensors when the Management Information Base (MIB) file that you import contains tables.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: SNMP Aangepaste Tabel
- French: Table personnalisée (SNMP)
- German: SNMP (Benutzerdef. Tabelle)
- Japanese: SNMP カスタムテーブル
- Portuguese: Tabela (customizada) (SNMP)
- Russian: Нестандартная таблица SNMP
- Simplified Chinese: SNMP 自定义表
- Spanish: Tabla (personalizado) (SNMP)
- This sensor supports IPv6.
- This sensor has a low performance impact.
- This sensor can use lookups. Select Lookup as Channel #x Unit and define the lookup file in Channel #x Lookup.
- It might not work to query data from a probe device via SNMP (querying localhost, 127.0.0.1, or ::1). Add this device with the IP address that it has in your network and create the sensor on this device instead.
- Knowledge Base: How do I find out which OID I need for an SNMP Custom sensor?
- Knowledge Base: What can I monitor with the SNMP Custom Table sensor?
Setting |
Description |
---|---|
Table |
The sensor shows you the table that the OID returns. Select the table rows that contain the data that you want to monitor. PRTG creates one sensor for each table row that you select. |
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. You can use the placeholders [tablename] and [rowidentifier]. PRTG replaces them with the name of the table and the identifying value of the chosen row respectively. You can select the column that provides the row identifier in the Identification Column option below. You can also enter a valid OID that is part of a different SNMP table, for example, [1.3.6.1.2.1.2.2.1.2], to query information that the current table does not contain. PRTG adds the same index as in the original table to the OID. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.
|
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe.
|
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority ( |
Setting |
Description |
---|---|
Table OID |
Enter the object identifier (OID) of the SNMP table that you want to monitor. The OID must directly point to an object that represents an SNMP table. PRTG creates one SNMP Custom Table sensor for each table row that you select.
|
Setting |
Description |
---|---|
Identifier |
This is the value of the column that you selected as the Identification Column during sensor creation. PRTG also displays it in the sensor name to distinguish it from other sensors you created for the same table with other table rows. |
Identification Column |
Define the identification column for the sensors that you want to create. The sensors use this column to uniquely identify each table row.
|
Channel #x Name |
Enter a name for the channel in which the sensor shows the desired result. Enter a string. |
Channel #x Column |
Select the table column that, together with the table row, points to the value that you want to monitor in this channel. You can choose between the available columns of the table that you monitor. |
Channel #x Value Type |
Select the expected numeric type of the results at the OID:
|
Channel #x Unit |
Define the unit of the data that this sensor receives in this channel:
|
Channel #x Custom Unit |
This setting is only visible if you select the channel unit Custom above. Define a unit for the channel value. Enter a string. |
Channel #x Lookup |
This setting is only visible if you select the channel unit Lookup above. Select a lookup file that you want to use with this channel. |
Channel #2 - #10 |
You can define up to 10 channels. You must define at least one data channel, so you see all available settings for Channel #1. Specify how to handle all other possible channels:
|
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status |
[Value] |
The returned numeric values in up to ten channels per table row |
KNOWLEDGE BASE
How do I find out which OID I need for an SNMP Custom sensor?
What can I monitor with the SNMP Custom Table sensor?
What security features does PRTG include?
My SNMP sensors don’t work. What can I do?
Can I monitor UPS systems complying with the UPS MIB (RFC-1628) with PRTG?