Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Using MongoDB, can't see Notifications or Event Log

  1. #11

    Re: Using MongoDB, can't see Notifications or Event Log

    Hi,

    Same here, anything "report related" doesn't work. I won't post any logs because logs are the same as sebg's logs.
    Commenting all logger.debug in the logstore_mongo.py does the trick for the alert list but doesn't for the rest.

    Reverting to logsqlite will drop my previous logs and I'll lose the last two weeks that I need to make a report from.

    Well, just wanted to confirm this... any idea on a fix ?

  2. #12
    Administrator
    Join Date
    Dec 2011
    Posts
    278

    Re: Using MongoDB, can't see Notifications or Event Log

    The *fix* as it is, is simply for the Scheduler daemon to run at INFO level.

    Why? Simply because the log messages that get stored in the Livestatus logstore (broker daemon) are sent with an INFO level.

    There are a bunch of pull requests with a gazillion commits that have to do with logging that are pending which deal with all this. Unfortunately, those commits also break other stuff, and it needs a bit of update to get everything back together. Sorry. In the mean time, just run the scheduler at INFO level and all will be dandy.

    Cheers,

    xkilian

  3. #13
    Junior Member
    Join Date
    Nov 2012
    Posts
    22

    Re: Using MongoDB, can't see Notifications or Event Log

    my scheduler already logs at INFO level : the bug we're talking about is not "no logs in mongo" but "reporting in thruk throws a 500"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •