The RIFT protocol engine writes log messages to the file rift.log in the same directory as where the RIFT protocol engine was started.
Note: when the RIFT protocol engine starts, it does not erase the existing rift.log file, it just appends to it. If you log at level DEBUG (see below) the rift.log file can become extremely large and fill up your disk. It is recommended to configure log rotation (e.g. using Linux logrotate).
It is useful to monitor the log file as the RIFT protocol engine is running using the tail -f command:
(env) $ tail -f rift.log 2018-07-29 13:03:20,682:INFO:node.fsm:[2001] Start FSM, state=COMPUTE_BEST_OFFER 2018-07-29 13:03:20,682:INFO:node.fsm:[2001] FSM push event, event=COMPUTATION_DONE 2018-07-29 13:03:20,682:INFO:node:[2002] Create node 2018-07-29 13:03:20,682:INFO:node.if:[2002-if_2002_201] Create interface 2018-07-29 13:03:20,682:INFO:node.if.fsm:[2002-if_2002_201] Create FSM 2018-07-29 13:03:20,682:INFO:node.if:[2002-if_2002_202] Create interface 2018-07-29 13:03:20,682:INFO:node.if.fsm:[2002-if_2002_202] Create FSM 2018-07-29 13:03:20,683:INFO:node.fsm:[2002] Create FSM 2018-07-29 13:03:20,683:INFO:node.fsm:[2002] Start FSM, state=COMPUTE_BEST_OFFER 2018-07-29 13:03:20,683:INFO:node.fsm:[2002] FSM push event, event=COMPUTATION_DONE 2018-07-29 13:05:38,323:INFO:node:[1] Create node 2018-07-29 13:05:38,324:INFO:node.if:[1-if_1_101] Create interface 2018-07-29 13:05:38,324:INFO:node.if.fsm:[1-if_1_101] Create FSM 2018-07-29 13:05:38,324:INFO:node.if:[1-if_1_102] Create interface 2018-07-29 13:05:38,325:INFO:node.if.fsm:[1-if_1_102] Create FSM ...
By default, the RIFT protocol engine only writes log messages at severity INFO and higher to the log file. This eliminates log messages at severity DEBUG which are used to report very common non-interesting events such timer tick processing, receiving and sending periodic messages, etc.
The command-line option "-l LOG_LEVEL" or "--log-level LOG_LEVEL" logs messages at the specified LOG_LEVEL or higher. Valid values for LOG_LEVEL are debug, info, warning, error, or critical.
The RIFT messages are structured with the intent to make it easy to grep for specific logs messages of interest.
2018-07-29 13:03:20,683:INFO:node.fsm:[2002] FSM push event, event=COMPUTATION_DONE -----------------------:----:--------:------ -------------------------------------- | | | | | | | | | +--> Message | | | +--> Identifier | | +--> Subsystem | +--> Severity +--> Timestamp
The fields in each log message are:
| Field | Meaning |
|---|---|
| Timestamp | The date and time (in the local timezone) at which the log message was generated. |
| Severity | The severity of the log message: DEBUG, INFO, WARNING, ERROR, or CRITICAL. |
| Subsystem | A dot-separated path that identifies the subsystem that generated the log message (see table below for possible values) |
| Identifier | A unique identifier that identifies the object that generated the log message (see table below for the meaning within each subsystem) |
| Message | A human-readable message |
The subsystems are:
| Subsystem | Log messages | Object ID |
|---|---|---|
| node | General logs related to a RIFT node | System-ID of the node |
| node.if | General logs related to a RIFT interface | System-ID of the node + Name of the interface |
| node.fsm | Logs related to the ZTP FSM for a node | System-ID of the node |
| node.if.rx | Logs related to received RIFT messages | System-ID of the node + Name of the interface |
| node.if.tx | Logs related to sent RIFT messages | System-ID of the node + Name of the interface |
| node.fsm | Logs related to the LIE FSM for an interface | System-ID of the node + Name of the interface |