What Is Monitored
Analytics, Alerts and Automation
How It Works
Deploy
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
Your Schedule
Device Data Next to Application Data
Alerts on Device Thresholds
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
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 - 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.
Aggregate Analysis of the Peak Temperature - GermainUX

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 not1, 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
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.Open the SNMP Monitor Component wizard
Name the component and select the rule
Add the SNMP Objects

SNMP Object Step of the SNMP Monitor Component Wizard - GermainUX
Open the SNMP Monitor Deployment wizard
Select the device

Target Step of the SNMP Monitor Deployment Wizard - GermainUX
Select the component and schedule
Validate
Check the deployment
Test SNMP from the Engine host
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.Find the values in GermainUX
Troubleshooting
No values appear after the scheduled poll
No values appear after the scheduled poll
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.One SNMP Object never reports a value
One SNMP Object never reports a value
snmpget from the Engine host.A text value doesn't appear
A text value doesn't appear
Integer or Long.Counters only ever grow
Counters only ever grow
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.
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.
Related Documentation
Network Observability
Rules
Automation
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
Can't Find What You Need?
The content of this document is proprietary to GERMAIN SOFTWARE.

