.. _transaction-log-levels:

Transaction Log Levels
----------------------

.. _21.1|VOSS-794|EKB-8517:
.. _21.1|VOSS-794|EKB-8602:
.. _21.1|VOSS-794|EKB-9184:

Automate users with access to the ``data/Settings`` model or ``view/DataSettings`` can manage 
global transaction logging levels. These logging messages display below a selected transaction on the 
**Transactions** page, and have no impact on the transaction or sub-transaction action or detail information. 

Log levels are *cumulative*, that is, more detailed levels include all details from less detailed levels. 

The table describes the transaction log levels and their severity values: 

========  ==========================================================  ========
Level     Description                                                 Severity 
========  ==========================================================  ========
Disabled  Disables all transaction log messages                       999
Error     Only displays error messages                                40
Warning   Also adds warning messages to above                         30
Info      Also adds informational messages to above                   20
Verbose   Also adds messages used for diagnostic purposes to above    15
Debug     Also adds advanced diagnostic messages - for future use     10
========  ==========================================================  ========

* Severity values are referenced (from value - to value) in transaction details
  when the log level is changed on this setting or changed by lower level
  administrators from the **System Settings** menu. See: :ref:`data-settings`.
* If a transaction fails, the Log block includes all entries with severity
  values larger than that of the default or selected level of logging.
* The log levels of data syncs can be set to override these global levels. 

  The transaction log level used for data sync and its immediate sub-transactions is by default
  set to Warning when it is not set.

  .. raw:: latex
  
     For details, refer to the Create a Custom Data Sync topic in the Core Feature Guide.
    
  .. raw:: html
  
     <p>For details, refer to <a href="create-data-sync.html">Create a Custom Data Sync</a></p>


Transaction log levels are configurable based on your needs, for example, set to ``Verbose`` 
to include greater details for immediate troubleshooting and customization work: 

1. Toggle the log level to ``Verbose``.
#. Reproduce the issue causing the problem.
#. Export the logs and forward them to VOSS support.
#. Toggle the log level back to ``Info``.

.. note::
  
   When setting transaction log level to ``Verbose`` or ``Debug``, notes and warnings are shown to 
   remind admins that the retention period of such logs is  due to their increased size, 
   which consequently reduces the date range of available logs for troubleshooting.