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

[dev.icinga.com #10476] Explain check_memorys and check_disks thresholds #3560

Closed
icinga-migration opened this issue Oct 28, 2015 · 2 comments
Labels
area/documentation End-user or developer help enhancement New feature or request
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10476

Created by jflach on 2015-10-28 14:22:55 +00:00

Assignee: jflach
Status: Assigned
Target Version: (none)
Last Update: 2015-11-26 07:52:38 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

They check against free ram/space.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-11-26 07:52:38 +00:00

  • Status changed from New to Assigned
  • Assigned to set to jflach

@icinga-migration icinga-migration added enhancement New feature or request area/documentation End-user or developer help labels Jan 17, 2017
@Crunsher Crunsher modified the milestones: 2.7.0, 2.8.0 Jun 19, 2017
@Crunsher
Copy link
Contributor

Nobody saw me doing that, right?

@Crunsher Crunsher reopened this Jun 19, 2017
@Crunsher Crunsher modified the milestones: 2.7.0, 2.8.0 Jun 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation End-user or developer help enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants