7. Incident Management - Automatic workflow execution
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:
- 1.Fylamynt -> Settings -> Incident Types
- 3.Select New Type
- 4.Enter the Name of the Incident type
- 5.Provide a description
- 6.Select the name of the example workflow created
- 8.Click Next
- 9.Leave the default AlertBody Runtime Parameter
- 10.Click Create Incident Type
- 1.Fylamynt -> Settings -> Integration -> New Relic -> Incident Type assignments
- Select whichever integration you need to configure.
- 3.Click New Assignment
- 1.For New Relic, select the Policy from the drop-down
- The required fields will be different depending on the integration.
- 2.Select the Corresponding Incident type created in the previous step
- 3.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.
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.
Step to create a New Notification channel:
- 1.Select Webhook as the channel type
- 2.Enter a channel name
- 4.Add custom headers
- 5.Click Create Channel
- 6.Add the channel to the Policy
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.