From c42f297522702a90319426f1a2a61cac9ac959bb Mon Sep 17 00:00:00 2001 From: ERIMROB Date: Mon, 8 Jun 2020 16:46:33 +0100 Subject: [PMSH] Re-alligning docs with the current state of pmsh logs Signed-off-by: ERIMROB Change-Id: I9f3aa6d70bd925ec54a462beb80665f8b3de21a3 Issue-ID: DCAEGEN2-2155 --- .../services/pm-subscription-handler/logging.rst | 23 ++++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-) diff --git a/docs/sections/services/pm-subscription-handler/logging.rst b/docs/sections/services/pm-subscription-handler/logging.rst index 59518d91..bd21384b 100644 --- a/docs/sections/services/pm-subscription-handler/logging.rst +++ b/docs/sections/services/pm-subscription-handler/logging.rst @@ -3,14 +3,29 @@ .. _Logging: -The PMSH logs will roll when the log file reaches 10Mb and a single backup will be kept. The logging level is not -configurable. +The PMSH logs will be rotated when the log file reaches 10Mb and a single backup will be kept, +with a maximum of 10 back ups. Logging ======= -The PMSH application writes logs on the debug level to the following file: +The PMSH application writes logs at INFO level to STDOUT, and also to the following file: .. code-block:: bash - /var/log/ONAP/dcaegen2/services/pmsh/debug.log + /var/log/ONAP/dcaegen2/services/pmsh/application.log + +To configure PMSH log level, the configuration yaml needs to be altered: + +.. code-block:: bash + + nano /opt/app/pmsh/log_config.yaml + +onap_logger level should be changed from INFO to DEBUG in order to enable debug logs to be +captured. This will affect both STDOUT logs and the logs written to application.log file + +.. code-block:: yaml + + loggers: + onap_logger: + level: INFO \ No newline at end of file -- cgit 1.2.3-korg