Evaluate current tiering of Monitor stage features
The purpose of this feature is to evaluate that the current feature-set for the Monitor stage is placed in the correct tier and ensure we are not missing opportunities that would have a positive impact towards IACV.
Current devopsmonitor features:
| Feature | Tier | Category | Proposed Change? |
|---|---|---|---|
| Application performance Monitoring | Core | metrics | |
| Application performance alerts | Ultimate | metrics | Core - necessary to complete the DevOps loop |
| GitLab Self-monitoring | Core | metrics | |
| Cloud native monitoring | Core | metrics | |
| Server Monitoring | Core | metrics | |
| Logs | Ultimate | metrics | Starter |
| Omnibus package supports log forwarding | Starter | logging | |
| Audit Logs | Premium | logging | |
| Tracing | Ultimate | tracing | Starter - would be purchased by manager to help team maintain SLOs |
| Kubernetes Cluster Monitoring | Ultimate | cluster_monitoring | Premium - Advanced Kubernetes management |
| Error Tracking | Core | error_tracking | |
| Incident Management | ? | incident_management | Features are split across tiers |
| Synthetic Monitoring | N/A | synthetic_monitoring | WILL BE: Ultimate |
| Status Page | N/A | status_page | WILL BE: Ultimate - Value Stream Management |
| Custom metrics | Ultimate | metrics | CE |
Tiers: core, starter, premium, ultimate
Categories: Metrics, Tracing, Logging, Incident Management, Cluster Monitoring, Error Tracking, Synthetic Monitoring, Status Page
Reasoning
Change X from A to B tier
Edited by Dov Hershkovitch