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: After connecting GitLab, ewake can correlate production issues with recent merge requests and deployments, surface the diff that likely caused a regression, and analyse infrastructure-as-code changes (Terraform, Kubernetes manifests) alongside application code.
Prerequisites
- A GitLab account with Owner or Maintainer access to the groups or projects you want to connect
- Access to your ewake dashboard
Configuration
Create a Personal Access Token in GitLab
In GitLab, go to your avatar (top right) → Edit profile → Access Tokens → click Add new token.Give it a name (e.g.
Set an expiry date and click Create personal access token. Copy it immediately.
ewake) and select the following scopes:| Scope | Why |
|---|---|
read_api | Read project data, MRs, and pipeline info |
read_repository | Read source code and diffs |
Copy the token now, GitLab will not show it again after leaving this page.
Connect in ewake
In your ewake dashboard, go to Integrations → GitLab → click Configure.
Click Test Configuration, then Save.
| Field | Value |
|---|---|
| GitLab Base URL | https://gitlab.com (Cloud) or your self-hosted GitLab URL |
| Personal Access Token | The token created in Step 1 |
Select projects
Choose which GitLab projects ewake should monitor.
We recommend including all projects with production services. Infrastructure repos (Terraform, Kubernetes configs) are particularly valuable for ewake’s root-cause analysis.
GitLab is connected. Ewake can now correlate incidents with merge requests and deployments.
Ewake uses read-only access to GitLab. It never pushes commits, creates branches, or comments on merge requests.