On Wed, Mar 05, 2014 at 04:13:08PM +0100, Daniel Pocock wrote: > On 05/03/14 14:38, Florian Ernst wrote: > > ITIYM http://www.rsyslog.com/using-mongodb-with-rsyslog-and-loganalyzer/ > > in particular? > > > > Not until now. Previously I followed > > http://www.rsyslog.com/doc/rsyslog_conf_modules.html/ommongodb.html > > (which now redirects to http://www.rsyslog.com/doc/ommongodb.html). > > > > I have now tried to implement the configuration mentioned there > > verbatim. This led to remote logs simply disappearing, i.e. not being > > logged on my syslog host. Thus I have reverted the change, for my > > current mongodb rsyslog configuration please see the other mail to > > Daniel.
Following up to that: the config given in the first link looks like it should actually do the trick. It reads as if the missing parsing should take place. But as that config broke my remote syslog, I didn't tinker with it any further. It might be that there's a separate problem in my remote logging configuration, but I don't really see myself exploring that posiibility further at the moment, given that I lack a safe testing environment. > Just out of interest, if you empty the database (or clear out the events > created before rsyslog 7.4 was installed) does LogAnalyzer work? No. And I really wouldn't expect it to be working, given the "flexible schema" nature of mongodb. > Also, I've just created a proper package of LogAnalyzer, it is in the > FTP queue - I'd appreciate any feedback you have about it or assistance > with maintaining it through our pkg-monitoring group. README.Debian has > some basic hints to get started with MongoDB, but if you could validate > or elaborate on it that would be very helpful. Tempting, but as I was merely toying with that, and in the light of a lack of spare time due to dayjob and family, I'm afraid there won't be much I'd manage to do. Cheers, Flo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
