SignalFx Steps

These steps allow you to communicate between xMatters and SignalFx. This uses the newer version of the payload and has been improved to use Flow Designer. The integration builder based integration can be found here.

---

---

Files

• SignalFx.zip - Workflow zip file with the steps and example flow
• signalfx.png - SignalFx logo

How it works

This flow can be triggered through either an xMatters integration in SignalFx. The flow will then get all similar xMatters alerts, and terminate them, then it will create a new xMatters alert. Responding to this alert will result in changes within SignalFx. Response options include: Acknowledge, which sends a delivery event to SignalFx; Mute, which mutes SignalFx; Unmute, which unmutes SignalFx; Resolve, which resolves the event in SignalFx.

Installation

xMatters Setup

1. Download the SignalFx.zip file onto your local computer
2. Navigate to the Developer tab of your xMatters instance
3. Click Import, and select the zip file you just downloaded
4. Update the Get Events step with the Status and Priority of the events you would like to look for.
5. Fill in the API Token for SignalFx in the Constants.
6. Fill in the recipients for the xMatters Alert in the xMatters Create Event step.
7. Update the SignalFx API and SignalFx Ingest Endpoints with the correct values. https://api.{REALM}.signalfx.com and https://ingest.{REALM}.signalfx.com respectively.

SignalFx Setup

1. Go to Integrations > xMatters. (It should be under the "Notification Services" section)

2. Create a new integration, filling in the name to identify the notification, and for the URL use the one given in the Inbound - SignalFx step in your xMatters Flow.

3. Add the xMatters integration to an alert as a recipient.

4. In SignalFx, go to your user profile and select Access Tokens from the tabs on the left. Create a new an Access Token from that menu.

5. Use this value to fill in the API Token Constant in xMatters.

Troubleshooting

If you are getting a 404 error in the activity log of any response to an xMatters event, make sure the realm is set in the API and Ingest endpoints. Also related to this issue is the API key. The API key is NOT the Generate User API Access Token found on the main page of your SignalFx profile. It is found by expanding the left side menu, and then selecting Access Tokens.

Double check that every instruction in the setup was followed, as any value not being set can cause the entire flow to not work as intended.

Example

This is an image of the example flow provided. On an alert from SignalFx, it will look for xMatters events matching the SignalFx incidentId. It will then create an xMatters alert. On a response to the alert, the response is relayed back to SignalFx.