Incident Management is the business layer on top of workflow executions and is used to automatically execute the workflow that is associated with a task type assignment.
Incident management contains 3 core pieces which include Incident Types, Incident Type assignment, and the Incident itself.
To automatically execute the example workflow with a New Relic trigger, the task type and assignment need to be configured. The configuration is similar for all other Fylamynt integrations.
Here are the steps:
Create an Incident Type:
Fylamynt -> Settings -> Incident Types
Select New Type
Enter the Name of the Incident type
Provide a description
Select the name of the example workflow created
Leave the default AlertBody Runtime Parameter
Click Create Incident Type
Incident Type Assignment:
Fylamynt -> Settings -> Integration -> New Relic -> Incident Type assignments
Select whichever integration you need to configure.
Click New Assignment
For New Relic, select the Policy from the drop-down
The required fields will be different depending on the integration.
Select the Corresponding Incident type created in the previous step
Click Add Assignment
The New Relic Policy name and the associated Incident type are now visible under Incident Type Assignments. Multiple Incident type assignments can be created to associate specific integration incidents/alerts to incident types.
New Relic notification Channel:
After completing the previous configuration steps of your first Incident Response workflow for the New Relic Integration, you need to create a webhook notification channel on the New Relic policy selected from the Policy Type assignment. This process will be different depending on the integration and New Relic is provided as an example.
The value is available from the New Relic integration page on the Fylamynt, by firstly selecting a Webhook API Key Name
Click Create Channel
Add the channel to the Policy
Automatically execute the workflow:
To trigger the workflow you need to create some artificial load on the host. This can be achieved with a tool like stress-ng by executing the following command: “stress-ng --vm 2 --vm-bytes 1G --timeout 240s”
On the New Relic Policy, wait for a memory alert to trigger on the New Relic
In Fylamynt a new Incident is created, where you can monitor the execution of each step.