Follow

Send notifications to Flowdock

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 the popular Flowdock service. 


First, you need to add the Flowdock Action to your BMC TrueSight Pulse account. Click "Settings" on left toolbar to open the dialog and go to Actions tab. Click on the "Add Action" button and select "Flowdock" on the next screen and click "Add".  

    

You will find yourself on the "Flowdock" configuration page. It has four fields - Name, API Token, Organization and Flow. Name can be any string, but getting other parameters requires more effort.

To get it, you need to login into your Flowdock account and get to API Tokens section. You can do that using this shortcut: https://www.flowdock.com/account/tokens (might require Flowdock login).

Then copy your personal 'API Token' into the first parameter in the Boundary configuration screen.

The next step is choosing the flow in the Flowdock app, where you want your notifications to appear and open its 'Flow Settings' window. Select the flow name at the left navigation bar, then click on the small 'Configure' icon and select "Flow Settings" menu item from the popup menu. 

At this window you need to locate and copy over two items: Flow and Configuration. 

Now you should have all the required parameters and your configuration window in BMC TrueSight Pulse should look like this:

 

Now the Flowdock action is 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 2%, to make sure the alarm is triggered. 

Just 15 seconds later, I was able to see notification in the Flowdock's "Test Channel" flow:

That's it! You can define more Flowdock actions for other Flowdock flows or re-use the same Action in multiple alarms. 

Have more questions? Submit a request