Skip to main content
ComponentsEngine
Availability8.6.9 or later

What Is Monitored

Any OID a device exposes

Analytics, Alerts and Automation

Device trends to alerts

How It Works

Objects, rule and KPI

Deploy

Two wizards per device

Overview

GermainUX reads the values your network and facility devices already publish over SNMP: interface status and traffic, error counters, CPU load, temperature, battery charge, uptime. You choose the OIDs, and the GermainUX Engine polls each device on the schedule you set. The values land next to your application and user data, so a failing uplink or a UPS on battery shows up in the same place as the slow pages it causes. Your team sees device problems as trends and alerts, without a separate network tool.

Any OID, Any Device

Standard MIB-II and IF-MIB values, or vendor OIDs for CPU, temperature and power, from switches, routers, firewalls, UPSs and printers.

Your Schedule

Poll each device as often as the value changes: hourly for uptime, every few minutes for interface errors.

Device Data Next to Application Data

Line up an uplink failure or a power event with the requests, sessions and errors it affected.

Alerts on Device Thresholds

SLAs on the values you poll raise alerts when an interface goes down, errors climb or a battery drains.

Questions It Answers

  • Is the core switch uplink up, and since when have its error counters been climbing?
  • Which devices restarted this week, according to their uptime?
  • Did the UPS switch to battery, and how low did the charge get?
  • Which device is running hot or close to full CPU?
  • Did network traffic change when the application slowed down?
  • Which devices stopped answering SNMP polls?

What Is Monitored

The table below lists common standard OIDs. Replace N with the interface or entry index on your device.

Analytics, Alerts and Automation

Dashboards and Reports

Chart the polled values on dashboards and reports: interface traffic and errors per device, CPU and temperature trends, battery charge, and uptime resets. GermainUX ships the SNMP Overview dashboard as a starting point. In the left menu, select Dashboards > All, and then open SNMP Overview in the Network folder under IT. It shows the values collected per device and SNMP Object, key values such as peak CPU load, peak temperature and lowest UPS charge, and trends for CPU load, temperature, link status, uplink errors, UPS power and battery charge, printer toner and device uptime. Click a chart to open the SNMP Value KPI behind it.
SNMP Overview dashboard showing key values, CPU load, temperature and link status by device, values collected by device, a device health summary and uplink input errors

SNMP Overview Dashboard - GermainUX

Analysis

Click a value on the dashboard to open it in the Analysis screen. The aggregate view compares a value across all devices with the previous period and the last quarter, shows its daily trend, and charts how it relates to other values.
Analysis screen for Peak temperature, comparing the overall maximum SNMP value with the recent period and showing the daily trend and relationships chart

Aggregate Analysis of the Peak Temperature - GermainUX

The instance view explains one reading from one device. It compares the reading with the same SNMP Object on other devices and over time, shows how common the value is, and lists the top differences against a comparable reading. Click Generate AI Summary for a summary in plain language.
Analysis screen for one SNMP value of the device printer-2f, comparing the instance with the population and overall values, with the How Does It Compare and Top Differences sections

Instance Analysis of an SNMP Value - GermainUX

SLAs and Alerts

Set SLAs on the SNMP Value KPI, with one SLA per SNMP Object name, such as interface status not 1, errors above a threshold or charge below 50%, and get an alert by email, SMS, Slack or Teams when one is breached. Outlier detection flags unusual traffic or error spikes.

Automation

When an SLA is breached, an automated action can run a diagnostic script, call an HTTP endpoint or open an incident.

Correlation with Other Technologies

Correlate device values with application and user data, to see whether a network or power event explains slow pages or failed transactions.

How It Works

DeviceSNMP MonitorRuleKPIAlerts
The default rule and the SNMP Value KPI work for any numeric SNMP Object, so you only choose the OIDs. To store text values or process values differently, select your own rule in the component. The GermainUX team can set it up with you.

Before You Start

  • A GermainUX Engine is deployed on a host that can reach each device over UDP, usually port 161. See GermainUX Engine.
  • Each device has SNMP v1 or v2c enabled and answers read requests from the Engine host.
  • You know the device’s read community. If it isn’t public, you store it as credentials in GermainUX, with the community as the password. You can create the credentials while you run the deployment wizard.
  • You know the OIDs to poll and their value types, from the device’s MIB documentation.

Deploy

Deploying takes two wizards: one creates the component with the SNMP Objects, and one deploys it to an Engine for each device.
1

Open the SNMP Monitor Component wizard

In the left menu, go to Settings > Wizards. On the SNMP Monitor Component card, click Add.
2

Name the component and select the rule

3

Add the SNMP Objects

Add one SNMP Object for each value to read.
SNMP Monitor Component wizard showing the Name, OID and Value Class Name fields of an SNMP Object

SNMP Object Step of the SNMP Monitor Component Wizard - GermainUX

Finish the wizard. GermainUX creates the component.
4

Open the SNMP Monitor Deployment wizard

On the Wizards screen, click Add on the SNMP Monitor Deployment card.
5

Select the device

SNMP Monitor Deployment wizard showing the URI and Monitored Software fields

Target Step of the SNMP Monitor Deployment Wizard - GermainUX

6

Select the component and schedule

Finish the wizard. GermainUX deploys the monitor to the Engine, which starts polling on the next scheduled run.
Repeat the deployment wizard for each device that uses the same set of SNMP Objects.

Validate

1

Check the deployment

In the left menu, go to Settings > Wizards. On the SNMP Monitor Deployment card, click Manage to see the deployed SNMP monitors.
2

Test SNMP from the Engine host

On the Engine host, read one of the configured OIDs with the Net-SNMP tools:
Replace COMMUNITY with the device’s read community, for example public, and DEVICE_IP with the device’s address. Use -v1 for an SNMP v1 device. A working device answers with its uptime, for example DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (123456789) 14 days, 6:56:07.89.
3

Find the values in GermainUX

After the next scheduled poll, in the left menu, select Dashboards > All, and then open SNMP Overview in the Network folder under IT. Check that Values by Device and Object lists a value for each numeric SNMP Object of the device.

Troubleshooting

Run the snmpget test from the Engine host. If it times out, check that the device allows SNMP from the Engine’s address, and that no firewall blocks UDP port 161 between them. If the test works, check that the deployment’s SNMP Version and Credentials match the version and community you tested with, and that the component’s Rules field selects snmp-default.drl or your own rule.
The device didn’t return that OID. Check the OID against the device’s MIB, including the interface or entry index at the end, with snmpget from the Engine host.
The default rule stores only numeric values and skips text, such as a system description. To keep text values, select your own rule in the component’s Rules field. For a number, set the SNMP Object’s Value Class Name to Integer or Long.
Interface octet and error OIDs are counters that increase until the device restarts. Chart or alert on the change between polls rather than the raw value.

Security and Privacy

SNMP monitoring data includes:
  • Infrastructure data: device host names and IP addresses, interface indexes, and the values of the configured OIDs
  • Free text: text values, such as system descriptions or contact and location fields, when your own rule stores them. The default rule skips them. They contain whatever the device’s administrator entered, so treat them as possibly containing personal or customer data.
SNMP v1 and v2c send the community string unencrypted. Store a community other than public as credentials in GermainUX, and limit SNMP read access on each device to the Engine host’s address. To mask, anonymize or exclude this data, see Data Privacy.

Network Observability

Connectivity, latency and interfaces

Rules

Analyze data as it arrives

Automation

More Automation Features

Get Help

SNMP monitoring is set up for the devices and values that matter in your network. The GermainUX team can help you choose the OIDs, set up custom rules and dashboards, and define the SLAs and alerts.

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't Find What You Need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.