Yes, this is my thought. The scope of the Sensu work is: "Is this thing working?" (with the reference being up/down) But the scope of the Grafana and friends is, "How hard is this working?" (but no alerting)
They are certainly complementary.... However, Sensu can throw data at a Grafana stack (aiui).. but I fear that is too much to achieve this cycle. -- Kind Regards, Dave Walker On 23 July 2016 at 00:11, Fox, Kevin M <kevin....@pnnl.gov> wrote: > I think those are two different, complementary things. > > One's metrics and the other is monitoring. You probably want both at the > same time. > > Thanks, > Kevin > ________________________________________ > From: Steven Dake (stdake) [std...@cisco.com] > Sent: Friday, July 22, 2016 3:52 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [kolla] Monitoring tooling > > Thanks for pointing that out. Brain out to lunch today it appears :( > > I think choices are a good thing even though they increase our > implementation footprint. Anyone opposed to implementing both with > something in globals.yml like > monitoring: grafana or > monitoring: sensu > > Comments questions or concerns welcome. > > Regards > -steve > > On 7/22/16, 3:42 PM, "Stephen Hindle" <shin...@llnw.com> wrote: > > >Don't forget mewalds implementation as well - we now have 2 monitoring > >options for kolla :-) > > > >On Fri, Jul 22, 2016 at 3:15 PM, Steven Dake (stdake) <std...@cisco.com> > >wrote: > >> Hi folks, > >> > >> At the midcycle we decided to push off implementing Monitoring until > >>post > >> Newton. The rationale for this decision was that the core review team > >>has > >> enough on their plates and nobody was super keen to implement any > >>monitoring > >> solution given our other priorities. > >> > >> Like all good things, communities produce new folks that want to do new > >> things, and Sensu was proposed as Kolla's monitoring solution (atleast > >>the > >> first one). A developer that has done some good work has shown up to > >>do the > >> job as well :) I have heard good things about Sensu, minus the fact > >>that it > >> is implemented in Ruby and I fear it may end up causing our gate a lot > >>of > >> hassle. > >> > >> https://review.openstack.org/#/c/341861/ > >> > >> > >> Anyway I think we can work through the gate problem. > >> > >> Does anyone have any better suggestion? I'd like to unblock Dave's work > >> which is blocked on a 2 pending a complete discussion of our monitoring > >> solution. Note we may end up implementing more than one down the road > >> Sensu is just where the original interest was. > >> > >> Please provide feedback, even if you don't have a preference, whether > >>your a > >> core reviewer or not. > >> > >> My take is we can merge this work in non-prioirty order, and if it > >>makes the > >> end of the cycle fantastic if not, we can release it in Ocatta. > >> > >> Regards > >> -steve > >> > >> > >> > >>_________________________________________________________________________ > >>_ > >> OpenStack Development Mailing List (not for usage questions) > >> Unsubscribe: > >>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > > > > > > > >-- > >Stephen Hindle - Senior Systems Engineer > >480.807.8189 480.807.8189 > >www.limelight.com Delivering Faster Better > > > >Join the conversation > > > >at Limelight Connect > > > >-- > >The information in this message may be confidential. It is intended > >solely > >for > >the addressee(s). If you are not the intended recipient, any disclosure, > >copying or distribution of the message, or any action or omission taken > >by > >you > >in reliance on it, is prohibited and may be unlawful. Please immediately > >contact the sender if you have received this message in error. > > > > > >__________________________________________________________________________ > >OpenStack Development Mailing List (not for usage questions) > >Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev