icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

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 Azure EventHub TA for Splunk Connector
SHA256 checksum (azure-eventhub-ta-for-splunk-connector_111.tgz) 304526be3ae00422d3903efbe19918b250e50bafe406e1c408f350b6bc91e473
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

Azure EventHub TA for Splunk Connector

Splunk AppInspect Passed
Admins: Please read about Splunk Enterprise 8.0 and the Python 2.7 end-of-life changes and impact on apps and upgradeshere.
The Azure Event Hub Connector TA provides:
- Pre-defined Sourcetypes (for json or syslog type events)
- Sample inputs to invoke wrapper script
- Sample inputs for monitoring inputs on disk

This TA is designed to work with the Solsys Event Hub Connector, created in-house. For details regarding the Solsys Event Hub Connector please contact developer@solsys.ca or sales@solsys.ca.


  • Install Solsys Azure Event Hub Connector and start collecting logs
  • Install "REST storage/passwords Manager for Splunk" from Splunkbase
    Installation Instructions:
  • Browse Apps Search for "Azure EventHub TA for Splunk Connector"
  • Restart Splunk


  • Once the Solsys Connector is setup, go to $APP/default/, copy the inputs.conf and place it in $APP/local.
  • Edit inputs.conf in the local drive by removing comments for the scripted inputs. The wrappey.py should be copied over from the connector and places in a bin directory for Splunk to access
  • Once the scripted input for the wrapper is commented and adjusted, restart Splunk to start onboarding data from the eventhub
  • Use the monitoring stanzas provided in the TA to start onboarding logs to your Splunk environment

Onboarding Data:

  • Onboard data from operational-insights-logs eventhub as eventhub:operational:json sourcetype to take advantage of the operational insights dashboards in the Azure Eventhub Insights Application
  • Use the sourcetype eventhub:json for all other generic eventhub json data

Details on Solsys Event Hub Connector

To download the User Guide for the Solsys Event Hub Connector click here. The User guide covers implemention of the Connector as well as installation location/steps.

For more information about Solsys and our Splunk EventHub Application check out our technical blog on our website here.

Release Notes

Version 1.1.1
June 20, 2019


Subscribe Share

AppInspect Tooling

Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB 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-2020 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.