From 383360e357bd02cd87997b1ce8e77181f373532d Mon Sep 17 00:00:00 2001 From: catch Date: Mon, 26 Apr 2021 09:17:21 +0100 Subject: [PATCH] Issue #2732113 by tameeshb, selwynpolit, rajeshwari10, ronchica, JacobSanford, rakesh.gectcr, dagmar, dhruveshdtripathi, gaurav.kapoor, arkiii, Dinesh18, ranjith_kumar_k_u, KapilV, mikeohara, leslieg, kiamlaluno, xjm, cilefen, valthebald, longwave, jhodgdon, ChrisDarke, abi_cima, yoroy, ijf8090, catch: Clarify in the dblog_help that the dblog module should not be used for forensic log --- core/modules/dblog/dblog.module | 2 ++ 1 file changed, 2 insertions(+) diff --git a/core/modules/dblog/dblog.module b/core/modules/dblog/dblog.module index 1bf50e64537..aa3f910f9f3 100644 --- a/core/modules/dblog/dblog.module +++ b/core/modules/dblog/dblog.module @@ -30,6 +30,8 @@ function dblog_help($route_name, RouteMatchInterface $route_match) { $output .= '
' . t('The Database Logging module allows you to view an event log on the Recent log messages page. The log is a chronological list of recorded events containing usage data, performance data, errors, warnings and operational information. Administrators should check the log on a regular basis to ensure their site is working properly.', [':dblog' => Url::fromRoute('dblog.overview')->toString()]) . '
'; $output .= '
' . t('Debugging site problems') . '
'; $output .= '
' . t('In case of errors or problems with the site, the Recent log messages page can be useful for debugging, since it shows the sequence of events. The log messages include usage information, warnings, and errors.', [':dblog' => Url::fromRoute('dblog.overview')->toString()]) . '
'; + $output .= '
' . t('This log is not persistent') . '
'; + $output .= '
' . t('The Database Logging module logs may be cleared by administrators and automated cron tasks, so they should not be used for forensic logging. For forensic purposes, use the Syslog module.', [':audit_trail_wiki' => 'https://en.wikipedia.org/wiki/Audit_trail']) . '
'; $output .= ''; return $output;