# GitLab version tags

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fdeveloper-portal%2Fapis%2Fversion-tags%2Fgitlab-version-tags.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fdeveloper-portal%2Fapis%2Fversion-tags%2Fgitlab-version-tags.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

Tell Coralogix when a new build ships, straight from your [GitLab](https://coralogix.com/docs/integrations/contextual-data/gitlab-data-ingestion.md) deployment pipeline. A pipeline webhook creates a version tag, which is what version benchmark reports compare behavior across.

## What you need [​](#what-you-need- "Direct link to what-you-need-")

* Access to your GitLab project's settings.
* A personal or team [API key](https://coralogix.com/docs/user-guides/account-management/api-keys/api-keys.md) with the `CICDIntegration` preset. Presets pick up new permissions automatically; individual permissions have to be maintained by hand.
* The GitLab version tags endpoint for your Coralogix [domain](https://coralogix.com/docs/user-guides/account-management/account-settings/coralogix-domain.md). Use the domain selector at the top of this page to resolve it:
  <!-- -->
  https\://api./api/v1/external/gitlab

| Preset          | Actions                                                                                                   | Grants                                                                                             |
| --------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| CICDIntegration | `VERSION-BENCHMARK-TAGS:READ`<br />`VERSION-BENCHMARKS-REPORTS:READ`<br />`VERSION-BENCHMARK-TAGS:UPDATE` | View version benchmark tags<br />View version benchmark reports<br />Modify version benchmark tags |

## Add the webhook in GitLab [​](#add-the-webhook-in-gitlab- "Direct link to add-the-webhook-in-gitlab-")

1

<!-- -->

.

Open the webhook settings

Sign in to GitLab, open your project, then select **Settings**, then **Webhooks**.

2

<!-- -->

.

Enter the URL

Build the URL from the GitLab endpoint for your domain and the query parameters below.

```
https://api.eu2.coralogix.com/api/v1/external/gitlab?application=APPLICATION_NAME&subsystem=SUBSYSTEM_NAME&name=TAG_NAME
```

| Parameter     | What to enter                                                                                                                                                                                                                                |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `application` | [Application name](https://coralogix.com/docs/user-guides/account-management/account-settings/application-and-subsystem-names.md) as it appears in your Coralogix UI                                                                         |
| `subsystem`   | [Subsystem name](https://coralogix.com/docs/user-guides/account-management/account-settings/application-and-subsystem-names.md) as it appears in your Coralogix UI. Separate multiple names with commas                                      |
| `name`        | The tag name. Omit it and Coralogix derives one from the GitLab payload's `project.name` and `object_attributes.ref` fields. See [pipeline events](https://docs.gitlab.com/ee/user/project/integrations/webhook_events.html#pipeline-events) |

3

<!-- -->

.

Add the secret token

Enter your API key in **Secret Token**, below the URL. This field is required. GitLab sends it in the `X-Gitlab-Token` header, and Coralogix rejects requests without it.

4

<!-- -->

.

Trigger on pipeline events

Under **Trigger**, select **Pipeline events**, then select **Save changes**.

[![GitLab webhook form with the Coralogix URL entered, a Secret Token field, and Pipeline events selected under Trigger](/docs/assets/images/Screen-Shot-2017-06-04-at-22.07.28-1024x825-554656530f3fabaa95ec8ba62d39c862.webp)](https://coralogix.com/docs/assets/images/Screen-Shot-2017-06-04-at-22.07.28-1024x825-554656530f3fabaa95ec8ba62d39c862.webp)

Shows the trigger that fires a version tag each time a pipeline's status changes.

## Related resources[​](#related-resources "Direct link to Related resources")

[GitLab data ingestion](https://coralogix.com/docs/integrations/contextual-data/gitlab-data-ingestion.md)[API keys](https://coralogix.com/docs/user-guides/account-management/api-keys/api-keys.md)[Coralogix endpoints](https://coralogix.com/docs/integrations/coralogix-endpoints.md)