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

Added usage events for new appliance filesystems #5551

Merged

Conversation

carbonin
Copy link
Member

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

@Fryguy
Copy link
Member

Fryguy commented Nov 20, 2015

👍

@miq-bot
Copy link
Member

miq-bot commented Nov 20, 2015

Checked commit carbonin@56faf25 with ruby 1.9.3, rubocop 0.34.2, and haml-lint 0.13.0
1 file checked, 1 offense detected

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
@Fryguy Fryguy merged commit 311bfd9 into ManageIQ:master Nov 23, 2015
@Fryguy Fryguy added this to the Sprint 33 Ending Dec 7, 2015 milestone Nov 23, 2015
@carbonin carbonin deleted the add_new_filesystems_to_usage_monitoring branch February 12, 2016 18:09
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants