Splunk® Enterprise

Admin Manual

Download manual as PDF

Splunk version 4.x reached its End of Life on October 1, 2013. Please see the migration information.
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

Send SNMP traps to other systems

You can use Splunk as a monitoring tool to send SNMP alerts to other systems such as a Network Management System console.

Note: For information on how to index SNMP alerts on Splunk, read "Send SNMP events to Splunk" in the Getting Data In manual.

Create a script that sends the SNMP traps


Note these requirements:

  • Perl is required to run the script.
  • Net-SNMP package is required in order to use the /usr/bin/snmptrap command. If you have another way of sending an SNMP trap from a shell script, modify the script as needed.
  • Make sure there's admin access to the $SPLUNK_HOME/bin/scripts directory.
  • For security reasons, scripts must reside in the $SPLUNK_HOME/bin/scripts directory.

Create the script

Note the following:

  • Create the script in the $SPLUNK_HOME/bin/scripts directory. Create the directory if it doesn't already exist. Copy the code listed below into sendsnmptrap.pl.
  • Run chmod +x sendsnmptrap.pl to make the script executable.
  • In the scrpt, change the Host:Port of the SNMP trap handler, the paths to the external commands splunk and snmptrap, and the user/password if necessary.

Sample script code

# sendsnmptrap.pl: A script to enable using Splunk alerts to send an SNMP trap.
# Modify the following code as necessary for your local environment.
$hostPortSNMP = "qa-tm1:162"; # Host:Port of snmpd or other SNMP trap handler
$snmpTrapCmd = "/usr/bin/snmptrap"; # Path to snmptrap, from http://www.net-snmp.org
$TRAPOID = ""; # Object IDentifier for traps/notifications 
$OID = ""; # Object IDentifier for objects, Splunk Enterprise OID is 27389
# Parameters passed in from the alert.
# $1-$9 is the positional parameter list. $ARGV[0] starts at $1 in Perl.
$searchCount = $ARGV[0]; # $1 - Number of events returned
$searchTerms = $ARGV[1]; # $2 - Search terms
$searchQuery = $ARGV[2]; # $3 - Fully qualified query string
$searchName = $ARGV[3]; # $4 - Name of saved search
$searchReason = $ARGV[4]; # $5 - Reason saved search triggered
$searchURL = $ARGV[5]; # $6 - URL/Permalink of saved search
$searchTags = $ARGV[6]; # $7 - Always empty as of 4.1
$searchPath = $ARGV[7]; # $8 - Path to raw saved results in Splunk instance (advanced)

# Send trap, with the parameter list above mapping down into the OID.
$cmd = qq/$snmpTrapCmd -v 2c -c public $hostPortSNMP '' $TRAPOID 
$OID.1 i $searchCount $OID.2 s "$searchTerms" $OID.3 s "$searchQuery" $OID.4 s 
"$searchName" $OID.5 s "$searchReason" $OID.6 s "$searchURL" $OID.7 s 
"$searchTags" $OID.8 s "$searchPath"/;

For Windows

This Perl script will work on MS Windows systems with Perl. However, on some Windows systems, Perl may not be installed, or Perl scripts may not be configured to be directly executable via Splunk. In those cases, you might find it easier to use a Windows CMD script, as described in "Sending SNMP traps on Windows".

Provide an MIB file

You can provide a Splunk MIB file for the SNMP monitoring agent. See "Splunk Alert MIB" for details.

Configure your alert to call the script

Follow these steps:

1. Create an alert. Read "Save searches and share search results" and "Create an alert" in the User manual for more information.

2. Set up your alert so that it calls the script. To do so, specify the name of the script (which must reside in $SPLUNK_HOME/bin/scripts):


Example script run

Here is an example of the script running, including what it returns:

[root@qa-tm1 ~]# snmptrapd -f -Lo
2007-08-13 16:13:07 NET-SNMP version Started.
2007-08-13 16:14:03 qa-el4.splunk.com [] (via UDP: []:32883) TRAP, SNMP v1, community public
        SNMPv2-SMI::enterprises.27389.1 Warm Start Trap (0) Uptime: 96 days, 20:45:08.35
        SNMPv2-SMI::enterprises.27389.1.1 = INTEGER: 7 SNMPv2-
SMI::enterprises.27389.1.2 = STRING: "sourcetype::syslog" SNMPv2-
SMI::enterprises.27389.1.3 = STRING: "search sourcetype::syslog starttime:12/31
/1969:16:00:00 endtime::08/13/2007:16:14:01" SNMPv2-SMI::enterprises.27389.1.4 
= STRING: "SyslogEventsLast24" SNMPv2-SMI::enterprises.27389.1.5 = STRING: 
"Saved Search [SyslogEventsLast24]: The number of hosts(7) was greater than 1" 
SNMPv2-SMI::enterprises.27389.1.6 = STRING: "http://qa-el4:18000/?q=sourcetype
%3a%3asyslog%20starttimeu%3a%3a0%20endtimeu%3a%3a1187046841" SNMPv2-
SMI::enterprises.27389.1.7 = STRING: "/home/tet/inst/splunk/var/run/splunk
2007-08-13 16:14:15 NET-SNMP version Stopped.
Configure scripted alerts
What you can back up

This documentation applies to the following versions of Splunk® Enterprise: 4.3, 4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7


Running this produces the following results:<br /><br />root@splunk(Linux) $ snmptrapd -f -Lo<br />Warning: no access control information configured.<br />This receiver will *NOT* accept any incoming notifications.<br />couldn't open udp:162 -- errno 98 ("Address already in use")

December 10, 2014

Thanks for the script. Was very useful and I was able to get this going.<br />May I humbly suggest changing the last two lines to be:<br /><br />@args = ("-v", "2c", "-c", "public", $hostPortSNMP, '', $TRAPOID,<br /> "$OID.1", "i", $searchCount, "$OID.2", "s", $searchTerms, "$OID.3", "s", $searchQuery,<br /> "$OID.4", "s", $searchName, "$OID.5", "s", $searchReason, "$OID.6", "s", $searchURL,<br /> "$OID.7", "s", $searchTags, "$OID.8", "s", $searchPath);<br />exec($snmpTrapCmd, @args);<br /><br />The reasoning being that - if you are going to make the `system` call be the last thing in the script, you might as well use `exec` to avoid the unnecessary extra fork() that system will do. Furthermore, passing exec (or system) a command and an array of args is safer and more efficient than simply passing a single string.

March 23, 2012

Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters