[tripleo][ptl]What is the future of availability monitoring in TripleO?
I've noticed that the availability monitoring integration in TripleO using Sensu is marked for deprecation post Rocky, but I do not see any blueprints detailing a replacement plan like there is for fluentd to rsyslog for the logging integration. Where can I find information on what the roadmap is? Is this a feature that will be dropped and left to operators to implement?
On 25.01.2019 22:34, David M Noriega wrote:
I've noticed that the availability monitoring integration in TripleO using Sensu is marked for deprecation post Rocky, but I do not see any blueprints detailing a replacement plan like there is for fluentd to rsyslog for the logging integration. Where can I find information on what the roadmap is? Is this a feature that will be dropped and left to operators to implement?
I know there is a spec [0], but it seems it needs some refreshing, like moving the target release. [0] https://review.openstack.org/#/c/523493/ -- Best regards, Bogdan Dobrelya, Irc #bogdando
On Fri, Jan 25, 2019 at 01:34:40PM -0800, David M Noriega wrote:
I've noticed that the availability monitoring integration in TripleO using Sensu is marked for deprecation post Rocky, but I do not see any blueprints detailing a replacement plan like there is for fluentd to rsyslog for the logging integration. Where can I find information on what the roadmap is? Is this a feature that will be dropped and left to operators to implement?
David, Sensu is marked for deprecation, which means it won't get installed by default in the near future anymore. Sensu (and fluentd combined) have a long tail of dependent packages (~ 150, if I'm not mistaken). For the future, I would look at replacing it with a combination of collectd, Prometheus and Alertmanager. I'll submit a spec for discussion in some future. Matthias -- Matthias Runge <mrunge@matthias-runge.de>
participants (3)
-
Bogdan Dobrelya
-
David M Noriega
-
Matthias Runge