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

Wagtail logging / statistic and alarm regarding tar file sizes #11

Open
rollacting opened this issue Feb 26, 2021 · 0 comments
Open

Wagtail logging / statistic and alarm regarding tar file sizes #11

rollacting opened this issue Feb 26, 2021 · 0 comments
Assignees
Labels
Enhancement A new feature or an improvement Needs Discussion

Comments

@rollacting
Copy link
Contributor

rollacting commented Feb 26, 2021

Due to cms-user errors, huge images, broken renditions, duplicated content or whatever we should have a permanent look at the size of the tar files for all collections.

What would be an easy (and project independent) solution?
Most likely the logic / statistic tracking should be implemented via wagtail-to-ion, and the project logic handles how this information is used / who is able to see this information (e.g. sending alarm emails via custom, project related triggers / adding a statistic panel to the wagtail dashboard etc...

New settings like ARCHIVE_MAX_FILE_SIZE_INIT / ARCHIVE_MAX_FILE_SIZE_DELTA would be useful to specify thresholds depending on project requirements

@rollacting rollacting added the Enhancement A new feature or an improvement label Feb 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement A new feature or an improvement Needs Discussion
Projects
None yet
Development

No branches or pull requests

2 participants