We have done few CI work, where we run continuously in an automated way building and running sanity checks against cs. As part of it ,we collect all logs( management server logs, api logs, test case log, test run logs etc).
After every automated build run, we upload these logs to nfs share automatically, we used elastic search on these logs collected to correlate failures with product logs, get information for failures across builds for a given failure etc. We used elastic search engine and python elastic search binding for indexing and querying. So, for "now" only limited case of getting data between two timestamps for a given failure etc were added, but i believe others can be added as well with more finetuning and other changes. Santhosh ________________________________________ From: Rohit Yadav [[email protected]] Sent: Wednesday, June 25, 2014 5:24 AM To: [email protected] Subject: Re: Anyone using ELK (ElasticSearch / LogStash / Kibana to analyze CS logs ? I've tried the ELK stack but I think it's not much helpful for debugging issues, though searching/tracking is faster for very long logs. Regards. On Wed, Jun 25, 2014 at 2:17 PM, Harm Boertien <[email protected] > wrote: > Cheers, > > Harm > > Harm Boertien > MCE @ Schuberg Philis B.V. > Boeing Avenue 271 > 1119 PD Schiphol-Rijk > > [email protected] > +31 6 14008293 > > > >
