Description of problem: If cpu or memory of host is utilized beyond 80% then there is no alert generated. Version-Release number of selected component (if applicable): tendrl-ansible-1.6.3-10.el7rhgs.noarch tendrl-api-1.6.3-8.el7rhgs.noarch tendrl-api-httpd-1.6.3-8.el7rhgs.noarch tendrl-commons-1.6.3-13.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-15.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-15.el7rhgs.noarch tendrl-node-agent-1.6.3-11.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-14.el7rhgs.noarch How reproducible: 100% Steps to Reproduce: 1. Import cluster into WA. 2. Setup alerting (mail, snmp) 3. Log into some host and utilize its cpu and memory with `stress` command [1]. 4. Check for alerts in mail, snmp and UI Actual results: There are no alerts. Expected results: There should be alerts when utilization breach warning and critical utilization threshold. Additional info: [1] https://github.com/usmqe/usmqe-testdoc/blob/master/web/alerting/utilization_host.rst
Cpu utilization was seen working in version 3.4.1. In 3.4.2 it is broken. Memory utilization was seen working in 3.3.1. In 3.4.0 it was broken.
it is the regression part of http://bugzilla.redhat.com/show_bug.cgi?id=1590416 fix I did some small mistake.
PR under review: https://github.com/Tendrl/monitoring-integration/pull/581
With tendrl-monitoring-integration-1.6.3-16.el7rhgs.noarch cpu utilization alerts started to appear in UI, but memory utilization alerts still aren't working.
Hi Elena Bondarenko, There is different section in memory utilization, you cna see that in the image which you shared, actually alert will raise when used memory cross 75, looks like here used is below 20%. So alert wont raised.
i can see memory alerts with tendrl-monitoring-integration-1.6.3-16.el7rhgs.noarch in my machine
Created attachment 1512949 [details] Memory_utilization
This is new behavior comparing to 3.3.1, so another BZ has been opened by Filip: https://bugzilla.redhat.com/show_bug.cgi?id=1657680 Apart from that, everything works as expected.
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:3829