You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Invalid logs lines should make a debug log ... not an info log !
2014-03-09 08:11:18,683 [1394349078] Info : [LogStoreMongoDB] This line is invalid: [1394349075] TIMEPERIOD TRANSITION: 24x7;-1;1
2014-03-09 08:11:18,717 [1394349078] Debug : [Livestatus Log Lines] Does not match
2014-03-09 08:11:18,717 [1394349078] Info : [LogStoreMongoDB] This line is invalid: [1394349075] TIMEPERIOD TRANSITION: none;-1;0
2014-03-09 08:11:18,752 [1394349078] Debug : [Livestatus Log Lines] Does not match
2014-03-09 08:11:18,752 [1394349078] Info : [LogStoreMongoDB] This line is invalid: [1394349075] TIMEPERIOD TRANSITION: workhours;-1;0
2014-03-09 08:11:18,787 [1394349078] Debug : [Livestatus Log Lines] Does not match
2014-03-09 08:11:18,787 [1394349078] Info : [LogStoreMongoDB] This line is invalid: [1394349075] TIMEPERIOD TRANSITION: us-holidays;-1;0
2014-03-09 08:11:18,822 [1394349078] Debug : [Livestatus Log Lines] Does not match
The text was updated successfully, but these errors were encountered:
In fact, logstore-mongo makes a log in brokerd.log each time you write a log line in shinken.log because this module cannot store this log in mongo ! Morevover, as far as I understand, it is the normal behaviour not to store this log ... In this case, I prefer having a debug log or, even better, no log at all ...
Invalid logs lines should make a debug log ... not an info log !
The text was updated successfully, but these errors were encountered: