Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading AMQP Messaging Modular Input
SHA256 checksum (amqp-messaging-modular-input_10.tgz) 10fd4653a767f729a02570eee5d8ea693db145e9352e668694d9128f4a870df4 SHA256 checksum (amqp-messaging-modular-input_09.tgz) 2514a347611feae8332191503482f886aeed5561013ec276eb84429c93e7dc6d SHA256 checksum (amqp-messaging-modular-input_08.tgz) 079a0f0ef5c306507522964b5f34f6e2a45d16bb30a9e9e491fb911f8ec53703 SHA256 checksum (amqp-messaging-modular-input_07.tgz) f2ecf7a39e003f0fc3320d87dc2033990760957373a8ce2d666d807712fed5a1 SHA256 checksum (amqp-messaging-modular-input_06.tgz) 2ad9f252262dc11fb0fe160a4647174be445069d932a2d43710a99c0cc344194 SHA256 checksum (amqp-messaging-modular-input_05.tgz) 923680026ad01828f1b59ce53df859170868b4885d392e90f2d465c8824cdf12
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

AMQP Messaging Modular Input

This is a Splunk Modular Input Add-On for indexing messages from an AMQP Broker.It utilizes the RabbitMQ Java client library , but can be used against any AMQP v0-9-1, 0-9 and 0-8 compliant broker.

Splunk AMQP Messaging Modular Input v1.0


This is a Splunk Modular Input Add-On for indexing messages from an AMQP Broker.It utilizes the RabbitMQ Java client library(v3.3.3) , but can be used against any AMQP v0-9-1, 0-9 and 0-8 compliant broker. Testing was performed against RabbitMQ Server v3.3.3

What is AMQP ?

From Wikipedia :

Examples of AMQP Brokers

  • RabbitMQ
  • Apache ActiveMQ
  • Apache Qpid
  • SwiftMQ
  • Apache Apollo
  • Windows Azure Service Bus


  • Splunk 5.0+
  • Java Runtime 1.7+
  • Supported on Windows, Linux, MacOS, Solaris, FreeBSD, HP-UX, AIX


  • Optionally set your JAVA_HOME environment variable to the root directory of your JRE installation.If you don't set this , the input will look for a default installed java executable on the path.
  • Untar the release to your $SPLUNK_HOME/etc/apps directory
  • Restart Splunk


As this is a Modular Input , you can then configure your AMQP inputs via Manager->Data Inputs->AMQP. The field entry should be straightforward and intuitive for anyone with basic experience with AMQP.


Any log entries/errors will get written to $SPLUNK_HOME/var/log/splunk/splunkd.log

JVM Heap Size

The default heap maximum is 64MB.
If you require a larger heap, then you can alter this in $SPLUNK_HOME/etc/apps/amqp_ta/bin/ on line 95

JVM System Properties

You can declare custom JVM System Properties when setting up new input stanzas.
Note : these JVM System Properties will apply to the entire JVM context and all stanzas you have setup

Customized Message Handling

The way in which the Modular Input processes the received AMQP messages is enitrely pluggable with custom implementations should you wish.

To do this you code an implementation of the com.splunk.modinput.amqp.AbstractMessageHandler class and jar it up.

Ensure that the necessary jars are in the $SPLUNK_HOME/etc/apps/amqp_ta/bin/lib directory.

If you don't need a custom handler then the default handler com.splunk.modinput.amqp.DefaultMessageHandler will be used.

This handler simply trys to convert the received byte array into a textual string for indexing in Splunk.

Code examples are on GitHub :


  • JAVA_HOME environment variable is set or "java" is on the PATH for the user's environment you are running Splunk as
  • You are using Splunk 5+
  • You are using a 1.7+ Java Runtime
  • You are running on a supported operating system
  • Look for any errors in $SPLUNK_HOME/var/log/splunk/splunkd.log
  • Run this command as the same user that you are running Splunk as and observe console output : "$SPLUNK_HOME/bin/splunk cmd python ../etc/apps/amqp_ta/bin/ --scheme"


This project was initiated by Damien Dallimore ,

Release Notes

Version 1.0
Nov. 24, 2015

Minor HEC data handling tweaks

Version 0.9
Sept. 28, 2015

Adjusted pre fetch logic

Version 0.8
Sept. 22, 2015

Added support to optional output to Splunk via a HEC (HTTP Event Collector) endpoint

Version 0.7
Feb. 11, 2015

Enabled TLS1.2 support by default.
Made the core Modular Input Framework compatible with latest Splunk Java SDK
Please use a Java Runtime version 7+
If you need to use SSLv3 , you can turn this on in bin/

Version 0.6
Aug. 20, 2014

Added configurable basic qos parameter

Version 0.5
June 25, 2014

Initial release


Subscribe Share

Splunk Certification Program

Splunk's App Certification program uses a specific set of criteria to evaluate the level of quality, usability and security your app offers to its users. In addition, we evaluate the documentation and support you offer to your app's users.

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 50GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
© 2005-2018 Splunk Inc. All rights reserved.
Splunk®, Splunk>®, Listen to Your Data®, The Engine for Machine Data®, Hunk®, Splunk Cloud™, Splunk Light™, SPL™ and Splunk MINT™ are trademarks and registered trademarks of Splunk Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.