Plugin: go.d.plugin Module: snmp
Monitor Tripplite PDU (pdu) with Netdata over SNMP. Netdata recognizes the device automatically by its sysObjectID (recognized across 1 device identifiers) and collects the metrics this profile declares — on top of the generic SNMP baseline — with no manual OID configuration.
Netdata’s SNMP collector matches the device to the tripplite-pdu.yaml profile via sysObjectID/sysDescr, then polls the OIDs it declares.
This integration is supported on all platforms.
This integration supports multiple instances configured side-by-side.
Auto-detected as Tripplite PDU via sysObjectID/sysDescr.
The default configuration for this integration does not impose any limits.
The default configuration for this integration is not expected to impose a significant performance impact on the system.
You can configure the snmp collector in two ways:
| Method | Best for | How to |
|---|---|---|
| UI | Fast setup without editing files | Go to Nodes → Configure this node → Collectors → Jobs, search for snmp, then click + to add a job. |
| File | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit go.d/snmp.conf and add a job. |
Important
UI configuration requires paid Netdata Cloud plan.
SNMP must be enabled on the device and reachable from the Netdata Agent acting as the site’s SNMP hub.
Configure the SNMP collector with the device hostname and SNMP credentials. See the SNMP collector reference for all options.
Configure the snmp collector from the Netdata web interface:
The configuration file name for this integration is go.d/snmp.conf.
The file format is YAML. Generally, the structure is:
update_every: 1
autodetection_retry: 0
jobs:
- name: some_name1
- name: some_name2
You can edit the configuration file using the edit-config script from the
Netdata config directory.
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/snmp.conf
There are no configuration examples.
On top of the generic SNMP baseline (the Generic SNMP Device integration — interfaces, system, IP/TCP/UDP, host resources), this Tripplite PDU profile adds the metrics below. Each is collected only where the device exposes the matching OID — inclusion means the profile requests it; availability depends on the device model and software.
19 metrics in 10 groups; each row is a chart context usable in alerts.
| Group | Metrics |
|---|---|
| Environment / Temperature | 2 |
| Hardware / Breaker | 1 |
| Hardware / Device | 1 |
| Hardware / Outlet | 1 |
| Hardware / Output | 1 |
| PowerFlow / Outlet | 3 |
| PowerFlow / Output | 5 |
| PowerFlow / Phase | 1 |
| System / Alarm | 3 |
| System / Uptime | 1 |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_tlpPduDeviceTemperatureC | Cel | per tlp_device_index | The ambient temperature at or near the PDU casing. |
snmp.device_prof_tlpPduDeviceTemperatureF | degF | per tlp_device_index | The ambient temperature at or near the PDU casing. |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_tlpPduBreakerStatus | {status} | per tlp_device_index, tlp_pdu_breaker_index, tlp_pdu_breaker_status | The current state of the bank breaker |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_tlpDeviceStatus | {status} | per tlp_device_index | The currently most critical alarm status for the device |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_tlpPduOutletState | {status} | per tlp_pdu_outlet_name | The current state of the outlet. |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_tlpPduDeviceMainLoadState | {status} | per tlp_device_index | The current state of the main output of the device |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_tlpPduOutletCurrent | mA | per tlp_pdu_outlet_name | The present output current, in hundreths of amps, of a given outlet. |
snmp.device_prof_tlpPduOutletPower | W | per tlp_pdu_outlet_name | The output power of a given outlet. |
snmp.device_prof_tlpPduOutletVoltage | V | per tlp_pdu_outlet_name | The magnitude of the present output voltage for a given outlet. |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_tlpPduDeviceOutputPowerTotal | W | per tlp_device_index | The AC output total power for all circuits. |
snmp.device_prof_tlpPduOutputCurrent | mA | per tlp_device_index, tlp_pdu_output_index, tlp_pdu_output_phase, tlp_pdu_output_phase_type | The output current, in hundreths of amps, for a given phase. |
snmp.device_prof_tlpPduOutputFrequency | Hz | per tlp_device_index, tlp_pdu_output_index, tlp_pdu_output_phase, tlp_pdu_output_phase_type | The present output frequency. |
snmp.device_prof_tlpPduOutputSource | {status} | per tlp_device_index, tlp_pdu_output_index, tlp_pdu_output_phase, tlp_pdu_output_phase_type | The present source of output power. |
snmp.device_prof_tlpPduOutputVoltage | V | per tlp_device_index, tlp_pdu_output_index, tlp_pdu_output_phase, tlp_pdu_output_phase_type | The magnitude of the present output voltage for a given output line. |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_tlpPduDevicePhaseImbalance | % | per tlp_device_index | The percentage of imbalance of the three phases. |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_tlpAlarmAcknowledged | {status} | per tlp_alarm_index | Denotes whether the alarm condition has been acknowledged |
snmp.device_prof_tlpAlarmState | {status} | per tlp_alarm_index | The current state of this alarm condition |
snmp.device_prof_tlpAlarmsPresent | {alarm} | device | The present number of active alarm conditions. |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_systemUptime | s | device | Time since the system was last rebooted or powered on. |
There are no alerts configured by default for this integration.
Want a personalised demo of Netdata for your use case?