Skip to content

GitLab integration

Connect DXDT to GitLab (gitlab.com or self-managed) with a read-only token so the platform can correlate incidents against commits, merge requests, pipelines, and releases. DXDT only reads.
Setup time ~8 minutes
Difficulty Easy

Access required: GitLab access token with read_api scope

Prerequisites

  • A GitLab account with access to the target projects or groups
  • Ability to create a Personal, Project, or Group Access Token
  • For self-managed GitLab, your instance base URL

Setup

1. Create an access token

In GitLab go to your avatar → Edit profile → Access tokens (Personal), or a group/project's Settings → Access tokens to scope more narrowly. Click Add new token.

  • Personal: Edit profile → Access tokens
  • Or Group/Project: Settings → Access tokens
  • Click Add new token

2. Select the read-only scope

Give the token a name like DXDT and select only the read_api scope. Do not grant api, write_repository, or any write scope. Set an expiry and create the token, then copy it — it is shown only once.

Note

read_api is sufficient for all of DXDT's read commands.

3. Identify your base URL

For gitlab.com, leave base_url blank. For self-managed GitLab, set it to your instance URL, e.g. https://gitlab.example.com.

Note

DXDT appends /api/v4 automatically — omit it.

4. Enter the values in DXDT

In the plugin Configuration tab, paste the Token (and Base URL if self-managed) and save. DXDT validates with a read-only ping.

Configuration fields

Field Where to find it
Token (token) A Personal/Project/Group Access Token with the read_api scope.
Base URL (base_url) Blank for gitlab.com; your instance URL (e.g. https://gitlab.example.com) for self-managed.

Verify the connection

Save on the Configuration tab and confirm the Live Status panel is healthy; DXDT runs a read-only ping showing the token user, then can list projects.

Security

Credentials are stored encrypted per-tenant and used only for read-only GitLab calls.

Troubleshooting

401 Unauthorized

Invalid, expired, or mistyped token. Create a new token with read_api and re-enter it.

403 or missing projects

The token scope or the user's project membership is too narrow. Ensure read_api is selected and the token owner is a member of the relevant projects/groups.

Cannot reach instance (self-managed)

Wrong or missing base_url. Set base_url to the instance root without /api/v4; leave blank for gitlab.com.

Vendor documentation: https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html