Grafana OnCall - Insights from looking at a competitive incident management product
Assets
-
🎬 Speed Run (Part 1 of 2), Speed Run (Part 2 of 2) -
🎁 Features and Screenshots -
Related Direction Page, Category Direction - Incident Management
-
Merge Request - www-gitlab-com!94570 (merged)
-
- Blog post
- Documentation
- Press Release
Tasks
Opening tasks
-
Add correct labels for ~devops::
~group::
~section:
-
Add a :recycle: Retrospective Thread
to make improvements to this template
Insights from looking at Grafana OnCall
- Grafana Labs’ acquired Amixr earlier this year; Amixr is now Grafana OnCall. Amixr’s mission was to build a product that is simple to use and allows you to start small and scale your on-call management over time
- Grafana OnCall is currently only available in cloud and is in Beta for free/paid. At this time it's unclear if Grafana OnCall will be available for on-premise or OSS.
- When a user creates an integration, the integration is tied to a specific alert route, Slack channel, and the escalation policy is built on the integration page.
- On-call schedules and scheduled overrides are created from calendar apps, i.e. Google Calendar or Microsoft Outlook, and then are brought into Grafana OnCall.
- Post-mortems (incident reviews) are automatically linked to incidents when relevant.
Share a summary of these findings in the following Slack channels:
-
#s_monitor stage -
#ops-section -
#product -
#analyst_relations -
#infrastructure-lounge -
#ceo
Feature enhancements
-
Create follow up issues and ping relevant product managers -
Attach issues as related to this one
Closing tasks
-
Update this template with any improvements suggested in the Retrospective Thread -
Close this issue
Edited by Alana Bellucci