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.

Sign up for GitHub

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

Jump to bottom

Add option to purge spikekill backups #2664

Closed
jdcoats opened this issue May 1, 2019 · 4 comments
Closed

Add option to purge spikekill backups #2664

jdcoats opened this issue May 1, 2019 · 4 comments
Labels
bug Undesired behaviour resolved A fixed issue
Milestone
v1.2.4

Comments

@jdcoats
Copy link

jdcoats commented May 1, 2019

Cacti's spikekill feature now makes rrd backups but does not appear to have a schedule to remove these backups. I noticed today that it had 198GB of rrd backups from spikekill and I only currently have 11G of rra's.
@netniV
Copy link
Member

netniV commented May 2, 2019

If that is true, yes, there should be a recycle option to say how long to hold onto these things if it does not already exist.

@cigamit
Copy link
Member

cigamit commented May 5, 2019

@jdcoats are you using prophylactic spikekill scans?

@cigamit
Copy link
Member

cigamit commented May 5, 2019

Which directory BTW?

@jdcoats
Copy link
Author

jdcoats commented May 5, 2019 via email

cigamit added a commit that referenced this issue May 5, 2019
@cigamit
Resolving Issue #2664
77332b6 
- Cacti spikekill should have a rrd backup cleanup process
- Also resolved false positive leading to excessive backps
@cigamit cigamit added bug Undesired behaviour resolved A fixed issue labels May 8, 2019
@cigamit cigamit added this to the v1.2.4 milestone May 8, 2019
@netniV netniV changed the title Cacti spikekill should have a rrd backup cleanup process Add option to purge spikekill backups Jun 2, 2019
@cigamit cigamit closed this as completed Jun 8, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Undesired behaviour resolved A fixed issue
Projects
None yet
Milestone
v1.2.4
Development

No branches or pull requests
3 participants
@cigamit @netniV @jdcoats