Navigation

Log Messages

mongosqld log messages have the form:

<timestamp> <severity> <component> [<context>] <message>

For example:

2017-08-17T13:34:48.910-0700 I NETWORK [initandlisten] waiting for connections at 127.0.0.1:3307

Log messages use iso8601 format for the timestamp, with a UTC offset set by the server on which mongosqld is running.

The following table lists the severity levels associated with each log message:

Level
Description
F
Fatal
E
Error
W
Warning
I
Informational, for Verbosity Level of 0
D
Debug, for All Verbosity Levels > 0

The default log verbosity level is 0, which includes all non-Debug messages. Increasing the verbosity level adds additional Debug messages to the logs. To set the verbosity level, see Configure Log Verbosity Levels.

Log messages include a component field, providing functional categorization of the messages:

Level
Description
CONTROL
Messages related to control activities, such as initialization.
NETWORK
Messages related to network activities, such as accepting connections.
ALGEBRIZER
Messages related to query plan generation.
OPTIMIZER
Messages related to query plan optimization.
EXECUTOR
Messages related to query execution.

To configure the log verbosity level:

To specify a verbosity level when starting mongosqld, use the -v option. Repeating v increases the verbosity level.

Example

The following invocation of mongosqld sets the log verbosity level to Developer.

mongosqld --schema schema.drdl --auth -vv

To learn more about the verbosity levels and how to use them, see --verbose.

New in version 2.5.

If you direct mongosqld to rotate log files with the --logRotate option, BI Connector adds a sequence number to ensure the uniqueness of each new log file name. Log files have the following format:

<filename>.<logSeqNumber>.<timeStamp>

For example:

mongosqld.log.000000.2018-04-20T15_10_23.898858222-07_00

For more information on log file rotation, see the --logRotate option.

Give Feedback