<div dir="auto">Hi,<div dir="auto"><br></div><div dir="auto">And Gluster version is 3.12.5.</div><div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Jeevan.</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 15, 2018, 7:40 PM Jeevan Patnaik <<a href="mailto:g1patnaik@gmail.com">g1patnaik@gmail.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Hi All,<div dir="auto"><br></div><div dir="auto">I have implemented a webhook and attached to glustereventsd to listen to events and to send alerts on critical events.</div><div dir="auto"><br></div><div dir="auto">So, I categorized events manually critical, informational and warning.</div><div dir="auto"><br></div><div dir="auto">We are interested in only events that can cause issue to end users like BRICK_DISCONNECTED (reducing redundancy of the volume), QUORUM_LOST (possible downtime of subvoume), QUOTA_CROSSES_SOFTLIMIT, AFR_SPLIT_BRAIN etc. and not included any other events that are resulted while some one does admin tasks like PEER_ATTACH.</div><div dir="auto"><br></div><div dir="auto">And I see atleast some events are local to the node like PEER_ATTACH and doesn't appear from other gluster node. </div><div dir="auto"><br></div><div dir="auto">My idea is to run glustereventsd service only on a gluster admin node, to avoid possible load on the storage serving nodes due to traffic caused by webhook events.</div><div dir="auto"><br></div><div dir="auto">So, my question is are there any events local to node, which will be missed in admin node but are fatal to end users, assuming that the admin node will always be running?</div></div>
</blockquote></div>