Created attachment 1426994 [details] event page Description of problem: In tendrl we are considering alerts are also a event. So any alert raised then it displayes in alert page as well as event page, Becuase it is easy to see the alert history. But all alerts from monitoring-integration are only displayed in alert page not in event page. Version-Release number of selected component (if applicable): How reproducible: Keep fill some data in volume upto it reaches abouve 75%, after few minutes alert is raised and displayed UI. But in event page no information about that alert. Steps to Reproduce: 1.Keep fill some data in volume upto it reaches abouve 75% 2.wait for few minutes to grafana raise alert 3.Check event and alert page in UI. Actual results: Alerts information is displayes in alert page only. Expected results: Alert information should present alert page as well as event page Additional info:
I manually decreased threshold alert breach % to near 4% to raise the alert, So please don't confuse with that screen short.
(In reply to gowtham from comment #0) > In tendrl we are considering alerts are also a event. So any alert raised > then it displayes in alert page as well as event page, Becuase it is easy to > see the alert history. But all alerts from monitoring-integration are only > displayed in alert page not in event page. Could you point me to the up to date documentation when the meaning of alert and event is described?
It seems that alerts related to brick, cpu, memory and swap utilization are correctly shown in events.--> VERIFIED Tested with: tendrl-ansible-1.6.3-4.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-5.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-3.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-3.el7rhgs.noarch tendrl-node-agent-1.6.3-5.el7rhgs.noarch tendrl-notifier-1.6.3-3.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-2.el7rhgs.noarch
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