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
- Owner access to your top-level GitLab group (GitLab.com) or administrator access (self-managed), required to create a service account
- Access to your ewake dashboard
Connect ewake with a dedicated service account rather than a personal access token. A service account isn’t tied to an individual, so access survives staff changes, stays least-privilege and auditable, and won’t break when someone leaves or rotates their own tokens. This is GitLab’s recommended pattern for integrations.
Configuration
Follow the steps for your GitLab deployment.- GitLab.com (SaaS)
- Self-managed
Create a service account
As a top-level group Owner, use Search or go to to open your group, then go to Settings → Service accounts → click Add service account.Enter a name (e.g.
ewake) and click Create service account.Create an access token for the service account
On the Settings → Service accounts page, find the service account, open the ⋮ (vertical ellipsis) menu → Manage access tokens → Add new token.Select the following scopes:
Set an expiry date and click Create personal access token.
| Scope | Why |
|---|---|
read_api | Read project data, merge requests, pipelines, and deployments |
read_repository | Read source code and diffs |
Copy the token now, GitLab will not show it again after you leave this page.
Give the service account access to your projects
Add the service account as a member of each group or project you want ewake to monitor (Manage → Members → Invite members) with the Reporter role.
A token with no project membership reads nothing. Reporter is the minimum role required to read code, merge requests, and pipelines on private projects, and adding the service account at the group level covers every project inside that group.
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 |
| Personal Access Token | The service account token created in Step 2 |
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.
Track deployments from GitLab CI/CD →
Send deployment events to ewake directly from your CI/CD pipeline.
What does ewake access in GitLab? →
Full read-only permission breakdown for the GitLab integration.