Skip to main content


Splunk Lantern

SNMP data


The simple network management protocol (SNMP) is one of the oldest, most flexible, and most broadly adopted IP protocols used for managing or monitoring networking devices, servers, and virtual appliances. This includes network devices such as routers and switches, as well as non-networking equipment such as server hardware or disk arrays. SNMP supports two different methods of obtaining data.

  • SNMP Traps are essentially alerts, set to send an alert on a state change, critical threshold, hardware failure and more. Traps are initiated by the SNMP device, and the trap is sent to an SNMP collector.
  • SNMP Polling is an interactive query/response approach. Unlike traps, polling is initiated by the SNMP collector in the form of a request for certain—or all—SNMP data available on the SNMP device.

Although many now provide vendor-specific APIs for remote management and data collection, SNMP is still valuable in troubleshooting due to its ubiquity (nearly every device supports it) and inherently centralized design (a single instance of SNMP management software can collect data from every device on an internal network, even across route domains). 

SNMP data can provide current information about performance, configuration, and current state. This could include current speed of all of the ports on a switch, the number of bytes sent (per port or in aggregate) through a router, the CPU temperature of a server, and any other information made available by the vendor per the SNMP MIBs for that device. 

SNMP Polling helps a security analyst to see the data transmission rates for a network-connected device that is suspected of malicious activity. The data can also help identify abnormal amounts of traffic to a certain site or domain, an abnormal amount of specific SNMP traps from a certain host, and an abnormal number of unique SNMP traps from hosts compared to normal profiles. In the Common Information Model, SNMP data is typically mapped to the Alerts data model

Before looking at documentation for specific data sources, review the Splunk Docs information on general data ingestion: