Fylamynt Product Docs
  • Welcome to Fylamynt
  • Getting started
    • Onboarding Checklist
    • 1. Setting up your first Cloud Service target account
    • 2. Getting to know workflows
    • 3. Creating your first workflow using AWS Cloud Services
    • 4. Setting up your first Integration
    • 5. Setting up your first resource
    • 6. Creating your first Incident Response workflow
    • 7. Incident Management - Automatic workflow execution
    • 8. Quickstart - Fylamynt sample workflows
  • Integrations
    • Amazon EventBridge
    • Ansible
    • AWS
    • AWS Health
    • Container
    • Datadog
    • Elasticsearch
    • Generic Webhook
    • GitHub
    • Google Kubernetes Engine (GKE)
    • Humio
    • Instana
    • Jenkins
    • Jira
    • New Relic
    • Opsgenie
    • PagerDuty
    • Pulumi
    • Prometheus
    • ServiceNow
    • Slack
    • Splunk
    • Splunk On-Call (VictorOps)
    • Spot by Netapp
    • Squadcast
    • Sumo Logic
    • Teleport
    • Terraform Cloud
    • Terraform CLI
    • Twilio
    • Zoom
  • AWS Services
    • EC2
    • Service Health
  • RESOURCES
    • API Keys
    • CloudFormation Templates
    • CloudWatch Targets
    • EKS Permissions
    • S3 Buckets
    • SSH Targets
  • FEATURED WORKFLOWS
    • Stop or Terminate underutilized AWS resources
    • Rightsizing EC2 instances
    • Incident Response Automation
    • Application Performance Monitoring
  • Announcement
    • What's new?
  • Support
    • Contact Fylamynt
Powered by GitBook
On this page
  • Create an Incident Type:
  • Incident Type Assignment:
  • New Relic notification Channel:
  • Automatically execute the workflow:

Was this helpful?

  1. Getting started

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.

Previous6. Creating your first Incident Response workflowNext8. Quickstart - Fylamynt sample workflows

Last updated 3 years ago

Was this helpful?

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:

  1. Fylamynt -> Settings -> Incident Types

  2. Select New Type

  3. Enter the Name of the Incident type

  4. Provide a description

  5. Select the name of the example workflow created

  6. Click Next

  7. Leave the default AlertBody Runtime Parameter

  8. Click Create Incident Type

Incident Type Assignment:

  1. Fylamynt -> Settings -> Integration -> New Relic -> Incident Type assignments

    • Select whichever integration you need to configure.

  2. 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.

New Relic notification Channel:

Step to create a New Notification channel:

  1. Select Webhook as the channel type

  2. Enter a channel name

  3. Add custom headers

    1. Enter name “x-api-key”

  4. Click Create Channel

  5. Add the channel to the Policy

Automatically execute the workflow:

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.

After completing the previous configuration steps of your 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 Base URL is available from the page on the Fylamynt console

The value is available from the page on the Fylamynt, by firstly selecting a Webhook API Key Name

To trigger the workflow you need to create some artificial load on the host. This can be achieved with a tool like by executing the following command: “stress-ng --vm 2 --vm-bytes 1G --timeout 240s”

first Incident Response workflow
New Relic integration
New Relic integration
stress-ng