SNMP Data Collection
Last updated on 02 July, 2025Simple Network Management Protocol (SNMP) is a widely used protocol for monitoring network devices. SNMP data collection enables the retrieval of performance and status data from networked devices such as routers, switches, servers, and more. To maximize compatibility with a broad range of modern and legacy devices, LogicMonitor uses the following fallback connection strategy for SNMP data collection:
- SNMP v3 (most secure)
- SNMP v2c
- SNMP v1
This approach ensures successful communication with devices regardless of their SNMP version support.
LogicMonitor uses two primary SNMP operations:
snmpget
—Retrieves individual metric values using a known Object Identifier (OID). This is the standard method for collecting specific metrics.snmpwalk
—Performs a sequential walk (with GETNEXT requests) through a subtree of the MIB hierarchy. It is used during Active Discovery to detect and list multiple instances of device components, such as interfaces or fans.
Note: Some legacy devices may support only one of these commands. For example, a device may support snmpget but not snmpwalk, which can affect multi-instance discovery.
SNMP uses Object Identifiers (OIDs), which are dot-separated numerical strings to reference specific metrics on a device. For example, 1.3.6.1.2.1.2.2.1.10
.
In multi-instance DataSources, LogicMonitor substitutes the instance index using the ##WILDVALUE##
token, enabling a single base OID to be reused across multiple discovered instances. See the following examples:
Base OID:
1.3.6.1.2.1.2.2.1.10
Discovered Instances:
1.3.6.1.2.1.2.2.1.10.1 (eth0)
1.3.6.1.2.1.2.2.1.10.2 (eth1)
With Wildvalue Token:
1.3.6.1.2.1.2.2.1.10.##WILDVALUE##
The SNMP data collection method automatically substitutes the correct index value (for example, 1
, 2
) for each discovered instance.
When configuring a multi-instance SNMP DataSource with Active Discovery, the discovery type determines how each discovered instance is named. For more information on discovery types, see the following table:
Discovery Type | Description |
wildcard | Uses the numerical index of each OID. For example, .1, .2. |
value | Uses the actual value returned from each OID. For example, an interface description like eth0 . |
lookup | Uses a separate lookup OID to convert the index into a meaningful name. |
Requirements for Configuring SNMP Data Collection
Before configuring SNMP data collection, ensure the following are met:
- SNMP credentials are properly configured on the target resource.
- A LogicMonitor Collector is installed and assigned to monitor the resource. For more information, see Adding a Collector.
- Administrator access to the LogicMonitor portal.
- Access to the device’s Management Information Base (MIB), which provides OIDs for supported metrics.
Configuring a Multi-Instance SNMP DataSource
- In LogicMonitor, navigate to Modules and either add a new DataSource or select the DataSource you want to configure SNMP data collection for.
For more information, see Custom Module Creation or Modules Management. - Configure or modify the module as needed, and select “SNMP” from the Collection Method dropdown menu.
- To enable active discovery, toggle the Enable Active Discovery switch.
You must enable the Multi-Instance switch before you can enable Active Discovery. - Select the Active Discovery tab and complete the Basic Information section. For more information, see Active Discovery.
- To configure SNMP data collection, set the following arguments in the Active Discovery tab:
- From the Discovery Method dropdown menu, ensure “SNMP” is selected.
- In the SNMP Discovery Type dropdown, select one of the following options for how you want to identify and filter instances:
- To use the returned valued from each walked OID, select Value.
- To use the index number from head OID as the instance name, select Wildcard.
- To use a secondary OID table to map each index to a friendly name, select Lookup.
- In the SNMP OID field, enter the base OID used to identify instances. If you are collecting metrics across multiple instances, include the
##WILDVALUE##
token to represent the dynamic index value. See the following example:The token is replaced at runtime with the discovered index for each instance (for example,1.3.6.1.2.1.2.2.1.10.##WILDVALUE##
1
,2
,3
). - (Optional) In the Description OID field, enter the OID that returns a human-readable label for each instance. This value is used as the display name (alias) in LogicMonitor. Like the SNMP OID, it should include the
##WILDVALUE##
token. See the following example:This retrieves the ifDescr (interface description) for each interface index (for example, eth0, eth1).1.3.6.1.2.1.2.2.1.2.##WILDVALUE##
Recommendation: Provide a description OID when using the Wildcard discovery type to make instance names more meaningful.