GitLab is a web-based DevOps lifecycle tool that provides a Git repository manager providing wiki, issue-tracking and continuous integration and deployment pipeline features, using an open-source license, developed by GitLab Inc.
AlertOps’ alert management system can be integrated with GitLab to receive and respond to all (predefined status mappings) alerts through email, SMS, push notification or phone alerts. AlertOps would ensure that the alert/job status would reach the appropriate team by using proper workflows, escalation policies and schedules. Based on your ruleset, incidents can be automatically opened and closed, depending on what event GitLab triggers
The above scenario and scope for integration is due to the fact that AlertOps has a very flexible and simple API/Webhook configuration feature that can be leveraged with GitLab’s event notification capabilities.
You can send alerts from GitLab to AlertOps.
- AlertOps will automatically create an incident when a new alert is received from GitLab when the object_attributes^action field contains “open” or “reopen”. (this is for GitLab issues)
- If an alert with status “open” or “reopen” matches an existing Open Alert, AlertOps will recognize the new alert as a duplicate and ignore the alert.
- The alert will be recorded in the Inbound Messages table as “Mapped Appended.”
- AlertOps will automatically close the same incident when an alert with object_attributes^action contains ‘close’.
These are examples of just some of the things you can do with GitLab and AlertOps.
