Archived

This repository has been archived on 2024-04-10. You can view files and clone it, but you cannot make any changes to it's state, such as pushing and creating new issues, pull requests or comments.

Bhargavi Hanumant Alandikar 3543960689 Elektron Logging library (#16 )

switch to logrus for logging.

replaced old logging library with a wrapper around logrus.
We now just need to use the exported Log(...) and Logf(...) from the logging/
package that wraps around a set of loggers constituting a chain (following COR).
Loggers are configured using a YAML file that specifies the following.
1. enabled/disabled
2. whether the message should be logged on console.
3. filename extension.
4. minimum log level.

Retrofitted source code to now use the updated logging library.
Updated the documentation with information regarding the specification
of the log config file.

Currently, the log format in the config file is not adhered to. This is going to be
addressed in a future commit.

2019-12-09 20:15:33 -05:00

496 B

Raw Permalink Blame History

Scheduled Trace

For every task that is scheduled, the task ID and the hostname of the node on which it was launched is logged.

The scheduled trace logs are written to a file named <logFilePrefix>_<timestamp>_schedTrace.log, where

logFilePrefix is the prefix provided using the -logPrefix option.
timestamp corresponds to the time when Elektron was run.

The format of the data logged is as shown below.

[<loglevel>]: <yyyy-mm-dd> <hh:mm:ss> <hostname>=<task ID>

496 B Raw Permalink Blame History

Scheduled Trace

496 B

Raw Permalink Blame History