Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

New GitLab integration in Incident Investigation view

We launched the first version of the Incident investigation view in April of 2020 for Bitbucket Pipelines. Shortly after that, we added the ability to investigate deployment-related incidents in Opsgenie from other tools with the creation of our Deployment API.

Today, we're proud to take that flexible approach one step further with the launch of Incident Investigation for GitLab. Now you can investigate your GitLab CI/CD deployments using Opsgenie’s Incident Investigation view, empowering your responders to investigate, identify root cause, and resolve incidents faster.

Let’s walk through how to set it up.

Note: This integration requires you to have GitLab Ultimate because it utilizes group-level web-hooks.

To begin investigating your GitLab CI/CD deployments, connect your GitLab and Opsgenie accounts by selecting the 'Add Connection' button in the GitLab integrations page under global settings.


When you authenticate GitLab you will be able to see the top-level groups from your account that you can connect to your Opssgenie account.


Back in Opsgenie on the Integrations page, all connected groups are listed. Admins can remove GitLab groups connected to Opsgenie, however, new groups can only be added by the GitLab account owner of the groups.


Once the GitLab group is connected to Opsgenie, it’s time to map the GitLab project under the connected GitLab Groups to Opsgenie services.



Next, it’s time to add mappings to each service. You need to manually select each project that you want to map to your services in Opsgenie.



The screenshot below shows that all connected projects listed on the Service settings page.



Now here we are inside the Incident Investigation view. We can see the deployment history for the services in question, and we can click in to get more detail on each deployment and commit. Note that we cannot currently see file changes in this view, but we hope to add that functionality to a future version.


Once the potential cause of an incident has been identified, it is added automatically to the incidents details screen, as shown below.




If you’re using GitLab and Opsgenie together we would love to hear your feedback on the first version of this new connection. Please leave a comment below!

Opsgenie GitLab documentation


Is this only available for the standalone version of Opsgenie? The Jira Service Management integrated Opsgenie does not have the Gitlab settings?

Like Sarjeel Syed Yusuf likes this

Hey @Gary Blower yes it is only available for the standalone version. We are working on introducing it for JSM too. 

Like Gary Blower likes this


Log in or Sign up to comment
Community showcase
Published in Opsgenie

Leveraging Atlassian’s Opsgenie and AWS Cloudformation Registry to stay ahead of incidents

In the past, managing IT infrastructure was a hard job. It required a lot of manual effort and it was hard to keep track of all the necessary information (monitoring, scalability etc). Thankfully, as...

1,826 views 0 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you