Send events to StackState from an external system

StackState Self-hosted v4.5.x

This page describes StackState v4.5.x. The StackState 4.5 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.5 version range to upgrade to a more recent release.

Go to the documentation for the latest StackState release.

This tutorial shows you how to send events from external systems to StackState.

StackState creates a real-time map over your IT landscape and tracks all changes that occur. These changes are visible as events in the Events Perspective.

This tutorial shows how you can submit external events to StackState.


This repository contains a sample project with a Puppet report processor ( that will process a report of a Puppet configuration run and send events to StackState.

In StackState, the events visible in the Events Perspective are related to elements (components or relations). In our example, the events sent to StackState by the report processor will be related to the host that Puppet runs on.

The sample project uses Vagrant ( to provision a virtual machine with Puppet and the sample report processor installed. If you don't have access to Vagrant, read how you can submit events directly.

Clone the repository to your laptop to get started.

Preparing StackState

Before you get started, StackState must be configured to handle the data that will be sent from the sample project. The project uses a StackState Agent installed on the virtual machine to send data in a format that is consumed by the StackState Agent v2 StackPack.

The sample project will handle installation of a StackState Agent on the virtual machine. You will need to install the Agent v2 StackPack in StackState to interpret the data it sends. If you're running the tutorial on an existing instance of StackState, we advise you to install a dedicated instance of the Agent v2 StackPack for the tutorial. This will allow you to easily clean up and remove all configuration and topology imported during the tutorial when you're finished.

Preparing the tutorial

First, boot the virtual machine using Vagrant:

vagrant up

Vagrant will download a virtual machine image and provision a virtual machine. When it is finished, you can log into the machine using the command:

vagrant ssh

The rest of this tutorial assumes you are running as the root user. Use the following command to change to root in your virtual machine:

sudo su -

Before running the example, you need to configure the sample project with your StackState instance URL and API key.

export STS_API_KEY=your-api-key
export STS_STS_URL=

That's it, you are now ready to run the example.

Running the example

The sample project is shipped with a single script that does the following:

  1. Check for the presence of the STS_STS_URL and STS_API_KEY environment variables.

  2. Place the environment variables in the correct configuration files.

  3. Install the StackState Agent if it isn't already installed.

  4. Starts the StackState Agent if it isn't already started.

  5. Invoke Puppet to make some configuration changes to the virtual machine.

Now, go ahead and trigger the script:


Once the Puppet run is finished, the report processor is invoked and formats a JSON message that it sends to StackState. You can see the report processor code on GitHub.

The event will be visible in the StackState Events Perspective:

Submitting external events directly

If you don't have access to Vagrant, you can also submit the JSON to StackState directly using the command below.

If you execute this command locally instead of on the virtual machine, make sure that you have the environment variables set properly.

TS=`date +%s`; cat event.json | \
    sed -e "s/##TIMESTAMP##/$TS/" | \
    curl -H "Content-Type: application/json" -X POST \
    -d @- ${STS_STS_URL}/intake/\?api_key\=${STS_API_KEY}

For these events to appear in StackState, the component representing the virtual machine must be present with the identifier urn:host:/localhost.localdomain. See how to manually add a component.

Terminating the virtual machine

When you are done running the example, exit the shell and use the following command to terminate the virtual machine:

vagrant destroy

Cleaning your StackState instance

When you are done with this tutorial, you can remove the configuration from your StackState instance as follows:

  • Uninstall the Agent v2 StackPack. This will remove the configuration and data received (topology) from StackState.

See also

Last updated