https://citconf.com/wiki/index.php?action=history&feed=atom&title=Monitoring_Metries_for_user_stalking 2026-04-25T00:56:20Z Revision history for this page on the wiki MediaWiki 1.35.11 https://citconf.com/wiki/index.php?title=Monitoring_Metries_for_user_stalking&diff=15520&oldid=prev 2013-10-04T07:32:22Z

<p>Created page with &quot;==Monitoring: Metries for user stalking == Mike started with description about what he currently uses in his environment at [http://www.mercateo.com Mercateo] 1. What Mike c...&quot;</p> <p><b>New page</b></p><div>==Monitoring: Metries for user stalking ==<br /> <br /> Mike started with description about what he currently uses in his environment at [http://www.mercateo.com Mercateo]<br /> <br /> 1. What Mike currently uses, and what the problem he faces<br /> <br /> * He&#039;s using Nagios as monitoring solution with snmp ( Jeff also confirmed that he use Nagios too.)<br /> * The check intervall ist about 5 minutes and the nagios has to do the check every 5 minutes for all services which causes the performance issue, and it&#039;s really bad if the numbers of services increases, which it always does.<br /> * As the check interval 5 minutes long, so that sometime if the machine reboots too fast then nagios didn&#039;t recognized it and there is no notifications!<br /> * What the current solution: he is using check_mk, collects all checks and ships to the nagios so that Nagios doesn&#039;t have to check everything, it helps Nagios to reduce some kind of load, but it not really improved so that he didn&#039;t migrate all to check_mk.<br /> * For sure that there is always another solutions for it but we want to keep it simple with one uniform solution using nagios.<br /> <br /> <br /> 2. Jeff added something that he currently implemented with logstash for his implementation he&#039;s using messages server (ZeroMQ) in combination with logstash but it&#039;s also does not guarantee if the message get lost as ZeroMQ does not hold them.<br /> @Carlo Bonamico: You added something for this topic but i did forget, can you help me to fill it out? <br /> <br /> <br /> 3. Squirrel informed what his team currently use<br /> <br /> logentries<br /> stackdrive<br /> <br /> 4. Discussion and findings<br /> <br /> * Jeff, Squirrel confirmed that they are using PagerDuty for EoD because its can directly alert to the right person who can solve the issue. <br /> * We should give a try with mCollective to aggregate Nagios Checks: Anyone has experience feels free to give a update/ feedback<br /> ** http://www.devco.net/archives/2013/01/01/scaling-nagios-nrpe-checks.php<br /> * There are also another solution with can help, but it requires to investigate and test.</div>

Anhngoc.phung