You must be an ApiTraffic account admin, and have the Maintainer or Owner role on any GitLab project you want to track (that role is required to add project webhooks). GitLab.com (cloud) is supported today; self-managed GitLab is not yet.
1. Start the connection
In ApiTraffic, go to Settings → Integrations → Git and click Connect GitLab.
2. Authorize ApiTraffic
You’ll be redirected to GitLab to sign in and approve the requested scopes (read your projects and manage their webhooks). Click Authorize.
3. Assign a project to a bucket
Back in ApiTraffic, your connection now shows as Active. Pick a project and choose the bucket whose API traffic that code powers. ApiTraffic registers the push/tag/release webhook on that project automatically.
4. Map branches to environments
Add one or more rows mapping a branch (or pattern) to an environment. First matching rule (by priority) wins; you can mark one row as the default fallback.
5. Verify
Push a commit to a mapped branch. Within a few seconds agit.push marker appears on that bucket’s charts.
Disconnecting
- In ApiTraffic: Settings → Integrations → Git → Disconnect removes the link, deletes the webhooks ApiTraffic created, and stops tracking.
- In GitLab: you can also revoke the ApiTraffic authorization under GitLab → Preferences → Applications.
Troubleshooting
A project I want isn't listed
A project I want isn't listed
ApiTraffic only lists projects your GitLab user is a member of. Confirm your membership, then refresh the ApiTraffic project list.
No marker after pushing
No marker after pushing
Confirm the branch you pushed to is mapped to an environment — unmapped branches are intentionally ignored — and that the ApiTraffic webhook still exists under the project’s Settings → Webhooks.
Connection shows an error / expired
Connection shows an error / expired
OAuth tokens expire. ApiTraffic refreshes them automatically, but if the refresh fails (for example the authorization was revoked) the connection is marked Error. Click Reconnect to re-authorize.