Skip to main content

lacework-global-282

6.2.7 Set 'Log_min_error_statement' Database Flag for Cloud SQL PostgreSQL Instance to 'Error' or Stricter (Automated)​

Profile Applicability​

• Level 1

Description​

The log_min_error_statement flag defines the minimum message severity level to consider as an error statement. The instance logs messages for error statements with the SQL statement. Valid values include DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, INFO, NOTICE, WARNING, ERROR, LOG, FATAL, and PANIC.

Each severity level includes the subsequent levels. Set a value of ERROR or stricter.

Rationale​

Auditing helps in troubleshooting operational problems and also permits forensic analysis. If log_min_error_statement is not set to the correct value, messages may not be classified as error messages appropriately. Considering general log messages as error messages would make is difficult to find actual errors and considering only stricter severity levels as error messages may skip actual errors to log their SQL statements. The log_min_error_statement flag should be set to ERROR or stricter. This recommendation is applicable to PostgreSQL database instances.

Impact​

Turning on logging will increase the required storage over time. Mismanaged logs may cause your storage costs to increase. Setting custom flags via command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended you apply these flags changes during a period of low usage.

Audit​

From Console:

  1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting https://console.cloud.google.com/sql/instances.
  2. Select the instance to open its Instance Overview page
  3. Go to Configuration card
  4. Under Database flags, check the value of log_min_error_statement flag is configured as to ERROR or stricter.

From Command Line:

  1. Use the below command for every Cloud SQL PostgreSQL database instance to verify the value of log_min_error_statement is set to ERROR or stricter.
gcloud sql instances list --format=json | jq '.settings.databaseFlags[] | select(.name=="log_min_error_statement")|.value'

Remediation​

From Console:

  1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting: https://console.cloud.google.com/sql/instances.
  2. Select the PostgreSQL instance for which you want to enable the database flag.
  3. Click Edit.
  4. Scroll down to the Flags section.
  5. To set a flag that is new to the instance, click Add item, choose the flag log_min_error_statement from the drop-down menu and set appropriate value.
  6. Click Save to save your changes.
  7. Confirm your changes under Flags on the Overview page.

From Command Line:

  1. Configure the log_min_error_statement database flag for every Cloud SQL PosgreSQL database instance using the below command.
gcloud sql instances patch <instance_name> --database-flags log_min_error_statement=<DEBUG5|DEBUG4|DEBUG3|DEBUG2|DEBUG1|INFO|NOTICE|WARNING|ERROR>
note

This command overwrites all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included uses the default value. For flags that do not take a value, specify the flag name followed by an equals sign ("=").

References​

https://cloud.google.com/sql/docs/postgres/flags
https://www.postgresql.org/docs/9.6/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHEN

Additional Information​

danger

This patch modifies database flag values, which may require you to restart your instance. The list of supported flags is on this page, along with details of which flags require a restart: https://cloud.google.com/sql/docs/postgres/flags.

note

Some database flag settings can affect instance availability or stability and remove the instance from the Cloud SQL Service-Level Agreement (SLA). For information about these flags, see Operational Guidelines.

note

Configuring the preceding flag does not require restarting the Cloud SQL instance.

Last updated on