-
Notifications
You must be signed in to change notification settings - Fork 13
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
Stopping volume - alerts #391
Comments
@ltrilety this is how it is implemented at the moment as based on state/status changes reported from |
This is an RFE, since Tendrl is a monitoring tool and does not understand if the Volume was stopped with good intentions or if it was stopped abruptly or whatever. Once Tendrl has capabilities like "Volume stop" from Tendrl API then we can address this request. |
If user stop a volume, such action generates a lot of alerts about bricks stop. That leads to state where the volume is stated as 'degraded' and even the cluster is declared as 'unhealthy' because of those stopped bricks.
We should differentiate this scenario from the one where bricks are stopping randomly. In this case stop of bricks is expected behaviour as the volume is stopped.
Tested version:
tendrl-ansible-1.6.1-2.el7rhgs.noarch
tendrl-commons-1.6.1-1.el7rhgs.noarch
tendrl-ui-1.6.1-1.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-api-1.6.1-1.el7rhgs.noarch
tendrl-api-httpd-1.6.1-1.el7rhgs.noarch
tendrl-monitoring-integration-1.6.1-1.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-notifier-1.6.0-1.el7rhgs.noarch
tendrl-node-agent-1.6.1-1.el7rhgs.noarch
tendrl-grafana-plugins-1.6.1-1.el7rhgs.noarch
The text was updated successfully, but these errors were encountered: