Public docs

Creating incidents

Once the connection is established, you will have access to a REST endpoint to create/edit incidents. When creating incidents, 2 parameters are mandatory: event identifier and rule. Rules are required to identify the cause of the event. You can read more about rules here. 

Logs

To view information about events and changes inside Alert Catcher plugin there is a separate page with action log. This page displays data about connections, actions, rules and changes in connection settings. To view all connections, go to the section Connections - View logs.

You can also see the connection logs from the connection page:

Rules

An Alert Catcher rule is condition where alert was sent, for example, "High memory utilization", "Update failed", etc. In different systems, a rule means different entities (for example, in Zabbix, these are triggers). The analogue of a rule in Jira is its components. You can also assign a person responsible for a certain rule as well as for components. Components are bound to the project, and rules are bound to the connection.

Сonnection

For identification of demands from third party systems in Alert Catcher, there is created the additional entity - connection. In essence, the connection is the name of the system from which you will receive notifications. When you create a connection, a REST-resource is created as well, so that you can use to create/change incidents in Jira.

Actions

In Alert Catcher, actions are needed to manage the creation of problems based on incidents coming from third party systems.

When acritical time or number of incidents is reached, another issue (in Alert Catcher such tasks are called problems) will be created that is associated with existing incidents.

Privacy Policy

This privacy policy is for website https://alertcatcher.com and served by Softlist llc and governs the privacy of its users who choose to use it.

The policy sets out the different areas where user privacy is concerned and outlines the obligations & requirements of the users, the website and website owners. Furthermore the way this website processes, stores and protects user data and information will also be detailed within this policy.

Connection types

To work with connections from third-party systems in Alert Catcher version 2.0 has the ability to specify the target system from which alerts are received. The functionality to work with these new features can be found in the Connection type section.

To connect a third-party system, enter the address, credentials, and type of system you want to synchronize with in the Connection type section.

• Zabbix

  OVERVIEW

  In this section, you will learn how to set up Zabbix and Jira integration using Alert Catcher for incident handling.

  Communication between Zabbix and Jira is carried out using an http-request, on the basis of which Alert Catcher forms an Issue in Jira; to set up a connection between Alert Catcher and Zabbix, follow the link.

Workflow extentions

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.

Processing incidents

When creating an incident through Alert Catcher, you can manage the creation of problems, as well as use post-functions to manage incidents. When an incident is created, it is automatically added to the Rule scope - this means that it can be processed by the rule to which it is linked.

But if you create an incident manually and want it to be added to the Rule scope, you need to:

Custom fields

Two fields - [Alert Catcher] Connection and [Alert Catcher] Alert ID - are automatically added to the Alert Catcher after installation.  The Connection field is used to display information about the connection and the rule. The Alert ID field shows the incident identifier from a third-party system.
These fields are not required to be added to the view/edit/create issue screen, but they can be useful for generating reports or adding issue manually to rule scope.