Skip to main content

Servertech Pdu4

Servertech Pdu4

Plugin: go.d.plugin Module: snmp

Maintained by Netdata

Overview​

Monitor Servertech Pdu4 (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 servertech-pdu4.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.

Default Behavior​

Auto-Detection​

Auto-detected as Servertech Pdu4 via sysObjectID/sysDescr.

Limits​

The default configuration for this integration does not impose any limits.

Performance Impact​

The default configuration for this integration is not expected to impose a significant performance impact on the system.

Setup​

You can configure the snmp collector in two ways:

MethodBest forHow to
UIFast setup without editing filesGo to Nodes → Configure this node → Collectors → Jobs, search for snmp, then click + to add a job.
FileIf 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.

Prerequisites​

SNMP access​

SNMP must be enabled on the device and reachable from the Netdata Agent acting as the site's SNMP hub.

Configuration​

Options​

Configure the SNMP collector with the device hostname and SNMP credentials. See the SNMP collector reference for all options.

via UI​

Configure the snmp collector from the Netdata web interface:

  1. Go to Nodes.
  2. Select the node where you want the snmp data-collection job to run and click the ⚙ (Configure this node). That node will run the data collection.
  3. The Collectors → Jobs view opens by default.
  4. In the Search box, type snmp (or scroll the list) to locate the snmp collector.
  5. Click the + next to the snmp collector to add a new job.
  6. Fill in the job fields, then click Test to verify the configuration and Submit to save.
    • Test runs the job with the provided settings and shows whether data can be collected.
    • If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.

via File​

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
Examples​

There are no configuration examples.

Alerts​

There are no alerts configured by default for this integration.

Metrics​

On top of the generic SNMP baseline (the Generic SNMP Device integration — interfaces, system, IP/TCP/UDP, host resources), this Servertech Pdu4 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.

45 metrics in 13 groups; each row is a chart context usable in alerts.

GroupMetrics
Hardware / Branch2
Hardware / InputCord2
Hardware / Line2
Hardware / OCP1
Hardware / Outlet3
Hardware / Phase2
Hardware / Sensor4
Hardware / Unit1
PowerFlow / Branch3
PowerFlow / InputCord10
PowerFlow / Line3
PowerFlow / Phase11
System / Uptime1

Hardware / Branch​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4BranchState{status}per servertech_sentry4_st4_branch_id, servertech_sentry4_st4_branch_labelBranch power state
snmp.device_prof_servertech_sentry4_st4BranchStatus{status}per servertech_sentry4_st4_branch_id, servertech_sentry4_st4_branch_labelBranch operational status

Hardware / InputCord​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4InputCordState{status}per servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeInput cord power state
snmp.device_prof_servertech_sentry4_st4InputCordStatus{status}per servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeInput cord operational status

Hardware / Line​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4LineState{status}per servertech_sentry4_st4_line_id, servertech_sentry4_st4_line_labelLine power state
snmp.device_prof_servertech_sentry4_st4LineStatus{status}per servertech_sentry4_st4_line_id, servertech_sentry4_st4_line_labelLine operational status

Hardware / OCP​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4OcpStatus{status}per servertech_sentry4_st4_ocp_id, servertech_sentry4_st4_ocp_label, servertech_sentry4_st4_ocp_typeOvercurrent protection device status

Hardware / Outlet​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4OutletState{status}per servertech_sentry4_st4_outlet_id, servertech_sentry4_st4_outlet_nameOutlet power state
snmp.device_prof_servertech_sentry4_st4OutletStatus{status}per servertech_sentry4_st4_outlet_id, servertech_sentry4_st4_outlet_nameOutlet operational status
snmp.device_prof_servertech_sentry4_st4OutletWakeupState{status}per servertech_sentry4_st4_outlet_id, servertech_sentry4_st4_outlet_nameOutlet wakeup state configuration

Hardware / Phase​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4PhaseState{status}per servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelPhase power state
snmp.device_prof_sservertech_sentry4_st4PhaseStatus{status}per servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelPhase operational status

Hardware / Sensor​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4HumidSensorStatus{status}per servertech_sentry4_st4_humid_sensor_id, servertech_sentry4_st4_humid_sensor_nameHumidity sensor status
snmp.device_prof_servertech_sentry4_st4HumidSensorValue%per servertech_sentry4_st4_humid_sensor_id, servertech_sentry4_st4_humid_sensor_nameHumidity sensor value
snmp.device_prof_servertech_sentry4_st4TempSensorStatus{status}per servertech_sentry4_st4_temp_sensor_id, servertech_sentry4_st4_temp_sensor_nameTemperature sensor status
snmp.device_prof_servertech_sentry4_st4TempSensorValueCelper servertech_sentry4_st4_temp_sensor_id, servertech_sentry4_st4_temp_sensor_nameTemperature sensor value

Hardware / Unit​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4UnitStatus{status}per servertech_sentry4_st4_unit_id, servertech_sentry4_st4_unit_name, servertech_sentry4_st4_unit_typeUnit operational status

PowerFlow / Branch​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4BranchCurrentAper servertech_sentry4_st4_branch_id, servertech_sentry4_st4_branch_labelCurrent of the branch
snmp.device_prof_servertech_sentry4_st4BranchCurrentStatus{status}per servertech_sentry4_st4_branch_id, servertech_sentry4_st4_branch_labelBranch current status
snmp.device_prof_servertech_sentry4_st4BranchCurrentUtilizedAper servertech_sentry4_st4_branch_id, servertech_sentry4_st4_branch_labelUtilized current of the branch

PowerFlow / InputCord​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4InputCordActivePowerWper servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeActive power of the input cord
snmp.device_prof_servertech_sentry4_st4InputCordActivePowerStatus{status}per servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeInput cord active power status
snmp.device_prof_servertech_sentry4_st4InputCordApparentPowerVAper servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeApparent power of the input cord
snmp.device_prof_servertech_sentry4_st4InputCordApparentPowerStatus{status}per servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeInput cord apparent power status
snmp.device_prof_servertech_sentry4_st4InputCordEnergyWhper servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeEnergy consumed by the input cord
snmp.device_prof_servertech_sentry4_st4InputCordFrequencyHzper servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeFrequency of the input cord
snmp.device_prof_servertech_sentry4_st4InputCordOutOfBalance%per servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeOut of balance measurement of the input cord
snmp.device_prof_servertech_sentry4_st4InputCordOutOfBalanceStatus{status}per servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeInput cord out of balance status
snmp.device_prof_servertech_sentry4_st4InputCordPowerFactorStatus{status}per servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typeInput cord power factor status
snmp.device_prof_servertech_sentry4_st4InputCordPowerUtilizedWper servertech_sentry4_st4_input_cord_id, servertech_sentry4_st4_input_cord_name, servertech_sentry4_st4_input_cord_inlet_typePower utilized by the input cord

PowerFlow / Line​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4LineCurrentAper servertech_sentry4_st4_line_id, servertech_sentry4_st4_line_labelCurrent of the line
snmp.device_prof_servertech_sentry4_st4LineCurrentStatus{status}per servertech_sentry4_st4_line_id, servertech_sentry4_st4_line_labelLine current status
snmp.device_prof_servertech_sentry4_st4LineCurrentUtilizedAper servertech_sentry4_st4_line_id, servertech_sentry4_st4_line_labelUtilized current of the line

PowerFlow / Phase​

Metric (chart context)UnitScopeDescription
snmp.device_prof_servertech_sentry4_st4PhaseActivePowerWper servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelActive power of the phase
snmp.device_prof_servertech_sentry4_st4PhaseApparentPowerVAper servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelApparent power of the phase
snmp.device_prof_servertech_sentry4_st4PhaseCurrentAper servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelCurrent of the phase
snmp.device_prof_servertech_sentry4_st4PhaseCurrentCrestFactor1per servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelCurrent crest factor of the phase
snmp.device_prof_servertech_sentry4_st4PhaseEnergyWhper servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelEnergy consumed by the phase
snmp.device_prof_servertech_sentry4_st4PhasePowerFactor1per servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelPower factor of the phase
snmp.device_prof_servertech_sentry4_st4PhasePowerFactorStatus{status}per servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelPhase power factor status
snmp.device_prof_servertech_sentry4_st4PhaseReactance{status}per servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelPhase reactance type
snmp.device_prof_servertech_sentry4_st4PhaseVoltageVper servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelVoltage of the phase
snmp.device_prof_servertech_sentry4_st4PhaseVoltageDeviationVper servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelVoltage deviation of the phase
snmp.device_prof_servertech_sentry4_st4PhaseVoltageStatus{status}per servertech_sentry4_st4_phase_id, servertech_sentry4_st4_phase_labelPhase voltage status

System / Uptime​

Metric (chart context)UnitScopeDescription
snmp.device_prof_systemUptimesdeviceTime since the system was last rebooted or powered on.

Troubleshooting​

Other Problems​

Collect Diagnostics for Netdata Support​

For SNMP metrics, BGP, licensing, or topology issues, follow Collect SNMP troubleshooting data to include built-in diagnostics in a support bundle. SNMP evidence is unsanitized; share the bundle through a restricted Netdata Support ticket.


Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.