Friday, 2019-05-10

*** sapd1_x has quit IRC00:24
*** ricolin has joined #openstack-self-healing00:43
*** dasp has joined #openstack-self-healing02:11
*** dasp has quit IRC04:08
*** dasp has joined #openstack-self-healing04:30
*** witek has joined #openstack-self-healing06:45
*** bogdando has joined #openstack-self-healing07:45
*** ricolin has quit IRC08:24
*** sapd1_x has joined #openstack-self-healing08:29
*** bogdando has quit IRC08:41
*** sapd1_x has quit IRC08:56
*** bogdando has joined #openstack-self-healing09:15
*** sapd1_x has joined #openstack-self-healing09:19
*** tojuvone has quit IRC09:46
*** tojuvone has joined #openstack-self-healing09:46
*** sapd1_x has quit IRC11:09
*** sapd1_x has joined #openstack-self-healing13:27
*** sapd1_x has quit IRC13:56
*** witek has quit IRC15:56
*** bogdando has quit IRC16:20
*** ekcs has joined #openstack-self-healing17:53
joadavisThe only (small) downside I've seen to alert based is that you split the logic - some bit goes in the monitoring to decide if it is an alarm, and some bit goes in the root cause or clustering tool to decide what to do about the alarm.  Its not really a problem, but you do need to be aware of both parts.20:55
aspiersjoadavis: that's a good point! can you ensure it's mentioned in the relevant spec(s)?20:58
joadavisI can take a look for watcher and vitrage - anywhere else?21:08
*** joadavis has quit IRC21:47
*** joadavis has joined #openstack-self-healing22:05

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!