v1.3.11 features

Author: sy-c

doc/README.md

@@ -176,6 +176,8 @@ The InfoLogger library allows to inject messages directly from programs, as show
  * More information on the API can be found in the headers /opt/o2-InfoLogger/include and the corresponding
  documentation generated by Doxygen.
  
+ * When using the C++ API, it is recommended to use the macros defined in InfoLoggerMacros.hxx to have the full context defined (severity, level, errno, source file/line) for each message in a compact way.
+ 
  * Some example calls are available in [the source code](/test/testInfoLogger.cxx)
  
  * There is the possibility to easily redirect FairLogger messages (see InfoLoggerFMQ.hxx) and process stdout/stderr to infologger (see InfoLogger.hxx setStandardRedirection())
@@ -184,8 +186,7 @@ The InfoLogger library allows to inject messages directly from programs, as show
  
  * The tags associated to a message consist of the following fields (which may be left undefined):
    * Severity: the kind of message, one of: Info (default), Error, Fatal, Warning, Debug
-   * Level: the relative visibility of the message and associated target audience to whom is addressed the message: from 1 (important, visible to all) to 99 (low-level debug message, for experts only).
-      For ALICE Run 2, the following ranges were used to categorize messages in DAQ/ECS: operations (1-5) support (6-10) developer (11-20) debug (21-99).
+   * Level: the relative visibility of the message and associated target audience to whom is addressed the message: from 1 (important, visible to all) to 99 (low-level debug message, for experts only). The following ranges are defined to categorize messages for a typical production environment: operations (1-5) support (6-10) developer (11-20) trace (21-99). Trace messages are usually not enabled in normal running conditions, and relate to debugging activities (also akin of the 'Debug' severity).
    * Timestamp: time at which message was injected (Unix time in seconds since 1.1.1970). Precision goes to the microsecond.
    * Hostname: the name of the machine where the message is issued. For concision, the domain name is excluded from this tag, only the base IP host name is kept.
    * Rolename: the role name associated to the entity running the process. The same host might run several different roles. Example role name: FLP-TPC-1, EPN-223.

doc/releaseNotes.md

@@ -39,3 +39,8 @@ This file describes the main feature changes for each InfoLogger released versio
 
 ## v1.3.10 - 04/08/2020
 - added automatic reconnection from clients to infoLoggerD
+
+## v1.3.11 - 07/08/2020
+- added helper definition for typical levels (operations, support, developer, trace)
+- added macros for compact writing of log commands with all fields set (severity, level, errno, source file/line). See InfoLoggerMacros.hxx.
+- sourceFile field: leading path is removed to keep only short filename.