Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
infrastructure
infrastructure
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,752
    • Issues 1,752
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GitLab.com
  • GitLab Infrastructure Team
  • infrastructureinfrastructure
  • Issues
  • #6178

Closed
Open
Opened Feb 07, 2019 by Andreas Brandl@abrandl🔴Maintainer

Monitor bloat estimate

We need to measure bloat in the database to remove the need to manually measure it. Bloat can only be measured accurately on a one-off database and is a offline and rather expensive operation. Hence, we aim to estimate bloat with standard methods and push this information to prometheus.

Ideally, the bloat estimate should be available in prometheus for

  • individual indexes,
  • individual tables (heap + toast),
  • overall index bloat (can be derived) and
  • overall table bloat (can be derived).

It's ok if the bloat estimate only gets updated a few times a day, if a high frequency of measurements is not feasible.

Edited Feb 07, 2019 by Andreas Brandl
Assignee
Assign to
JF Team 2019 week 11
Milestone
JF Team 2019 week 11 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-com/gl-infra/infrastructure#6178