On 05/03/14 11:26, Michael Biebl wrote: > [dropping debian-devel] > > Am 05.03.2014 11:07, schrieb Daniel Pocock: >> On 05/03/14 09:09, Florian Ernst wrote: >>> Hello all, >>> >>> On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: >>>> The rsyslog mongodb output module and the PHP mongodb modules are now in >>>> wheezy-backports. This would appear to be sufficient to do something like: >>>> >>>> rsyslog => mongodb => loganalyzer >>>> >>>> Has anybody else tried that or does anybody have any comments on it (or >>>> recommended alternatives)? >>> That actually did work for a time, but something broke starting with >>> rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb >>> doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. >>> As I was merely experimenting with it I didn't follow up any further. >> Some of this looks like documentation bugs and/or problems with the >> default config rather than mongodb integration itself >> >> LogAnalyzer and rsyslog are from the same upstream too, so I would be >> surprised if they would not have them working together >> >> I had a look at the Git history for the ommongodb, does anything stand >> out here? >> >> https://github.com/rsyslog/rsyslog/commits/master/plugins/ommongodb >> >> You state the problem started with 7.4.0-1 - could you comment on the >> previous set of versions that you had working (both rsyslog and >> LogAnalyzer versions)? >> > If the README.Debian (which was based on [1]) is no longer correct, > please let me know. > > If you are using the 7.4.0 backport for wheezy, make sure to also use > the libjson-c 0.11 backport. > > > [1] > http://git.adiscon.com/?p=rsyslog.git;a=blob;f=plugins/ommongodb/README;hb=HEAD
Michael, thanks for the fast response on this In the bug report, it goes on to say that after correcting the first issue, "I can dump data to mongodb again, though the format doesn't match previous entries." and then the email to debian-devel suggests that LogAnalyzer can no longer read the data (even though it is there) It is this latter issue that I am curious about - is it a deliberate schema change? Is it just the libjson-c version (and can you add that to the control file)? Does it require some newer version of LogAnalyzer (and is anyone aware if upstream is working on that, if it is unreleased, etc)? I also queried it upstream: https://github.com/rsyslog/rsyslog/issues/46 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
