Ensure syslog messages are not lost due to size

FaibleNiveau 1Revue manuelleyugabytedb

Description

YugabyteDB log messages can exceed 1024 bytes, which is a typical size limit for traditional Syslog implementations. When syslog_split_messages is off, YugabyteDB server log messages are delivered to the Syslog service as is, and it is up to the Syslog service to cope with the potentially bulky messages.

Méthode de vérification

Méthode d'audit: Revue manuelle

Cette recommandation ne peut pas être vérifiée automatiquement. Une analyse la liste avec ces instructions lorsque vous passez --include-manual.

Run SHOW syslog_split_messages; in ysqlsh. Where syslog is a log destination it must be on (the default), so that messages longer than about 1024 bytes are split instead of truncated or lost; off is a finding.

Méthode de correction

Méthode de correction: Recommandation ou correctif d'infrastructure

Use the yb-tserver binary and its flags to configure the YB-TServer server. Add the following GFLAG to YB-TServer: ./bin/yb-tserver --ysql_pg_conf_csv="syslog_split_messages='on'"

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: yugabytedblogging
Référence: CIS YugabyteDB Benchmark v2.0.0 - 3.1.9 Ensure syslog messages are not lost due to size