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

Databases get full #396

Open
slifty opened this issue Apr 20, 2021 · 0 comments
Open

Databases get full #396

slifty opened this issue Apr 20, 2021 · 0 comments

Comments

@slifty
Copy link
Contributor

slifty commented Apr 20, 2021

After leaving the system on for a few months it has run quite smoothly BUT the scrape log database has gotten pretty big (around 9 GB!).

I want to check to see if we're over-logging, but beyond that I think we can probably rotate out historic scrape logs (database level logs, not logfile logs).

Short term I'm going to manually clear out the historic logs on prod and dev, but this issue is meant to capture the need to add a new worker that runs once a day to clear out certain logs before a certain (configurable) time.

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

No branches or pull requests

1 participant