BMC TrueSight Pulse provides easy to use alarms, which will be triggered when the monitored metric goes above (or below) the defined threshold. Each alarm can be connected to one or more Actions, so users can be notified when an alarm status changes. When the account is created, we pre-provision several simple alarms to get you started and connect them to the e-mail Action. Customers who use different collaboration tools can easily create more Actions and attach them to Alarms. This article describes how to integrate with popular VictorOps service.
First, you need to add the VictorOps Action to your BMC TrueSight Pulse/Boundary account. Click "Settings" on left toolbar to open the dialog and go to Actions tab. Click on the "Add Action" button and select "VictorOps" on the next screen and click "Add".
You will find yourself on the "VictorOps" configuration page. It has just four fields - Name, API Key, Severity and Routing Key, the last one is optional. Name can be any unique string for this Action. Then you can pick the Severity from dropdown box, it has three possible values - Critical, Warning and Info. Depending on it, it will be presented differently in VictorOps - using red for critical, yellow for warning and gray for info. Getting an API Key requires a bit more work.
To get it, you need to login into your VictorOps account, click on Settings >Alert Behavior , then choose "Integrations" to get to API Tokens section.
At this time, select "BMC TrueSight Pulse" from the list and click "Enable Integration".
VictorOps will produce an API Key for the integration.
Now, select and copy the API Key and switch back to BMC TrueSight Pulse/Boundary configuration window. There you will paste the API Key into the relevant text control. The last parameter, Routing Key, is optional and is used internally by VictorOps to provide additional functionality when routing the ticket - see VictorOps documentation for details.
Now you should have VictorOps action ready to be used. The last step would be attach it to new or existing Alarms. For my test, I attached it to the default CPU Utilization alarm and lowered the threshold, to make sure the alarm is triggered.
A bit later, I was able to see notifications in the Timeline view of my VictorOps account:
That's it! You can define more VictorOps actions with different severity or Routing Key or re-use the same VictorOps Action in multiple alarms.