Diagnostic log

Jörn Constabel
Jörn Constabel Customer
Fourth Anniversary 10 Comments Advocate 5 Up Votes
edited May 2022 in Platform
Dear all,

we are in progress to updated from 10.3 to 12.3
As written in the release notes, a new logging is available in BOARD 12. The diagnostic log. 
The only documentation I found is this: Other enhancements

Does anyone know how to configure the verbosity level of the logging? 

Regards,
Jörn

------------------------------
Jörn Constabel
Controller
Braunschweiger Flammenfilter GmbH
Germany
------------------------------

Accepted Answer

  • Björn Reuber
    Björn Reuber Employee, Community Captain
    500 Likes Fourth Anniversary 100 Comments 5 Answers
    edited May 2022 Answer ✓
    Hi Jörn

    you can find the requested information in our manual:
    Other enhancements (boardmanual.com)
    • New Diagnostic log - The Exception log has been replaced by a new, improved log: the Diagnostic log. This new log can be configured to adjust its verbosity level so that debugging will be a lot easier, given the amount of information it can include.
      These are the available verbosity levels:

      Each log line will always include the following information: timestamp, error level, action, TaskId, user, CorrelationId, additional details specific for each action.
      Log files are rolled at the end of each month or when they reach a file size of 50 Mb, whichever comes first. Log files older than two months are automatically deleted.

      • Off. The Diagnostic Log is turned off
      • Error (default). Returns the same amount of information included in the previous Exception log
      • Warning. Returns the same amount of information as the Error level plus exceptions with no impact on the user
      • Information. Returns the same amount of information as the Warning level plus additional information about non-error actions, such as Data model loading, Dataflow executions, Data Reader executions, Data Entry actions.
        At this level, the Diagnostic log file also includes lines written in all other Board log files. Entries generated by the same request have the same "TaskId" value, while entries belonging to the same Procedure have the same "CorrelationId" value.
      • Debug. The highest verbosity level: includes the same amount of information as the Information level plus information about the start and end of each task
    Please only change the BoardEngineParams.xml wihtin a downtime

    Regards
    Björn


    ------------------------------
    Björn Reuber
    Support Team Manager
    Board Deutschland GmbH
    Germany
    ------------------------------
    -------------------------------------------

Answers

  • Jörn Constabel
    Jörn Constabel Customer
    Fourth Anniversary 10 Comments Advocate 5 Up Votes
    edited May 2022
    Thanks Björn.

    The BoardEngineParams.xml -File was, what I was searching for.

    Regards,
    Jörn 


    ------------------------------
    Jörn Constabel
    Controller
    Braunschweiger Flammenfilter GmbH
    Germany
    ------------------------------
    -------------------------------------------