Skip to main content

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.

Send these to @ewake in any Slack channel where the bot is present. Ewake will query your connected tools and return a structured, evidence-backed answer.
Replace [service-name] with the name of your service as it appears in Datadog.

On-Call Agent

Use these when an alert fires and you need to understand what happened, fast.
@ewake What triggered this alert?
@ewake What changed on [service-name] in the last hour?
@ewake Is this alert correlated with a recent deployment?
@ewake Has this alert fired before? What resolved it last time?

Configure the On-Call Agent →


Incident Response

Use these during a P0 or war room, when the team is actively debating the problem.
@ewake Summarize this incident for me before I join the call.
@ewake What's the root cause of the current degradation on [service-name]?
@ewake Which services are affected downstream from [service-name]?
@ewake What are the most likely fixes based on similar past incidents?
@ewake Draft a status update I can share with stakeholders right now.

Configure Incident Response →


Scheduled Tasks

Use these for proactive health checks, morning reviews, pre-deploy checks, on-call handoffs.
@ewake Give me the daily health digest for my services.
@ewake Is [service-name] healthy enough to deploy right now?
@ewake What should I know before I start my on-call shift?
@ewake Generate a weekly reliability report for [service-name].
@ewake Any anomalies overnight I should address this morning?

Configure Scheduled Tasks →


Quick questions

Short-form questions you can ask at any time.
@ewake What's the health of [service-name] right now?
@ewake What are the top errors in [service-name] right now?
@ewake Why is [service-name] slow right now?
@ewake Show me error spikes in [service-name] this week.
@ewake Were there any deployments in the last 24 hours I should know about?

Time scoping

Ewake defaults to the last 1 hour when no time window is specified. You can override it using plain language, relative or absolute:
@ewake Any anomalies since yesterday?
@ewake Show me errors on [service-name] from 9am to 11am.
@ewake What changed on [service-name] in the last 15 minutes?