tl;dr Enrich your Slack alerts with contextual observability data, helping on-call engineer investigate faster.
PlayBooks are executable notebooks designed to Automate Preliminary Investigations in Production for engineers. Watch demo video.
- Define a playbook with your enrichment logic
- Configure the playbook to auto-trigger basis a Slack alert received in a channel
- Receive automated investigation summary in the Slack thread for the same alert
- Explore the sandbox to get a sense of how the playbooks work.
- You can also check out the #demo-alerts channel in community Slack workspace to see how automated replies are received for alerts.
-
Enrichment library: The tool currently supports fetching 50+ types of enrichment data from metric sources (Datadog, New Relic, Grafana+Prometheus, Cloudwatch Metrics), Logs & Events (Cloudwatch Logs, EKS) and Databases (PostgreSQL DB, Clickhouse DB)
-
Past Executions: See the historical runs of a playbook and go back to an investigation from a specific point in time.
-
Continuous monitoring: Setup continuous monitoring cron for specific use-cases (e.g. post deployment, peak hours, post bug-fix). Read docs for list of allowed configurations.
- Interpretation Layer: Configure ML modules which can analyse & interpret data from your investigation playbooks.
- Templates: Common investigation & troubleshooting logics which can be used out of the box.
- Conditionals: Create decision trees in your playbooks basis evaluation of a playbook step.
- More integrations: Find something missing? Request here.
Step 1: We currently support setup using docker. Run the below command and signup on localhost to start creating playbooks.
git clone git@github.com:DrDroidLab/PlayBooks.git
docker-compose -f playbooks.docker-compose.yaml up -d
Step 2: Follow this Step-by-Step guide to do your first alert enrichment.
Asks questions in the Slack Community or write to us at founders [at] drdroid [dot] io