Our next-gen architecture is built to help you make sense of your ever-growing data Watch a 4-min demo video!
Formats: PNG, PDF, and SVG
Files size: 2.8 MB
For brand guidelines, please click here
Use Coralogix alerts and visualizations to gain insights into the status of repositories, branches, and activities such as commits and pulls, as well as to monitor any modifications to your GitLab repo. Consolidating all logs into Coralogix allows you to view application and infrastructure logs in the context of GitLab when doing root-cause or impact analysis.
The following tutorial demonstrates how to use webhooks to easily connect to your GitLab account.
Select a project from your projects or click on “New project” to create a new project.
If you click on one of the existing projects you already have, a new screen will open. In this screen, you want to select settings and select webhooks.
Complete the form and select the event for which you would like to trigger the collection. Refer to team URL based on the table below.
|Cluster URL||Team URL|
|Payload URL||Application Type||Secret|
|https://integrations.cluster URL/v1/gitlab/v1/events/<token>||application/json||This is the same as the token in the payload URL|
If you like to specify the application and subsystem name, add them after the token in the payload URL, as follows: https://integrations.<team url>/v1/gitlab/v1/events/<gitlab key token>?appName=<appname>&subSystem=<subsystem name>.
For example, for an EU team use: https://integrations.coralogix.com/v1/gitlab/v1/events/11111111-1111-1111-1111-111111111111?appName=MyApp&subSystem=MySubsystem
Make sure the URL endpoint corresponds with the domain of your account URL (.com, .in, .us). See table above.
Input your GitLab key token in the Secret token field.
Once you finish the configuration you want to click on add webhook.
You can also test your configuration and web-hook by clicking on test. If you get anything else besides 200 OK you might want to check the configuration.