Skip to content

MVC GitLab and Opsgenie Integration

Problem to solve

Opsgenie is a popular tool for operations tasks, specifically ITSM related alerts and incident management. To validate GitLab investment in a bi-directional integration with Opsgenie, we want to pursue an MVC that demonstrates how we might relate the two applications. The purpose of the MVC will be to establish community awareness and to generate excitement and questions from joint customers which will inform how we choose to integrate.

Intended users

User experience goal

Allow users to communicate their desire to integrate GitLab with Opsgenie and get an initial taste of what an integration into GitLab's single application would look like.

Proposal

  • Allow users to add an Opsgenie integration in Settings > Operations
  • If the user utilizes the Opsgenie integration - we could either show a link to Opsgenie within the list view (allowing them to still utilize the GitLab endpoint functionality, if they want to) or utilize the list empty state to link to Opsgenie
  • Instrument metrics to track:
    • How many projects have activated the OpGenie Integration (usage ping?)
    • How many users viewed the Opsgenie Integration tab (snowplow)

Pricing

The integration between Opsgenie and GitLab Operations will be launched in the Premium pricing tier for GitLab. Based on the GitLab's buyer based pricing model, the buyer for this integration is likely a Director+ who wants processes and workflows to remain in Atlassian products while integrating with Gitlab where they use SCM and CI.

Design

For a very first pass at an Opsgenie integration, we've decided on the following:

First empty state Configuration page Updated empty state
First_empty_state Settings_page_-expanded-_alert_endpoint Empty_state_-_OpsGenie_enabled
  • On the first empty state - some small text tweaks required to the existing empty state to remove the reference to displaying alerts directly in GitLab.
  • On the config page - since we've already planned to build #218572 (closed) in 13.2, we would just need to add another item for Opsgenie to the integrations dropdown.
  • When Opsgenie is enabled, we can show an updated empty state linking users directly to Opsgenie.

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited by Peter Leitzen