unSkript Documentation
Free SandboxBlogGitHubSlack Community
  • What is unSkript?
  • Guides
    • Contribute to Open Source
    • Getting started
      • Sign Up/Install
      • Authentication
        • Okta configuration
          • Okta Groups Sync
      • Create a Proxy
      • Add Credentials to Connect your Resources
      • Key Terms
  • RunBooks
    • Prebuilt xRunBooks
      • xRunBooks for CloudOps
      • xRunBooks for Cost Optimization
      • xRunBooks for DevOps
      • xRunBooks for IAM
      • xRunBooks for SecOps
      • xRunBooks for SRE
      • xRunBooks for Troubleshooting
    • Creating RunBooks
      • Importing unSkript xRunBooks
      • Create a xRunBook
      • Add an Action
      • Connecting Actions
      • Create a RunBook Input Parameter
      • Create a Credential
      • Writing Notes
      • Running XRunBooks
        • Running RunBooks with Approvals
      • Schedules
      • xRunBook Executions
      • Alarms
        • Create an Alarm Webhook
          • Webhooks for onprem installations
        • Create a Grafana Alert
        • Attaching runbooks to alarms
      • Folders
      • RunBook Outputs
  • Actions
    • What is an Action?
    • Create Custom Actions
    • Create Actions with AI
    • Actions
      • Action Configuration
        • Configure Action Inputs
        • Add Action Inputs
        • Action Output
        • Action Iterator
          • Using Iterators
        • Action Poll
        • Action Start Condition
      • Anatomy of an Action
    • Prebuilt Actions
  • Healthchecks
    • What is a HealthCheck?
    • Create a HealthCheck
      • Create a HealthCheck Folder
      • Adding Checks
    • HealthCheck Parameters
    • Running HealthChecks
    • HealthCheck Remediation
  • Workflows
    • What is a Workflow?
  • Connnecting
    • Connectors
      • Airflow
        • Airflow Actions
      • AWS
        • AWS Actions
          • AWS Cloudwatch Actions
          • AWS EC2 Actions
          • AWS ECS Actions
          • AWS EKS Actions
          • AWS ELB Actions
          • AWS IAM Actions
          • AWS Postgres Actions
          • AWS RDS Actions
          • AWS RedShift Actions
          • AWS S3 Actions
          • AWS VPC Actions
      • Azure
        • Azure Actions
      • ChatGPT
        • ChatGPT Actions
      • Datadog
        • Configuring webhook in Datadog
        • Datadog Actions
          • Datadog Alert Actions
          • Datadog Metrics Actions
          • Datadog Monitor Actions
      • Elasticsearch
        • Elasticsearch Actions
      • GCP
        • GCP Actions
          • GCP Bucket Actions
          • GCP GKE Actions
          • GCP IAM Actions
          • GCP VM Actions
      • Github
        • Github Actions
      • Grafana
        • Grafana Actions
      • Hadoop
        • Hadoop Actions
      • Jenkins
        • Jenkins Actions
      • Jira
        • Jira Actions
      • Kafka
        • Kafka Actions
      • Kubernetes
        • K8s Actions
      • MongoDB
        • MongoDB Actions
      • MS SQL
        • MSSQL Actions
      • MySQL
        • MySQL Actions
      • Netbox
        • Netbox Actions
      • Nomad
        • Nomad Actions
      • OpenSearch
        • opensearch Actions
      • Pingdom
        • Pingdom Actions
      • Postgres
        • Postgres Actions
      • Prometheus
        • Prometheus Actions
      • Redis
        • Redis Actions
      • REST
        • REST Actions
      • SalesForce
        • SalesForce Actions
      • Slack
        • Slack Actions
      • Snowflake
        • Snowflake Actions
      • Splunk
        • Splunk Actions
      • SSH
        • SSH Actions
      • Stripe
        • Stripe Actions
      • Terraform
        • Terraform Actions
      • Zabbix
    • Proxies
      • Environment
        • RunBooks Across Environments: ServiceIDs
      • unSkript Proxy
      • AWS Proxy
      • GCP Proxy
    • Secret store
      • Vault
  • Tooling
    • Role Based Access Control
      • RBAC Roles
    • API reference
      • Authentication
      • Endpoints
        • Executions
        • RunBooks
        • Schedules
    • Command Line Tool
    • Notifications
  • Fundamentals
    • Jupyter Notebook 101
  • Use Cases
    • DevOps
    • SRE
  • Open source
    • Runbooks.sh
    • Contribute to Open Source
  • Lists
    • AWS Service Quota list
Powered by GitBook
On this page

Was this helpful?

  1. RunBooks
  2. Creating RunBooks
  3. Alarms

Attaching runbooks to alarms

You've created an alert, and connected to an unSkript Webhook. Let's connect it to a RunBook!

PreviousCreate a Grafana AlertNextFolders

Last updated 1 year ago

Was this helpful?

In order to connect an alarm to a RunBook you must have first completed the following steps:

  1. Create an alert

    1. Create a Cloudwatch Alert

  2. into unSkript

    1. In your Proxies tab, find the connection with your webhook, and click the "Pull Alarms" options from the 3 dot menu:

  3. The Alarm must have fired at least once. You can test the alert from or Cloudwatch as a proxy.

  4. Have a RunBook in mind to connect to the alert.

With these steps completed, we are ready to connect the Alert to the RunBook.

Attaching your Alarm to a RunBook

  1. Find your Alarms: Click the Events button in the top navigation of unSkript. You'll land on the listing of alarms that are already attached to RunBooks (if this is the first alarm, the table will be empty).

  2. Alarms not attached to RunBooks: Since your alarms are not yet attached to a RunBook, click "unattached" on the top right of the table. This will give you a list of all alarms that have been synced into unSkript, but do not yet have a RunBook connected. You can use the search box to filter the results. The the screenshot below, we have filtered on the term "docs."

  3. Attach your alarm: Click the checkbox to select the alarms you'd like to connect to a RunBook, and then click the "attach RunBook" button that is above the table.

  4. Select your RunBook: Select the RunBook you'd like to connect to the alarm

  5. If your alarm has fired, you will be prompted to connect the output of the alarm to the input parameters of your RunBook.

If your alarm has not fired, you can TEST your alarm.

  • Send a Cloudwatch test

  1. To connect alarm parameters to RunBook input parameters, we will use JQ commands:

  2. In the screenshot above, the left side shows the input parameters for the RunBook (in this case "alarm_name" and "alarm_value." The right side shows the 5 most recent alerts from the alarm.

    1. Use JQ commands to select the items from the JSON to populate the RunBook inputs.

    2. if you have never used jq, there is an autofill feature. Type a period into the box, and a set of options will appear.

    3. Once you have chosen the desired path, click return, and the value will appear below the field.

  3. Click attach RunBook to connect the alert to the RunBook.

Create an Alarm Webhook
Create a Grafana Alert
Sync the alerts
Send a Grafana test
Grafana