# Ewake Docs

- [About ewake](https://docs.ewake.ai/index.md)
- [Concepts](https://docs.ewake.ai/concepts.md): How ewake reasons over your production environment, the knowledge map, the cartographer, and how ewake acts on your behalf.
- [Quickstart](https://docs.ewake.ai/get-started/quickstart.md): Connect your stack and get your first ewake investigation in Slack in under 8 minutes.
- [Sign In](https://docs.ewake.ai/get-started/sign-in.md): Access your ewake dashboard with your organisation's single sign-on
- [Connect Slack](https://docs.ewake.ai/get-started/connect-slack.md): Connect Slack to enable @ewake mentions, alert routing, and proactive reports in your workspace.
- [Integrations Overview](https://docs.ewake.ai/integrations/overview.md): All integrations available in ewake, connect your stack in minutes.
- [Datadog](https://docs.ewake.ai/integrations/observability/datadog.md): Connect Datadog to give ewake access to your metrics, logs, traces, and monitors.
- [Grafana](https://docs.ewake.ai/integrations/observability/grafana.md): Connect Grafana to let ewake query your dashboards, metrics, and logs for incident correlation.
- [Prometheus](https://docs.ewake.ai/integrations/observability/prometheus.md): Connect Prometheus to give ewake access to your time-series metrics for anomaly detection and root cause analysis.
- [Thanos](https://docs.ewake.ai/integrations/observability/thanos.md): Connect Thanos to give ewake access to your long-term, global PromQL metrics for anomaly detection and root cause analysis.
- [VictoriaMetrics](https://docs.ewake.ai/integrations/observability/victoriametrics.md): Connect VictoriaMetrics to give ewake access to your time-series metrics for anomaly detection and root cause analysis.
- [Loki](https://docs.ewake.ai/integrations/observability/loki.md): Connect Grafana Loki to give ewake access to your log aggregation for real-time log analysis.
- [Tempo](https://docs.ewake.ai/integrations/observability/tempo.md): Connect Grafana Tempo to give ewake access to your distributed traces for latency analysis and root cause investigation.
- [ClickHouse](https://docs.ewake.ai/integrations/observability/clickhouse.md): Connect ClickHouse to give ewake access to your distributed traces for latency analysis and root cause investigation.
- [CloudWatch](https://docs.ewake.ai/integrations/observability/cloudwatch.md): Connect Amazon CloudWatch to give ewake read-only access to your AWS logs, metrics, and alarms via a secure cross-account IAM role.
- [Elasticsearch](https://docs.ewake.ai/integrations/observability/elasticsearch.md): Connect Elasticsearch to give ewake access to your logs and metrics for incident analysis.
- [GCP Cloud Logging](https://docs.ewake.ai/integrations/observability/gcp-cloud-logging.md): Connect GCP Cloud Logging to let ewake query your application and infrastructure logs for incident investigation.
- [Kubernetes](https://docs.ewake.ai/integrations/infrastructure/kubernetes.md): Let ewake read pods, events, logs, and deployment state from your cluster, and act on it if you allow — you decide the access, with no inbound ports.
- [Argo CD](https://docs.ewake.ai/integrations/infrastructure/argocd.md): Connect Argo CD to give ewake read-only visibility into your GitOps delivery — application sync status, health, and deployed revision — to correlate incidents with deployments.
- [Custom MCP Server](https://docs.ewake.ai/integrations/custom/custom-mcp.md): Connect any MCP server you run so ewake can call your own tools during investigations.
- [Incident.io](https://docs.ewake.ai/integrations/alerting/incident-io.md): Connect Incident.io to let ewake auto-investigate new incidents and build a knowledge map from your incident history.
- [Rootly](https://docs.ewake.ai/integrations/alerting/rootly.md): Connect Rootly to give ewake read access to your incidents so it can pull live incident context into investigations.
- [FireHydrant](https://docs.ewake.ai/integrations/alerting/firehydrant.md): Connect FireHydrant to let ewake reference your incident history and retrospectives during investigations.
- [PagerDuty](https://docs.ewake.ai/integrations/alerting/pagerduty.md): PagerDuty integration is coming soon.
- [GitHub](https://docs.ewake.ai/integrations/code/github.md): Connect GitHub to let ewake correlate production issues with deployments and code changes.
- [GitHub App (self-hosted)](https://docs.ewake.ai/integrations/code/github-app-self-hosted.md): Create a GitHub App in your own organisation and let a self-hosted Ewake deployment act as it. This is how GitHub is connected on a self-hosted deployment.
- [GitLab](https://docs.ewake.ai/integrations/code/gitlab.md): Connect GitLab to let ewake correlate production issues with merge requests, deployments, and infrastructure code changes.
- [Gerrit](https://docs.ewake.ai/integrations/code/gerrit.md): Gerrit integration is coming soon.
- [Confluence](https://docs.ewake.ai/integrations/knowledge/confluence.md): Confluence integration is coming soon.
- [Notion](https://docs.ewake.ai/integrations/knowledge/notion.md): Connect Notion in one click to let ewake search your runbooks and internal docs — with AI search over their full content offered in the same flow.
- [Jira](https://docs.ewake.ai/integrations/project-management/jira.md): Connect Jira over Atlassian Rovo MCP or the REST API to give ewake read access to your issues — and, over MCP, your Confluence pages and semantic search.
- [Linear](https://docs.ewake.ai/integrations/project-management/linear.md): Connect Linear to let ewake create issues from incidents and surface relevant in-progress work.
- [Deployment Tracking](https://docs.ewake.ai/integrations/deployment/deployment-tracking.md): Send deployment events to ewake from any CI/CD pipeline, with a GitHub Action or a plain curl, to enable deployment-correlated incident analysis.
- [Dashboard](https://docs.ewake.ai/working-with-ewake/dashboard.md): The ewake dashboard is where you configure integrations, set up the On-Call Agent and Scheduled Tasks, and manage your API keys.
- [On-Call Agent](https://docs.ewake.ai/working-with-ewake/on-call-agent.md): Investigate alerts the moment they fire in Slack, act on your behalf, and escalate only what needs your team.
- [Scheduled Tasks](https://docs.ewake.ai/working-with-ewake/scheduled-tasks.md): Receive proactive system health reports, anomaly summaries, and reliability signals on a schedule you define.
- [Incident Response](https://docs.ewake.ai/working-with-ewake/incident-response.md): Run an investigation alongside your team during a live incident, ewake correlates signals across your stack while engineers debate the fix.
- [Evaluations](https://docs.ewake.ai/working-with-ewake/evaluations.md): Judge ewake on your own alerts — replay ones that already fired and rate the answers, or route live alerts to a channel only you are watching.
- [Skills](https://docs.ewake.ai/working-with-ewake/skills.md): Write team playbooks that ewake applies automatically when it encounters a matching situation.
- [Giving Feedback](https://docs.ewake.ai/working-with-ewake/giving-feedback.md): How to judge an ewake investigation and leave a 👍 or 👎 that teaches it the right lesson.
- [Interacting with the Agent](https://docs.ewake.ai/working-with-ewake/interacting-with-the-agent.md): How your team interacts with ewake in day-to-day use, on-demand questions, automated responses, and thread follow-ups.
- [Prompt Library](https://docs.ewake.ai/working-with-ewake/prompt-library.md): Copy-paste prompts by use case, send them to @ewake in any Slack channel.
- [MCP Server](https://docs.ewake.ai/interfaces/mcp.md): Connect ewake to Claude Code, Cursor, or any MCP client, and query your service map and past investigations from your editor.
- [Setup skills for coding agents](https://docs.ewake.ai/interfaces/setup-skills.md): Install four skills for your coding agent. With the skills, your coding agent can connect to ewake, report deployments from your pipeline, map your services, and check the setup.
- [Permissions & Data Access](https://docs.ewake.ai/security/permissions.md): Complete matrix of what ewake can access in each integration, scope by scope, and how it takes action. The page InfoSec teams need.
- [AGENTS.md](https://docs.ewake.ai/agents.md): Context file for AI agents and coding assistants integrating with ewake. Read this before issuing tool calls.
- [FAQ](https://docs.ewake.ai/faq.md): Frequently asked questions about ewake.
- [Contact Support](https://docs.ewake.ai/support.md): Send us a message, we typically reply within a few hours.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.