 |
 |
Fabrice, Let's create an epic for the monitoring tool, and put this info there as a comment. It will be easier to find in the future. Thanks! (and thank you to Booker!) Jacek On 01/23/2015 01:14 PM, Fabrice Jammes wrote: > Hi Booker, > > Thanks for all this interesting artilce, I also had a look at ELK stack > that you introduced me a few days ago. > > Using these modular components seems the good way of designing > a dedicated, flexible and powerful monitoring tool for the Qserv database. > > I cc Qserv mailing list. > > Thanks again, > > Fabrice > > On 01/23/2015 10:14 AM, Booker Bense wrote: >> >> Here's a good walk through of the kind of monitoring people are >> currently using for application level stuff. >> >> http://www.infoq.com/articles/graphite-intro?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global >> >> >> Graphite is a very common part of the tool chains people >> are setting up. A lot of the work in monitoring is moving >> away from a monlithic setup like nagios or ganglia into >> a flow of information in which you can swap components in/out >> as needed. >> >> - Booker C. Bense > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the QSERV-L list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1