Visualize GitLab users, groups, code repositories, and merge requests, map GitLab users to employees and development/security trainings, and monitor changes through queries and alerts.
- Installation guide
- GitLab data model
To use this integration, JupiterOne requires a GitLab personal access token configured with read access and the API base URL, such as https://gitlab.com).
To install the GitLab integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select GitLab. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
Account Name by which you'd like to identify this GitLab account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen Tag with Account Name is selected.
Description that will further assist your team when identifying the integration instance.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration.
Personal Access Token configured for read access in GitLab.note
Once your token has expired, the integration will no longer run successfully, and the token will be revoked from your GitLab account. You will need to create another token to replace the expired one.
Your GitLab API Base URL (e.g.,
https://gitlab.com, or your self-managed instance URL).
Click Create after all values are provided to finalize the integration.
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
The following entities are created:
|Resources||Entity ||Entity |
The following relationships are created:
|Source Entity ||Relationship ||Target Entity |