Boundary and Splunk

“The ability to have data from Boundary’s APM service correlated with machine data directly in Splunk not only allows operations staff to proactively identify and resolve problems across physical, virtual and cloud environments, but also provides greater context to key performance indicators and ultimately a better experience for end users”

- Bill Gaylord, Senior Vice President, Business Development at Splunk

Using Boundary with Splunk

Boundary enables customers to monitor and improve application performance. If you have business-critical services deployed in cloud or hybrid IT infrastructures, Boundary can help you ensure these services deliver optimal performance and uptime. The Boundary adaptor for Splunk feeds information about application topology, network latency, and app-to-app conversation information into your Splunk environment. It also allows Boundary to consolidate all your Splunk alerts as annotations and see them alongside the other tools you have connected to Boundary.

Getting Started

First, download and install the Boundary Splunk adaptor by extracting it to a folder called boundary in $SPLUNK_HOME/etc/apps. Once you’ve unpacked it, configuring the Boundary Splunk application takes just a second. You can download the integration off GitHub from the link to your right.

Adding Your Credentials

First, we’ll need to grab your Boundary “Organization ID” and API key. You can find your organization ID and API key by logging in at and clicking “Organization » Org Settings” at the top right.Once you’ve got it, head to Splunk’s App Manager UI and choose the “Set Up” action for the Boundary adaptor. Then, drop the API Key and Organizaton ID into the form and click Save. With your configuration set and Splunk restarted, you’re good to go!



Case Studies

Get the Plugin

More Information