Feature monitoring

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Description

There are at least three kinds of monitoring that a developer cares about:

  1. Application performance monitoring (APM)
  2. System monitoring
  3. Business metrics/analytics

What I'm excited about is a 4th kind, which I'm calling "feature monitoring". Being able to know after shipping a merge request that we didn't blow up production. Or that error rates grew by 5% after enabling a feature flag on a subset of users.

Proposal

Here are three potential evolutions:

  1. Measure before/after deploying merge request and attribute any changes to the relevant merge request(s)
  2. Canary deploys where new features (via merge requests) can be shipped to a portion of a production fleet so they get real traffic, then monitor, report, and alert on differences in performance.
  3. Feature flags to ship one or more merge requests behind a flag that can be enabled for a portion of production users, then monitor, report, and alert on differences in performance.

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖