Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab Enterprise Edition
GitLab Enterprise Edition
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 3,612
    • Issues 3,612
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 227
    • Merge Requests 227
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab Enterprise EditionGitLab Enterprise Edition
  • Issues
  • #1677

Closed
Open
Opened Nov 07, 2016 by Mark Pundsack@markpundsack
  • Report abuse
  • New issue
Report abuse New issue

Feature monitoring

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

  • Feature flags: #779 (closed)
  • Related: gitlab-ce#23841 (closed)

Related issues

Assignee
Assign to
Epic
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
No due date
5
Labels
Accepting merge requests GitLab Premium Monitor UX direction
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-ee#1677