Red Hat Bugzilla – Bug 1559399
Alert count is not incremented for utilization alerts
Last modified: 2018-09-04 03:02:57 EDT
Description of problem: Currently, all utilization related alerts are raised and handled in the server node itself. When threshold breach cross 75% and above the alert is raised from grafana and the alert is handled and displayed in UI, but alert count for is not incremented. Problem is cluster node alert count needs cluster_id to increment the alert count for particular cluster but monitoring-integration is not passing any cluster_id so unable to increment the count. Version-Release number of selected component (if applicable): How reproducible: Increase the utilization of volume or brick or CPU or memory or swap to 75% or above, after few seconds alerts, will be raised and displayed in UI but the alert count is not incremented. Steps to Reproduce: 1. 2. 3. Actual results: The alert count does not match with Number of alerts which is displayed in UI Expected results: The alert count should match with Number of alerts which is displayed in UI Additional info:
Cluster level notification counter is incremented by brick utilization alerts but is not incremented by memory and cpu related alerts. --> ASSIGNED Tested with: tendrl-ansible-1.5.4-7.el7rhgs.noarch tendrl-api-1.5.4-4.el7rhgs.noarch tendrl-api-httpd-1.5.4-4.el7rhgs.noarch tendrl-commons-1.5.4-9.el7rhgs.noarch tendrl-grafana-plugins-1.5.4-14.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.5.4-14.el7rhgs.noarch tendrl-node-agent-1.5.4-16.el7rhgs.noarch tendrl-notifier-1.5.4-6.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.5.4-6.el7rhgs.noarch
Created attachment 1443120 [details] Cluster page
filip CPU, memory, and swap alerts are node related alerts not cluster related alert. Only for cluster-related alerts cluster alert count will be increased. There is big discussion happened for this. https://github.com/Tendrl/documentation/wiki/List-of-Alerts-and-Notifications-in-Tendrl
Ok, based on https://github.com/Tendrl/ui/issues/666, https://github.com/Tendrl/gluster-integration/issues/449 and https://github.com/Tendrl/commons/issues/765 I VERIFY it.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2616