diff --git a/core/modules/dblog/dblog.module b/core/modules/dblog/dblog.module
index ed92d6c..43985b2 100644
--- a/core/modules/dblog/dblog.module
+++ b/core/modules/dblog/dblog.module
@@ -28,6 +28,8 @@ function dblog_help($route_name, RouteMatchInterface $route_match) {
       $output .= '<dd>' . t('The Database Logging module allows you to view an event log on the <a href=":dblog">Recent log messages</a> 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' => \Drupal::url('dblog.overview')]) . '</dd>';
       $output .= '<dt>' . t('Debugging site problems') . '</dt>';
       $output .= '<dd>' . t('In case of errors or problems with the site, the <a href=":dblog">Recent log messages</a> page can be useful for debugging, since it shows the sequence of events. The log messages include usage information, warnings, and errors.', [':dblog' => \Drupal::url('dblog.overview')]) . '</dd>';
+      $output .= '<h3>' . t('This log is not persistent') . '</h3>';
+      $output .= '<p>' . t('Users with <em>administer site reports</em> permissions can clear all the logs, and cron can <a href =":logging_settings" title="Go to logging settings page.">regularly clear</a> old entries. For these reasons, the Database Logging module should not be used for forensic purposes. Instead, it is recommended to use the Syslog module to build a forensic logging system.<a href=":audit_trail_wiki">Read more </a> about forensic logging.', [':logging_settings' => \Drupal::url('system.logging_settings'), ':audit_trail_wiki' => 'https://en.wikipedia.org/wiki/Audit_trail']) . '</p>';
       $output .= '</dl>';
       return $output;