19 lines
906 B
Markdown
19 lines
906 B
Markdown
---
|
|
stage: Monitor
|
|
group: Respond
|
|
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
|
---
|
|
|
|
# Incident management **(FREE)**
|
|
|
|
> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2877) in GitLab 13.0.
|
|
|
|
Incident Management enables developers to easily triage and view the alerts and incidents
|
|
generated by their application. By surfacing alerts and incidents where the code is
|
|
being developed, efficiency and awareness can be increased. Check out the following sections for more information:
|
|
|
|
- [Integrate your monitoring tools](integrations.md).
|
|
- Manage [on-call schedules](oncall_schedules.md) and receive [notifications](paging.md) for
|
|
triggered alerts.
|
|
- Triage [Alerts](alerts.md) and [Incidents](incidents.md).
|
|
- Inform stakeholders with [Status Page](status_page.md).
|