Event logging for CREODIAS (CF-9)

[kautlenbachs]

From CF-REQ-PGAAS Requirements_for_new_processor.pdf chapter 2.6 Event logging

The processor shall be equipped with event and error logging. Preferably the logging system should allow changing the type of logged events (DEBUG, INFO, ERROR). [REQ-LOG-1] Logs should be generated in structured logging format. [REQ-LOG-2] Example message:

{ "time": "2010-01-01 12:34:56.0000", "level": "ERROR", "message": "hello, world", "elapsed": 10,
"unit": "s" }

Messages should be generated in the proposed format due to external systems receiving, parsing and indexing logs. If the supplied processor includes an error logging system then the documentation for this processor must include additional information regarding the details of the system. The documentation must include additional information: where log files are created, a description of the format of created logs, a description of typical logged messages, how to control the level of logged events, whether a log archiving mechanism is included, and whether a mechanism for limiting the space available for logging is included. [REQ-DOC-6]

• Create a secret argument that switches the log format output to match the requirement. Argument name: '--log_format'. It should be called with a value 'creodias'
• Create boost::log formatter accordingly (see branch creodias_log)
• Add argument to alus::log::Initialize to specify format with enum. Currently then DEFAULT, CREODIAS
• Also tune the SetLevel() based on format. CREODIAS requires 3 levels - INFO, DEBUG, ERROR

Requirement CF9

[kautlenbachs]

There is already work done in branch on bitbucket - https://bitbucket.org/cgi-ee-space/alus/branch/creodias_log