What is it?
Link your git provider to ApiTraffic and every push, tag, and release is automatically turned into an event marker on your dashboard — no CI glue required. You’ll see exactly which code change lines up with a change in throughput, error rate, or latency.
How it works
1
Connect your provider
An account admin links ApiTraffic to GitHub, GitLab, or Bitbucket once.
2
Assign a repository to a bucket
Pick a repo and the ApiTraffic bucket whose traffic it powers.
3
Map branches to environments
e.g.
main → Production, release/* → Staging. Pushes to unmapped branches are ignored.4
Push code
We receive the webhook and create an event marker on the matching bucket + environment automatically.
Before you start
Connecting a provider and managing repositories is admin-only — you must be the primary user on the ApiTraffic account.
- A GitHub, GitLab (gitlab.com), or Bitbucket Cloud account with admin access to the repository you want to track.
- At least one ApiTraffic bucket and one environment already created.
Provider guides
GitHub
Install the ApiTraffic GitHub App.
GitLab
Authorize via OAuth (gitlab.com).
Bitbucket
Authorize via OAuth (Bitbucket Cloud).
What gets tracked
Managing repositories and branch mappings
Once connected, go to Settings → Integrations → Git to assign repositories and edit branch mappings at any time.
Troubleshooting
I pushed but no marker appeared
I pushed but no marker appeared
The branch is probably not mapped to an environment. Only pushes to mapped branches create markers — check the branch mapping table for the repository.
My connection shows "Reconnect needed"
My connection shows "Reconnect needed"
The provider access token expired or was revoked. Click Reconnect to re-authorize.
Too many markers on my chart
Too many markers on my chart
Turn off one marker per commit for the repository so each push produces a single
git.push marker.