GitLab integration
Connect GitLab so Errorgap triage can link production failures to issues, merge requests, and deploy context.
Use GitLab when your team tracks source, issues, merge requests, or deploys there. Errorgap keeps runtime evidence, while GitLab keeps implementation discussion and code review.
What GitLab is for
- Create or link issues from actionable error groups.
- Use repository and release context to identify likely changed code.
- Keep a production failure linked to the work that fixes it.
Connect a project
- Open the project settings.
- Select Integrations, then GitLab.
- Choose the project or repository that owns the monitored service.
- Save and test by linking a safe error group.
Use with errors
Link existing GitLab work when a fix is already underway. Create new work when the error needs investigation, code changes, or release tracking.
Release context
Compare first seen time, release values, and recent merge requests before assigning cause to a deploy. Use Errorgap evidence to narrow the likely files and GitLab to review the change.
Troubleshooting
- Confirm the selected repository is the one that owns the service.
- Check that your GitLab permissions allow issue or merge request access.
- Use an existing issue link first if duplicate issue creation is a concern.