Using Custom Alert actions to integrate with JIRA
At 5 minutes intervals, the CFEngine hub gathers information from all of its connected agents about the current state of the system, including the outcome of its runs.
In this tutorial we will show how to use a Custom action alert script to open a ticket, using JIRA an an example, when a CFEngine policy fails (is not kept).
How it works
We assume that there is already a CFEngine policy bundle in place called web_service that ensures an important service is working.
As we are already using the JIRA ticketing system to get notified about issues with the infrastructure, we want CFEngine to open a ticket if our web_service bundle fails (is not kept). This is done centrally on our hub, because it knows the outcome of the policy on all the nodes. We will only open a ticket once the alert changes state to triggered, not while it remains in triggered, to avoid an unnecessary amount of tickets being automatically created.
Note however that it is possible to expand on this by adjusting the Custom action script. For example, we could create reminder tickets, or even automatically close tickets when the alert clears.
1. Create a Custom action script that creates a new ticket
1. Log in to the command line of your CFEngine hub, and make sure you have python and the jira python package installed (normally by running “pip install jira”).
2. On your workstation, unpack cfengine_custom_action_jira.py to a working directory.
3. Inside the script, fill in MYJIRASERVER, MYUSERNAME and MYPASSWORD with your information.
4. Test the script by unpacking alert_parameters_test into the same directory and running
5. Check if the previous step created a ticket in JIRA. If not, recheck the information to typed in, connectivity and any output generated when running the script.
2. Upload the Custom action script to the Mission Portal
1. Log in to the Mission Portal of CFEngine, go to Settings (top right) followed by Custom notification scripts.
3. Click save to allow the script to be used when creating alerts.
3. Create a new alert and associate the Custom action script
1. Log into the Mission Portal of CFEngine, click the Dashboard tab.
2. Click on the existing Policy compliance widget, followed by Add alert.
3. Name the alert ‘Web service’ and set Severity-level at ‘high’.
4. Click create new condition and leave Name ‘Web service’.
5. Select Type to ‘Policy’.
6. Select Filter to ‘Bundle’, and type ‘web_service’.
7. Type Promise Status to ‘Not kept’.
8. Associate the Custom action script we uploaded with the alert.
In this tutorial, we have shown how easy it is to integrate with a ticketing system, with JIRA as an example, using CFEngine Custom actions scripts.
Using this Custom action, you can choose to open JIRA tickets when some or all of your alerts are triggered. But this is just the beginning; using Custom actions, you can integrate with virtually any external system for notifying about- or handling triggered alerts.
You can read more in the Custom action documentation.