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 have at the end: ewake mapped to your production system, continuously building context across your services, and ready to investigate issues with ranked hypotheses, supporting signals, and suggested actions.
Connect your tools
Connect your telemetry, development, and productivity tools. This gives ewake access to alerts, production signals, and deploy history.
Slack
Required. Alerts, reports, and
@ewake mentions all go through Slack.Datadog
Required. Ewake queries your metrics, logs, traces, and monitors.
GitHub
Required. Ewake correlates alerts with deployments and code changes.
Your stack is connected
To confirm everything is working, mention 
@ewake in any Slack channel where the bot is present and ask a simple question:If ewake responds with a structured investigation, your connection is working.
With just your stack connected, ewake can already answer on-demand questions. These responses are useful, but limited, ewake hasn’t been configured to watch for alerts or run scheduled analysis yet. The next step is where it becomes proactive.
Put ewake to work
Pick the use case that fits your team’s first priority, each one configures in a few minutes from the Dashboard.Once you’ve set up one or more use cases, you’ll find more relevant prompts tailored to your configuration here:
On-Call Agent
Automatically investigate every alert that fires in Slack, before your engineer opens a terminal.
Scheduled Tasks
Deliver proactive health reports and anomaly summaries on a schedule you define.
Incident Response
Run real-time investigations during a P0 or war room, on demand.
Prompt Library →
Have feedback or questions? Reach the team at support@ewake.ai.