> ## 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.
# Quickstart
> Connect your stack and get your first ewake investigation in Slack in under 8 minutes.
**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.
***
Open your ewake instance URL and click **Continue with Google**.
Connect your telemetry, development, and productivity tools. This gives ewake access to alerts, production signals, and deploy history.
Required. Alerts, reports, and `@ewake` mentions all go through Slack.
Required. Ewake queries your metrics, logs, traces, and monitors.
Required. Ewake correlates alerts with deployments and code changes.
To confirm everything is working, mention `@ewake` in any Slack channel where the bot is present and ask a simple question:
```
@ewake What's the health of [my-service] right now?
```
```
@ewake Any anomalies in the last 24 hours?
```
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.
Pick the use case that fits your team's first priority, each one configures in a few minutes from the Dashboard.
Automatically investigate every alert that fires in Slack, before your engineer opens a terminal.
Deliver proactive health reports and anomaly summaries on a schedule you define.
Run real-time investigations during a P0 or war room, on demand.
Once you've set up one or more use cases, you'll find more relevant prompts tailored to your configuration here:
***
Have feedback or questions? Reach the team at [support@ewake.ai](/support).