You will find in this directory, a log file for each Shinken Enterprise daemon :
and an aggregated one:
Note : there is a daily rotation of log files).
Those files are also in this directory and they are suffixed with a date like this : arbiterd.log.2015-09-02
You can setup the level inside your configuration file (shinken.cfg)
To launch Shinken Enterprise in debug mode :
service shinken -d [debug level] restart |
or (only one deamon)
service shinken-[daemon name] -d [debug level] restart |
In this one, you will find all events about your Shinken Enterprise Architecture, because the arbiter daemon is used to check and dispatch configuration to the others daemons ( but not the Synchronizer ).
In error case :
Very useful in complex architecture with spare daemons where you will see here high availability events.
In this one, you will find all events about data management, because the broker daemon is used to export and manage data ( from schedulers ), for example, making those logs files ( and rotation ).
In this log you will find log output abou connection errors with the others daemons when occurs:
In this one, you will find all events about checks plugins, because the poller daemon is used to launch checks and return results to the schedulers.
You will mainly find issues with the scheduler communication if occurs.
In this one, you will find all events about communication ( mail, RSS, ... ) , because the reactionner daemon is used to issue notifications and launch event_handlers.
You will mainly find issues with the scheduler communication if occurs.
In this one, you will find all events about passive checks, because the receiver daemon is used to receives passive check data and serves as a distributed passive command buffer that will be read by the arbiter daemon.
You will mainly find issues with the scheduler communication if occurs and if the receiver is in direct routing mode.
In this one, you will find all events about checks (dispatch, returns, ...), because the scheduler daemon is used to manage the dispatching of checks and actions to the poller and reactionner daemons respectively.
You will see all checks returns :
In this one, you will find all events about configuration, because the synchronizer daemon is used to manage the whole configuration. It uses modules to detect new hosts and host modifications.