[Meta] Application Performance Monitoring
Performance monitoring is a core capability needed to deliver and maintain high quality software and experiences for your users. At GitLab, we have an opportunity to help our customers more easily and effectively track, manage, and optimize their software and hardware performance.
There are a few core needs that most organizations have:
- Detecting and preventing changes that would negatively impact performance and user experience
- Tracking long term performance trends, and progress towards goals
- Detection of issues in production, and potentially halting a deploy or rolling back
- Resources and insight to aid in debugging
- Visibility into infrastructure usage, efficiency, and costs
GitLab, with itsintegrated solution, is well positioned to help customers address these needs quickly and easily.
Detecting and preventing code performance degradations
Even for organizations with mature CI/CD capabilities in place, it is important to try to detect and prevent performance regressions from making it into production. With Continuous or Constant Deployment the time to recover and impact may not be high, but there is a cost to both users and the organization when a deploy fails or rollbacks are required.
To help customers avoid these situations, we can add enhance GitLab with a few new features:
- Track and compare Canary vs Stable (gitlab-ee#2594 (closed))
- Determining performance impact of a MR (gitlab-ee#3173): Automatically calculate the performance impact of a merge, without deploying to production first
Track long term performance gains/losses, progress towards goals
Building a fast and responsive application is not a one time effort, it is an on-going journey. Over time, new features are added, bugs are fixed, and typical user behavior may change. In short, it's a moving target and requires diligence and a constant eye.
Often, a company may not be happy with the performance of their application. Achieving their responsiveness goals will not occur in a single sprint. By providing a window into long term progress, developers as well as their managers can track continued progress towards objectives.
There are a few features which fall into this category:
- Display the long term performance trends of a single branch (gitlab-ee#3542)
- Internal Ops Dashboard: (gitlab-ee#3541)
- Improve Environment Page to show comprehensive status
Detection of issues in Production
A critical and foundational capability of a monitoring system is to be able to detect issues in production. We have a base set of features for this today, with the capability to monitor system and response metrics with Prometheus. We have the opportunity to extend this functionality and take it further, though.
- Track production page performance (gitlab-ee#3046 (closed))
- Production health checks (gitlab-ee#3554)
- Service mesh (gitlab-ee#3633)
- Alerting (gitlab-ee#3610, gitlab-ee#3555)