Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 35,780
    • Issues 35,780
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,222
    • Merge Requests 1,222
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #250694

Closed
Open
Opened Sep 17, 2020 by Markus Koller@toupeiraMaintainer

NSM Wiki: Track GET calls in the API as page "views" with Usage Ping

This is a follow-up to #218161 (closed), where we added Usage Ping tracking for wiki page views in the browser.

We also want to track when a wiki page is fetched over our REST API.

Proposal

We can either:

  1. Include API requests in the same counter.
  2. Add a separate counter for API requests.

Option 1 would be slightly easier as we wouldn't need to create separate counters/graphs etc., but would also mean we can't tell the difference between browser views and API requests. There's also the possibility that we have a lot of automated API requests, which would further confuse this data. So I think option 2 would be preferable.

Links

  • Internal: Knowledge Tracking Spreadsheet
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#250694