I’m currently testing checkmk raw edition for our monitoring setup. I want to set it up so that when alerts are triggered, it automatically creates tickets in JIRA. I’ve been searching around but can’t find clear documentation on how to configure this integration properly.
Has anyone successfully connected checkmk RAW with JIRA for automatic ticket creation? I would really appreciate any step-by-step guides, configuration examples, or documentation links that could help me get this working.
Actually ran into this last month too. ended up using curl commands in a bash script instead of python - seemed simpler for our setup. the trick is getting the json payload formatted correctly for jira’s api. check your checkmk notification macros first tho, they contain all the alert data you need to pass thru.
I struggled with this same integration about six months ago. The main challenge with checkmk RAW is that it lacks the built-in notification plugins that come with the enterprise edition. What worked for me was creating a custom notification script using Python that calls JIRA’s REST API. You need to place the script in the local/share/check_mk/notifications/ directory and configure it through the notification rules in WATO. The script should handle the checkmk notification variables and map them to appropriate JIRA fields like summary, description, and priority. Make sure your JIRA instance has API access enabled and create a dedicated service account with proper permissions. The authentication can be tricky depending on your JIRA setup - we used basic auth with an API token. Testing the script manually first before integrating it with checkmk saved me considerable debugging time.
You might also want to consider using a webhook approach if you’re comfortable with setting up an intermediate service. I implemented this by configuring checkmk to send HTTP notifications to a small Flask application that I deployed on our internal server. This middleware handles the translation between checkmk’s notification format and JIRA’s API requirements. The advantage of this method is that you can easily modify the ticket creation logic without touching checkmk’s configuration directly, and it’s easier to troubleshoot when things go wrong. The Flask app logs all requests so you can see exactly what data checkmk is sending and debug any field mapping issues. I found this approach more maintainable than embedding all the JIRA logic directly in checkmk’s notification scripts, especially when we needed to customize ticket fields based on different alert types or severity levels.