-
Notifications
You must be signed in to change notification settings - Fork 900
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
Added usage events for new appliance filesystems #5551
Merged
Fryguy
merged 1 commit into
ManageIQ:master
from
carbonin:add_new_filesystems_to_usage_monitoring
Nov 23, 2015
Merged
Added usage events for new appliance filesystems #5551
Fryguy
merged 1 commit into
ManageIQ:master
from
carbonin:add_new_filesystems_to_usage_monitoring
Nov 23, 2015
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
👍 |
Checked commit carbonin@56faf25 with ruby 1.9.3, rubocop 0.34.2, and haml-lint 0.13.0 app/models/miq_server/environment_management.rb
|
Fryguy
added a commit
that referenced
this pull request
Nov 23, 2015
…onitoring Added usage events for new appliance filesystems
jrafanie
added a commit
to jrafanie/manageiq
that referenced
this pull request
Jan 8, 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1658670 Although removed in ManageIQ#5551 and related appliance PRs, it's quite possible that users could mount their own disk at this moint point and would want to monitor for this event. It's trivial processing to skip it if they don't have a disk mounted at this location. The description of the event needed to be changed to make it less ambiguous with the other "log" disk usage events.
jrafanie
added a commit
to jrafanie/manageiq
that referenced
this pull request
Jan 8, 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1658670 Although removed in ManageIQ#5551 and related appliance PRs, it's quite possible that users could mount their own disk at this moint point and would want to monitor for this event. It's trivial processing to skip it if they don't have a disk mounted at this location. The description of the event needed to be changed to include the full log path to make it less ambiguous with the other "log" disk usage events.
jrafanie
added a commit
to jrafanie/manageiq
that referenced
this pull request
Jan 8, 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1658670 Although removed in ManageIQ#5551 and related appliance PRs, it's quite possible that users could mount their own disk at this moint point and would want to monitor for this event. It's trivial processing to skip it if they don't have a disk mounted at this location. The description of the event needed to be changed to include the full log path to make it less ambiguous with the other "log" disk usage events.
jrafanie
added a commit
to jrafanie/manageiq
that referenced
this pull request
Jan 8, 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1658670 Although removed in ManageIQ#5551 and related appliance PRs, it's quite possible that users could mount their own disk at this moint point and would want to monitor for this event. It's trivial processing to skip it if they don't have a disk mounted at this location. The description of the event needed to be changed to include the full log path to make it less ambiguous with the other "log" disk usage events.
jrafanie
added a commit
to jrafanie/manageiq
that referenced
this pull request
Jan 8, 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1658670 Although removed in ManageIQ#5551 and related appliance PRs, it's quite possible that users could mount their own disk at this moint point and would want to monitor for this event. It's trivial processing to skip it if they don't have a disk mounted at this location. The description of the event needed to be changed to include the full log path to make it less ambiguous with the other "log" disk usage events.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We now monitor all partition or logical volume backed filesystems for high usage and raise events if we pass the configured threshold.
The entries "/var/www/miq" and "/var/www/miq/vmdb/log" were removed because they are not filesystem mount points on the appliance.
Additional filesystems were added here ManageIQ/manageiq-appliance-build#51
https://bugzilla.redhat.com/show_bug.cgi?id=1281563