Documentation Index
Fetch the complete documentation index at: https://docs.ewake.ai/llms.txt
Use this file to discover all available pages before exploring further.
What you’ll get: A structured report delivered to your Slack channel on the schedule you define, morning health brief, overnight anomaly summary, weekly reliability digest, or pre-deploy check. You write the mission; ewake does the investigation.
What it does
Scheduled Tasks lets you configure ewake to run an autonomous analysis on a defined schedule and deliver the results to a Slack channel. You define what to look for (via a mission prompt), how far back to analyse, and when to deliver. Ewake does the rest, querying Datadog, correlating with recent deployments, and producing a structured report.When to use it
- You want a daily system health brief before standup
- You want an overnight anomaly report waiting for your team each morning
- You want a weekly reliability summary for leadership
- You want to proactively catch degradations before they become incidents
What you’ll get
[Screenshot to add: example ewake scheduled report in Slack, health summary with anomalies highlighted] A typical scheduled report includes:- System health summary, status of key services over the analysis window
- Anomalies detected, metrics or error rates outside normal baseline
- Notable changes, recent deployments that may have introduced risk
- Risk signals, patterns that historically precede incidents
Prerequisites
Slack
Alert source
Datadog, Grafana, PagerDuty, or others
GitHub
Incident.io
Includes historical incident patterns in health digests and reliability reports.
Deployment Tracking
Surfaces recent deployments in health reports, flag risky changes before they become incidents.
How to set it up
Name your schedule
Enter a unique name (alphanumeric, hyphens, and underscores only).Examples:
daily-health-brief, overnight-anomaly-report, weekly-reliability-summarySelect frequency
Choose how often the task runs:
| Frequency | Use case |
|---|---|
| Daily | Morning health brief, overnight summary |
| Weekly | Reliability report, team retrospective input |
| Monthly | Long-term trend analysis |
| Every N hours | High-frequency monitoring during incidents or releases |
Set the time (UTC)
Specify when the report should be delivered, in UTC 24-hour format.Example:
07:00 to deliver at 7 AM UTC (9 AM Paris time).Write a mission prompt
The mission prompt is the core instruction, it tells ewake what to look for.Examples:
Select a Slack channel
Choose where the report is delivered (e.g.
#monitoring, #engineering, #standup).Ewake must be present in this channel. Add it here →
Set hours to look back
Define the analysis window in hours. This determines how far back ewake looks when generating the report.Examples:
24 for a daily report, 168 for a weekly report.Need help setting this up? Contact support@ewake.ai.
