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

check-disk-usage.rb - Option to define minimal free space threshold #166

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

VeselaHouba
Copy link
Contributor

Pull Request Checklist

Is this in reference to an existing issue?
No

General

  • Update Changelog following the conventions laid out here

  • Update README with any necessary configuration snippets

  • Binstubs are created if needed

  • RuboCop passes

  • Existing tests pass

New Plugins

  • Tests

  • Add the plugin to the README

  • Does it have a complete header as outlined here

Purpose

Known Compatibility Issues

Copy link
Member

@majormoses majormoses left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank your for your contribution. I think the change makes sense to me although I would like to discuss the defaults further. Look forward to your response.

description: 'Trigger alarm only if free space on device is below '\
'this threshold (in GB)',
proc: proc(&:to_f),
default: 10_000
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like to better understand where the rationale for this default number came from. I'd imagine this default should be much lower value. 10,000 GB is maybe an appropriate value for a SAN/NAS but I would wager that a double digit number would be more appropriate. Most of my VMs at work have < 100 GB of local storage.

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

Successfully merging this pull request may close these issues.

None yet

2 participants