> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SNMP Device Monitoring

> Poll switches, routers, UPSs and other SNMP devices on a schedule, and trend, alert and act on the values they report.

Components
[`Engine`](https://docs.germainux.com/deploy/germain-ux-engine)

Availability
8.6.9 or later

> [card] [What Is Monitored](#what-is-monitored)
>
> Any OID a device exposes

> [card] [Analytics, Alerts and Automation](#analytics-alerts-and-automation)
>
> Device trends to alerts

> [card] [How It Works](#how-it-works)
>
> Objects, rule and KPI

> [card] [Deploy](#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.

> [card] 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.

> [card] Your Schedule
>
> Poll each device as often as the value changes: hourly for uptime, every few minutes for interface errors.

> [card] Device Data Next to Application Data
>
> Line up an uplink failure or a power event with the requests, sessions and errors it affected.

> [card] 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

| Area | What GermainUX monitors |
| - | - |
| **Device values** | Any numeric SNMP object the device answers with a GET request: counters, gauges and status codes, one value per configured OID on every poll, stored in the **SNMP Value** KPI by device and SNMP Object |
| **Interfaces** | Status, traffic and error counters per interface, using the standard IF-MIB OIDs |
| **Device health** | CPU load, temperature, memory and uptime, from standard or vendor OIDs |
| **Power and facilities** | UPS battery status and charge, output source, printer supplies, and any other value the device publishes over SNMP |
| **Reachability** | The Engine logs an error for each poll that times out or gets no answer |
| **Engine host** | CPU, memory, disk and network of the host that runs the polls. See [Linux monitoring](https://docs.germainux.com/integrations/linux-redhat-suse-monitoring.md) or [Windows monitoring](https://docs.germainux.com/integrations/windows-monitoring.md). |

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

| Value | OID | Value Class Name |
| - | - | - |
| System uptime (GermainUX converts it to seconds) | `.1.3.6.1.2.1.1.3.0` | Long |
| Interface status (`1` up, `2` down) | `.1.3.6.1.2.1.2.2.1.8.N` | Integer |
| Interface inbound errors | `.1.3.6.1.2.1.2.2.1.14.N` | Long |
| Interface inbound octets (64-bit) | `.1.3.6.1.2.1.31.1.1.1.6.N` | Long |
| Interface outbound octets (64-bit) | `.1.3.6.1.2.1.31.1.1.1.10.N` | Long |
| Processor load (%) | `.1.3.6.1.2.1.25.3.3.1.2.N` | Integer |
| UPS estimated charge remaining (%) | `.1.3.6.1.2.1.33.1.2.4.0` | Integer |
| UPS output source | `.1.3.6.1.2.1.33.1.4.1.0` | Integer |

## Analytics, Alerts and Automation

### Dashboards and Reports

Chart the polled values on [dashboards and reports](https://docs.germainux.com/dashboards/dashboard-and-report.md): 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](https://mintcdn.com/germain-ux/BTdAnP0ToWFYZWJt/images/main/snmp-monitoring/snmp-overview-dashboard.png?fit=max\&auto=format\&n=BTdAnP0ToWFYZWJt\&q=85\&s=25d9a771c68a5513b1ae7bd688462a42)

SNMP Overview Dashboard - GermainUX

### Analysis

Click a value on the dashboard to open it in the [Analysis](https://docs.germainux.com/dashboards/analytics-dashboard/4-analysis-dashboard.md) 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](https://mintcdn.com/germain-ux/BTdAnP0ToWFYZWJt/images/main/snmp-monitoring/snmp-peak-temperature-aggregate-analysis.png?fit=max\&auto=format\&n=BTdAnP0ToWFYZWJt\&q=85\&s=0abc32505359a0254cdee4712c9126c8)

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](https://mintcdn.com/germain-ux/BTdAnP0ToWFYZWJt/images/main/snmp-monitoring/snmp-value-instance-analysis.png?fit=max\&auto=format\&n=BTdAnP0ToWFYZWJt\&q=85\&s=aadb6c70a9d416ff0468ce2886ddf7e7)

Instance Analysis of an SNMP Value - GermainUX

### SLAs and Alerts

Set [SLAs](https://docs.germainux.com/analytics/slas.md) 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](https://docs.germainux.com/automation/notifications.md) by email, SMS, Slack or Teams when one is breached. [Outlier detection](https://docs.germainux.com/analytics/outlier-detection.md) flags unusual traffic or error spikes.

### Automation

When an SLA is breached, an [automated action](https://docs.germainux.com/automation/automated-actions.md) can run a diagnostic script, call an HTTP endpoint or open an incident.

### Correlation with Other Technologies

[Correlate](https://docs.germainux.com/analytics/correlation-and-tracing.md) device values with application and user data, to see whether a network or power event explains slow pages or failed transactions.

## How It Works

Device
SNMP Monitor
Rule
KPI
Alerts

| Part | What it does |
| - | - |
| **SNMP Monitor component** | Lists the SNMP Objects to read: a name, an OID and a value type for each. One component can serve many devices of the same kind. |
| **Rule** | Turns each value the monitor reads into GermainUX data. The default rule, `snmp-default.drl`, stores each numeric value in the **SNMP Value** KPI with the device and the SNMP Object name, and skips text values. You select the rule in the component's **Rules** field. |
| **SNMP Monitor deployment** | Runs the component on a GermainUX Engine against one device, on a schedule. The default schedule is hourly (`0 0 * * * *`). |
| **GermainUX Engine** | Sends one SNMP v1 or v2c GET request with all the component's OIDs to the device's UDP port, `161` by default, and passes each value in the answer to the rule, with the SNMP Object name and the time of the poll. Uptime values are converted to seconds. |
| **SNMP Value KPI** | Makes the values available for dashboards, SLAs and alerts, by device (**System Name**) and SNMP Object (**Name**) |

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](https://docs.germainux.com/deploy/germain-ux-engine.md).
* 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**

| Field | Value |
| - | - |
| **Component Name** | A name for the set of objects, for example `Core Switch SNMP` |
| **Rules** | The rule that turns the SNMP values into GermainUX data. Keep the default, `snmp-default.drl`, to store numeric values in the **SNMP Value** KPI, or select your own [rule](https://docs.germainux.com/automation/rules.md). |

**3. Add the SNMP Objects**

Add one **SNMP Object** for each value to read.

| Field | Value |
| - | - |
| **Name** | A unique name for the value, for example `Uplink In Errors`. It identifies the value in the rule and in GermainUX. |
| **OID** | The object ID, for example `.1.3.6.1.2.1.2.2.1.14.49` |
| **Value Class Name** | `Integer` or `Long` for numbers, `String` for text. The default is `String`. The default rule stores only numeric values, so use `Integer` or `Long` for anything you want to chart or alert on. |

![SNMP Monitor Component wizard showing the Name, OID and Value Class Name fields of an SNMP Object](https://mintcdn.com/germain-ux/BTdAnP0ToWFYZWJt/images/main/snmp-monitoring/snmp-monitor-component-object-step.png?fit=max\&auto=format\&n=BTdAnP0ToWFYZWJt\&q=85\&s=a600284310f1c9dd9e871d1f535a59af)

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**

| Field | Value |
| - | - |
| **URI** | The device to poll. Select its URI, or create one with the device's host name or IP address, for example `192.0.2.10:161`. The port defaults to `161`. |
| **Monitored Software** | The application the device data belongs to, for example `Network` |
| **SNMP Version** | `v1` or `v2c`, as enabled on the device. The default is `v2c`. |
| **Credentials** | The credentials whose password is the device's read community. Leave it empty to use `public`. |

![SNMP Monitor Deployment wizard showing the URI and Monitored Software fields](https://mintcdn.com/germain-ux/BTdAnP0ToWFYZWJt/images/main/snmp-monitoring/snmp-monitor-deployment-target-step.png?fit=max\&auto=format\&n=BTdAnP0ToWFYZWJt\&q=85\&s=e9c78baa8d7bb72ff153faee0983a5a1)

Target Step of the SNMP Monitor Deployment Wizard - GermainUX

**6. Select the component and schedule**

| Field | Value |
| - | - |
| **Component** | The SNMP Monitor component you created |
| **Monitor Name** | A name for this device's monitor, for example `core-sw-01 SNMP` |
| **Monitoring Node** | The Monitoring Node and Engine that polls the device |
| **Schedule on which to run this component** | How often to poll. The default `0 0 * * * *` polls at the top of every hour. |

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:

```bash theme={null}
snmpget -v2c -c COMMUNITY DEVICE_IP .1.3.6.1.2.1.1.3.0
```

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

> [accordion] No values appear after the scheduled poll
>
> 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.

> [accordion] One SNMP Object never reports a value
>
> 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.

> [accordion] A text value doesn't appear
>
> 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`.

> [accordion] Counters only ever grow
>
> 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](https://docs.germainux.com/management/compliance-privacy-and-security/data-privacy.md).

## Related Documentation

> [card] [Network Observability](https://docs.germainux.com/integrations/network-monitoring.md)
>
> Connectivity, latency and interfaces

> [card] [Rules](https://docs.germainux.com/automation/rules.md)
>
> Analyze data as it arrives

> [card] [Automation](https://docs.germainux.com/automation.md)
>
> 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.

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/support.md)
>
> 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.

> [card] 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.