Monitor 14.6 Planning Issue
Planning Boards
Goals for the milestone:
- Start work on Incident Timelines
- Test alerts in GitLab for two different internal teams
- Complete the UX Roadmap for bringing Incident Management maturity from
Viable
toComplete
Scope of Work for Engineering
Incident Escalations
The remaining work from %14.5 => https://gitlab.com/gitlab-org/monitor/monitor/-/issues/81#notification-on-manually-created-incidents
Incident Timelines
Priority | Issue | Notes | Assigned | In Dev/ Merged | Frontend | Backend |
---|---|---|---|---|---|---|
1 | Feature flag for incident timelines | Deliverable | @tristan.read |
|
|
|
1 | Incident timeline empty state | Deliverable |
|
|
|
|
1 | Create tables for Incident Timeline Events | Deliverable | @ck3g |
|
|
|
1 | Display Incident Timeline Events | Deliverable | @ck3g |
|
|
|
1 | Add timeline event from comment |
|
|
|
||
1 | Add timeline event manually | Deliverable |
|
|
|
|
1 | Edit timeline event |
|
|
|
||
1 | Delete timeline event | Deliverable |
|
|
|
|
1 | Notify users of timeline event activity |
|
|
|
Notification on Manually Created Incidents
Priority | Issue | Notes | Assigned | In Dev | Merged | Frontend | Backend |
---|---|---|---|---|---|---|---|
2 | Add a "Status" dropdown in the UI on the incident page, gitlab-org/gitlab#330283 (closed) | @tristan.read @splattael | S | S-M | |||
2 | Resolve status on manually created incidents when incident is closed, gitlab-org/gitlab#334713 (closed) | @ck3g |
Technical Debt
Priority | Issue | Notes | Assigned | In Dev | Merged | Frontend | Backend |
---|---|---|---|---|---|---|---|
3 | Remove feature flag usage_data_i_incident_management_oncall_notification_sent |
There are some feature flag dependencies for this issue that are scheduled for %14.5. | |||||
3 | Apply retention period for pending escalation tables | ||||||
3 | On GitLab.com, the Metrics::Dashboard::SyncDashboardsWorker sidekiq job has about a 13% failure rate |
||||||
3 | Fix DST issues with generating new shifts | ||||||
3 | Resolve button in error tracking isn't working | Searching for issue... | |||||
3 | Refactor collector service for better error handling | @splattael | backend only | S | |||
3 | ErrorTracking: Ensure presence of transaction and stracktrace in Sentry payload |
@splattael | backend only | S | |||
3 | ActiveRecord::StatementInvalid: PG::UntranslatableCharacter: ERROR: unsupported Unicode escape sequence | @splattael | backend only | S |
Scope of Work for UX
Issue | When it should be ready |
---|---|
UX Roadmap: Incident Management Viable -> Complete | 14.6 Deliverable |
Monitor team lightning decision jam | 14.6 |
Scope of Work for Product
Issue | When it should be ready |
---|---|
Create Error Tracking Instrumentation Issue | 14.6 Deliverable |
Create Opportunity Canvas for Error Tracking Issue | 14.6 Deliverable |
Refine the Incident Management's funnel for AARRR Performance Metrics | 14.6 Deliverable |
Speed Runs for Grafana OnCall |
14.6 Deliverable, |
Facilitate with Dogfooding Alerts, Synchronous test of PagerDuty alerts and Testing GitLab Alerts and Implementing Metrics in Sisense | 14.6 Dogfooding |
Edited by Alana Bellucci