Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,883
    • Issues 43,883
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,385
    • Merge requests 1,385
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #323713
Closed
Open
Created Mar 08, 2021 by Shinya Maeda@shinya.maeda💡Maintainer

Deprecate old DORA4 Analytics Project API

Problem

In a few months ago, we introduced an API to fetch DORA metrics at project-level. This API is functionally fine, however, it has a couple of problems:

  • It frequently times out due to the inefficient aggregation approach, which causes SLA issue.
  • Due to the inefficiency, we can't enable the group-level API feature flag.
  • The API path (/projects/:id/analytics/deployment_frequency) is inappropriate. It should be scoped by dora.
  • environment parameter should be optional as DORA metrics targets production only.
  • The API design is not extensible/manageable as we have to create new path per metric.
  • The cost to fix the current APIs is much more expensive than introducing new APIs, because we have to handle the breaking change carefully.

Proposal

After we've added new generic-and-performant APIs in #291746 (closed) and https://gitlab.com/gitlab-org/gitlab/-/issues/322404, we'll deprecate the old APIs. To do so, we have to change the API path in frontend at first (for project-level deployment frequency)

Edited Mar 08, 2021 by Shinya Maeda
Assignee
Assign to
Time tracking