turbot/steampipe-mod-gcp-compliance

Control: Ensure that the 'log_lock_waits' database flag for Cloud SQL PostgreSQL instance is set to 'on'

Description

Enabling the log_lock_waits flag for a PostgreSQL instance creates a log for any session waits that take longer than the allotted deadlock_timeout time to acquire a lock.

Usage

Run the control in your terminal:

powerpipe control run gcp_compliance.control.sql_instance_postgresql_log_lock_waits_database_flag_on

Snapshot and share results via Turbot Pipes:

powerpipe login
powerpipe control run gcp_compliance.control.sql_instance_postgresql_log_lock_waits_database_flag_on --share

SQL

This control uses a named query:

select
self_link resource,
case
when database_version not like 'POSTGRES%' then 'skip'
when database_flags @> '[{"name":"log_lock_waits","value":"on"}]' then 'ok'
else 'alarm'
end as status,
case
when database_version not like 'POSTGRES%'
then title || ' not a PostgreSQL database.'
when database_flags is null or not (database_flags @> '[{"name":"log_lock_waits"}]')
then title || ' ''log_lock_waits'' database flag not set.'
when database_flags @> '[{"name":"log_lock_waits","value":"on"}]'
then title || ' ''log_lock_waits'' database flag set to ''on''.'
else title || ' ''log_lock_waits'' database flag set to ''off''.'
end as reason
, location as location, project as project
from
gcp_sql_database_instance;

Tags