Alert Catcher expands the functionality to handle problems and incidents with post-functions. This page provides a list of post-functions, as well as options for using them.
For correct work of post-functions we recommend to change the order of their location and to put in the middle of the list of all post-functions transition.
This post-function should be set to a problem workflow.
When the problem goes to a specific status, a comment will be copied to all related incidents created through Alert Catcher or for which the Connection field is set.
This post-function should be set to a problem workflow.
When the problem goes to a specific status, the resolution will be copied to all related incidents created via Alert Catcher or for which the Connection field is set.
This post-function should be set to a problem workflow. This post-function allows you to transition incidents to a status, which is specified in the post-function.
This can be useful when you close a problem and want all related incidents to be closed.
This post-function is intended to activate changes in the Connection field. Using this post-function, you can add an incident to the rule queue for processing or change the rule/connection itself.
You can use this post-function for manual rule processing.
If you want to close an incident from a third-party system from a issue screen in Jira, you can add a post-function to move to a specific status.
If you have correctly configured the Connection type Zabbix, the event ID was transferred correctly, you can approve the event from Jira to Zabbix. After performing the post-function, the value of the Acknowledged field will change to Yes.
.png?version=1&modificationDate=1595578876124&cacheVersion=1&api=v2 "Alert Catcher > Workflow extentions > zabbix alert (1).png")