BMC TrueSight Pulse (formerly Boundary)


This article provides installation, configuration, and implementation details for the xMatters integration with TrueSight Pulse.

The integration to TrueSight Pulse:

  • Leverages built in Actions
  • Can be associated with any trigger
  • Relevant details about the alarm are sent to xMatters for easy display in notifications

Configure xMatters

Before configuring anything in TrueSight Pulse, you need to configure xMatters first.

Create an integration user

The first step in configuring xMatters is to create a user to authenticate REST web service calls when injecting signals.

This user needs to be able to work with alerts, but not update administrative settings. The best way to create a user for this integration is to have a dedicated "REST Web Service User" role that includes the permissions and capabilities. If this role does not exist in your deployment, you will need to create it, or ask xMatters Customer Support to create it for you.

In the following example, this role is named "REST Web Service User".

Create users and groups that will receive notifications

Recipients to the TrueSight Pulse alarms are set in the action when it is created in TrueSight Pulse. See below for details.

You can create multiple groups and users at once using the EPIC feature.

Import the workflow

The next step is to import the TrueSight Pulse workflow.

Install and configure the integration

Now that you've configured xMatters, it's time to configure TrueSight Pulse.

Configure TrueSight Pulse

The xMatters action has already been enabled in TrueSight Pulse.

Test the integration

You can test the integration by sending a notification email from within TrueSight Pulse.


First, add an email Action to the alarm. Was the email received? If so, check xMatters to see if the alert was created there. If not, verify the conditions of the Alarm to make sure it is actually being triggered.

Download resources