The open-source alert management and AIOps platform

Why Keep? · Getting started · Supported tools and integrations · Docs · Try it out · Website · Report Bug · Slack Community

How does it work?

1. Connect your tools: Connect everything from monitoring platforms to databases and ticketing systems.

Connect providers	Receive alerts

2. Set up Workflows: Initiate automated workflows in response to alerts or based on custom intervals.

Create and upload workflows

3. Operational efficiency: Automate your alert handling to focus your team's efforts on what really matters.

Why Keep?

1. Centralized dashboard: Manage all your alerts across different platforms in a single interface.
2. Noise reduction: Deduplicate and correlate alerts to reduce alert fatigue.
3. Automation: Trigger workflows for alert enrichment and response.
4. Developer-first: Keep is API-first and lets you manage your workflows as code.
5. Works with every tool: Plenty of supported providers and more to come.

Workflows

The easiest way of thinking about Workflow in Keep is GitHub Actions. At its core, a Workflow in Keep is a declarative YAML file, composed of triggers, steps, and actions and serves to manage, enrich, and automate responses to alerts:

workflow:
  id: most-basic-keep-workflow
  description: send a slack message when a cloudwatch alarm is triggered
  # workflow triggers - supports alerts, interval, and manual triggers
  triggers:
    - type: alert
      filters:
        - key: source
          value: cloudwatch
    - type: manual
  # list of steps that can add context to your alert
  steps:
    - name: enrich-alert-with-more-data-from-a-database
      provider:
        type: bigquery
        config: "{{ providers.bigquery-prod }}"
        with:
          query: "SELECT customer_id, customer_type as date FROM `customers_prod` LIMIT 1"
  # list of actions that can automate response and do things with your alert
  actions:
    - name: trigger-slack
      provider:
        type: slack
        config: " {{ providers.slack-prod }} "
        with:
          message: "Got alarm from aws cloudwatch! {{ alert.name }}"

Workflow triggers can either be executed manually when an alert is activated or run at predefined intervals. More examples can be found here.

Supported Providers

Missing any? Just submit a new provider issue and we will add it in the blink of an eye.

Observability tools

Databases and data warehouses

Communication platforms

Incident Management tools

Ticketing tools