Description of problem: When trying to track disk usage for vmdb/log this is not an option in the UI to choose as a driving event. Version-Release number of selected component (if applicable): 5.8.5 and 5.9.5 How reproducible: Always Steps to Reproduce: 1. Go to Control > Explorer > Alerts 2. Configuration > Add new alert 3. Based on = Server 4. What to evaluate = Expression (Custom) 5. Driving Event = ??? Actual results: Option for tracking vmdb/log is not available Expected results: Option to track vmdb/log should be available Additional info: This alert is listed in our documentation https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.5/html-single/monitoring_alerts_and_reporting/#to_create_an_alert --------------------------------- 6.10. Create an Operational Alert --------------------------------- * Navigate to Control → Explorer. * Click on the Alerts accordion, then click Configuration => Add a new Alert * In the Info area: Type in a description for the alert. Check Active when you feel that the alert is ready to be enabled. From Based On, select Server. Select the appropriate driving event. ***choose EVM Server High Log Disk Usage here*** In Notification Frequency, select how often you want to be notified if the event log threshold is reached. * After setting the parameters, select what you want the alert to do. * Click Add. More about this alert type below: ------------------------------ EVM Server High Log Disk Usage ------------------------------ The server’s log disk is 80% full. This check is run as part of a system schedule. Threshold configured in Advanced Settings. server: events: :disk_usage_gt_percent: 80
I took a look at this and we don't have an event for the log disk. See [1]. In upstream, we don't have an external disk for the /var/www/miq/vmdb/log directory, see [2]. In downstream, we have a separate disk for this /var/www/miq/vmdb/log directory but don't add a new event definition. I don't believe we ever did have an event for this so I'm not sure how the documentation has it. Either way, in a test environment, if you add a line to the vmdb/db/fixtures/miq_event_definitions.csv for this new event and restart, you should be able to try it out and see if it works as you want. If so, this can become a RFE to add this feature. In other words ... evm_server_system_disk_high_usage,Server High System Disk Usage,Default,evm_operations evm_server_boot_disk_high_usage,Server High /boot Disk Usage,Default,evm_operations evm_server_home_disk_high_usage,Server High /home Disk Usage,Default,evm_operations evm_server_var_disk_high_usage,Server High /var Disk Usage,Default,evm_operations Add the following line: evm_server_vmdb_log_disk_high_usage,Server High vmdb/log Disk Usage,Default,evm_operations evm_server_var_log_disk_high_usage,Server High /var/log Disk Usage,Default,evm_operations evm_server_var_log_audit_disk_high_usage,Server High /var/log/audit Disk Usage,Default,evm_operations evm_server_miq_tmp_disk_high_usage,Server High Temp Storage Disk Usage,Default,evm_operations evm_server_tmp_disk_high_usage,Server High /tmp Disk Usage,Default,evm_operations ... [1] https://github.com/ManageIQ/manageiq/blob/602b4347e65f9091ac4ea02997d4d5dd3a1f2e2a/db/fixtures/miq_event_definitions.csv#L18-L25 [2] https://github.com/ManageIQ/manageiq-appliance-build/blob/e280b2b0cf73e9508d257a8d43bba49d174dd528/kickstarts/partials/main/disk_layout.ks.erb#L10-L15
Upstream PR https://github.com/ManageIQ/manageiq/pull/18340, merged
With bug 1705139 and bug 1707871 both fixed, I was able to verify this BZ in CFME 5.11.0.4.20190514210444_0c91ee1. Steps of verification were the same as those of bug 1672698. This BZ has automated test coverage here: https://github.com/ManageIQ/integration_tests/blob/2ba0baca2a0ec7379f0e2ff3dadd5d3e171435bb/cfme/tests/control/test_bugs.py#L394-L452