Sentry’s GitLab integration helps you track and resolve bugs faster by using data from your GitLab commits. Additionally, you can streamline your triaging process by creating a GitLab issue directly from Sentry.


  1. Navigate to Settings > Integrations > GitLab.

    Install GitLab integration

  2. In the resulting modal, click "Add Installation".

    Connect Sentry to a GitLab instance

  3. In the pop-up window, complete the instructions to create a Sentry app within GitLab. Once you’re finished, click "Next".

    Configuration modal and Sentry app within GitLab

  4. Fill out the resulting GitLab Configuration form with the following information:

    1. The GitLab URL is the base URL for your GitLab instance. If using, enter

    2. Find the GitLab Group Path in your group’s GitLab page. Groups might contain subgroups and projects. You should not specify the URL to any specific

      projectRepresents your service in Sentry and allows you to scope events to a distinct application.
      , just to a group or subgroup.

      GitLab page showing group path

    3. Find the GitLab Application ID and Secret in the Sentry app within GitLab.

      GitLab application id and secret

    4. Use this information to fill out the GitLab Configuration and click "Submit".

      GitLab configuration form

  5. In the resulting panel, click "Authorize".

  6. In Sentry, return to Organization Settings > Integrations. You’ll see a new instance of GitLab underneath the list of integrations.

  7. Next to your GitLab Instance, click "Configure". It’s important to configure to receive the full benefits of commit tracking.

    GitLab instance with connected group and highlighted configure button

  8. On the resulting page, click "Add Repository" to select which repositories in which you’d like to begin tracking commits.

    Add repository


Use GitLab to track commits, identify suspect commits, resolve via commit or PR and manage issues.

Issue Management

Issue tracking allows you to create GitLab issues from within Sentry and link Sentry issues to existing GitLab issues.

  1. Select your issue

    List of unresolved issues

  2. Navigate to Linked Issues on the right panel of the issue's page and click "Link GitLab Issue".

    GitLab logo with Link GitLab Issue text

  3. You have two options to complete the issue link:

    1. In the pop-up, you can fill out the appropriate details in the Create tab, and then click "Create Issue".

      pop-up modal to create issue

    2. Or, in the pop-up, you can click the Link tab, search the issue by name, and then click "Link Issue". Issues aren't currently searchable by number.

      pop-up modal to search issue name

  4. To unlink an issue, click on the "X" next to its name under Linked Issues.

    GitLab logo and project next to an X icon

Commit Tracking

Commit tracking allows you to hone in on problematic commits. With commit tracking, you can better isolate what might be problematic by leveraging information from releases like tags and metadata.

Once you've configured both release and commit tracking, you'll be able to see more thorough information about a release: who made commits, which issues were newly introduced by this release, and which deploys were impacted.

Dashboard with last commit highlighted

When you investigate deeper into that commit, you can leverage information from metadata like tags.

Issue detail highlighting tags

Broadly, this lets you isolate problems in order to see which commits might be problematic.

Learn more about release and commit tracking.

Resolve via Commit or Pull Request

Once you've added a repository (see configuration step 8), you can start resolving issues by including fixes <SHORT-ID> in your commit messages. You might want to type something in the commit like: "this fixes MyApp-AB12" or "Fixes MyApp-317". The keyword to include is fixes. You can also resolve issues with pull requests by including fixes <SHORT-ID> in the title or description. This will automatically resolve the issue in the next release.

A <SHORT-ID> may look something like 'BACKEND-C' in the image below.

Issue detail highlighting suspect commits

Stack Trace Linking

Stack trace linking takes you from a file in your Sentry stack trace to that same file in your source code. If you have commit tracking set up in Sentry, we can take you to the exact version (using the commit associated with the event) of the source code when the error occurred. Otherwise we'll link you to the current state of the source code (using the default branch).

  1. Navigate to Settings > Integrations > GitLab > Configurations.

  2. Click the "Configure" button next to your GitLab Instance.

  3. Click the Code Mappings tab.

  4. Set up a code mapping for each

    projectRepresents your service in Sentry and allows you to scope events to a distinct application.
    for which you want to enable stack trace linking. To create a new code mapping, click Add Mapping.

  5. Fill out the form, then click Save Changes. Each form field is described below:

    • Project (required): This is the Sentry project.
    • Repo (required): This is the GitLab project associated with the Sentry project above. If you have more than one GitLab project being used per Sentry project, you'll need multiple code mappings.
    • Branch (required): This is the default branch of your code we fall back to if you do not have commit tracking set up.
    • Stack Trace Root and Source Code Root (optional): See below for information on determining these values.

Stack Trace Root and Source Code Root

First, navigate to a stack trace that you wish to map. Find an In App frame, which is denoted by a bubble on the right side of the frame. The filename will be shown as the first piece of text at the left hand side of the frame header. In this example, it is src/

Highlighting where in the UI to find the file name in the stack trace

If you aren’t sure, you can look at the event JSON by clicking on the {} button in the event header. Find the text in the frame's filename.

Highlighting where in the UI to find the event JSON

Next, locate the file seen in the stack trace with your source code provider (e.g. GitHub). In this example, the path is flask/src/ (empower is ignored since it is the name of the repo).

An example of a file in source control

Compare the file path from the stack trace with the path found in your source repository. In this example, the src/ folder in the stack trace matches the flask/src folder in the source code. Using that information, set the Stack Trace Root to src/ and the Source Code Root to flask/src/. This tells Sentry to replace all file paths beginning in src/ with flask/src/ when searching for the source code.

For best results, we recommend always providing a non-empty value for the Stack Trace Root when possible.

An example of a completed code mapping

Suspect Commits

Once you've set up stack trace linking, Sentry can use information from your source code provider to suggest the commit that likely introduced the error. The first frame in the stack trace is considered suspect when looking at them top-down. If the first frame is not in-app, the next frame is considered suspect.

After pinpointing the suspect commit, you can also identify the developer who made the commit and assign them the task of fixing the error.

Issue detail highlighting suspect commits

Learn about setting up this functionality in Suspect Commits.

Code Owners

Import your existing GitLab CODEOWNERS files to automatically assign Sentry issues and route alerts to the responsible individuals and teams.

For more details, see the full documentation for Code Owners.


  • I'm using GitLab on-premises. Do I need to allow Sentry's IP addresses?

    • Yes. You can find our IP ranges here .
    • Verify the provided installation URL is a fully qualified domain name (FQDN), which is resolvable on the internet.
    • Make sure that Sentry's access to your installation URL is not path restricted.
    • To add the GitLab repo, navigate to GitLab > Admin area > Settings > Network > Outbound requests > Allow requests to the local network from hooks and services and enable the option.
  • I'm using both GitLab on-premises and self-hosted Sentry, and I get an error Error Communicating with GitLab (HTTP 422): unknown error when I try to use the integration. How can I fix this?

    • By default, GitLab does not allow Hooks to communicate with the local private network, which prevents the integration with Sentry from working. To enable local network communication in GitLab, enable "Allow requests to the local network from hooks and services" on the Admin > Settings > Network page.
  • Do you support subgroups?

    • Currently, we only support subgroups for users using GitLab 11.6 or higher.
  • My repositories are hosted under my user account, not a group account. Can I still use this integration?

    • Unfortunately, not. The GitLab integration only works for repositories that are hosted under group accounts.
  • Are there pricing restrictions?

  • Who has permission to install this?

    • You must have both owner/manager/admin permissions in Sentry and owner permissions in GitLab to successfully install this integration.
  • Why am I getting a 500 response during installation or configuration?

    • First, make sure you’ve allowed our IPs, which can be found here. The 500 response is coming from GitLab, so you may need to try again or double-check that your settings and permissions are correct in GitLab. You must have both owner/manager/admin permissions in Sentry as well as owner permissions in GitLab to successfully install this integration.
  • Why am I seeing an "Invalid Repository Names" error?

    • GitLab takes into account the whitespace before and after the / . On the Repositories page (Organization Settings > Repositories), you’ll notice a space (for example, "Owner / Repo" as opposed to "Owner/Repo"), which will need to be included in any command you’re running. If you are using GitLab’s environment variables to pass the repository as CI_PROJECT_PATH in a cURL request for example, it may not include the spaces and you’ll need to hardcode the name in order for it to work.
  • Why am I always the reporter?

    • When using the GitLab integration to create issues, the “reporter” field is populated as the person who set up the integration by default — this is not configurable.
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").