Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a status check for the size of database tables. #119

Open
cwebster61083 opened this issue Apr 20, 2022 · 3 comments
Open

Add a status check for the size of database tables. #119

cwebster61083 opened this issue Apr 20, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@cwebster61083
Copy link

Use Case

Have a check to alert if a table is above a certain threshold. For example, the certnames table. It would like this value to have a sane value but also be configurable.

Describe the Solution You Would Like

Alert me if key tables are larger than a set threshold and allow me to configure the threshold where necessary.

@cwebster61083 cwebster61083 added the enhancement New feature or request label Apr 20, 2022
@cwebster61083 cwebster61083 changed the title A a status check for the sized of database tables. Add a status check for the size of database tables. Apr 20, 2022
@MartyEwings
Copy link
Collaborator

MartyEwings commented Apr 25, 2022

The way we have the module is that the facts can not be altered, it's a good.idea but we wouldn't configure the threshold.

What list of tables and sizes do we think we want @cwebster61083

@bastelfreak
Copy link
Contributor

might be related? If not let me know and I create a new issue:
I spent a few hours debugging unresponsive nodes

  • they worked fine, but reports weren't stored in PuppetDB
  • pe-puppetdb on the compiles was fine, but couldn't write into postgresql
  • postgresql was overloaded because autovacuum was too conservative and didn't clean up enough
  • dead tuple count was rising -> db size grow -> inserting takes more and more IO
  • we were at a point where inserts where aborting because storage wasn't delivering enough IO for the (too) huge database

tl;dr a fact for dead tuples per table would be helpful I think? (and PE should have better defaults for autovacuum)

@MartyEwings
Copy link
Collaborator

@bastelfreak seems like a good addition

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants