This discussion is archived
1 Reply Latest reply: Jan 5, 2013 1:38 PM by PradeepKPathak RSS

Best practice on monitoring Endeca health / defining outage

Jim Song Newbie
Currently Being Moderated
(This is a double post from the Endeca Experience Management forum)

I am looking for best practice on how to define Endeca service outage and monitor the health of the system. I understand this depends on your user requirements and it may vary from customer to customer. Specifically what criteria do you use to notify your engineer there is a problem? We have our load balancers pinging dgraphs on an interval. However the ping operation is not sufficient in our use case. We are also experimenting running a "low cost" query to the dgraphs on an interval and using some query latency thresholds to determine outage. I want to hear from people on the field running large commercial web site about your best practice of monitoring/notifying health of the system.



  • Correct Answers - 10 points
  • Helpful Answers - 5 points