Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remediation Guide for GCP PostgreSQL Log Planner Stats Plugin #681

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions en/google/sql/postgresql-log-planner-stats.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
[![CloudSploit](https://cloudsploit.com/img/logo-new-big-text-100.png "CloudSploit")](https://cloudsploit.com)

# GOOGLE / SQL / PostgreSQL Log Planner Stats Disabled

## Quick Info

| | |
|-|-|
| **Plugin Title** | PostgreSQL Log Planner Stats Disabled |
| **Cloud** | GOOGLE |
| **Category** | SQL |
| **Description** | Ensures SQL instances for PostgreSQL type have log_planner_stats flag set to "off". |
| **More Info** | Logging planner performance statistics can lead to an increased amount of logs and can impact performance. It is recommended that the "log_planner_stats" flag is set to off to avoid performance issues caused by excessive logging. |
| **GOOGLE Link** | https://cloud.google.com/sql/docs/postgres/flags |
| **Recommended Action** | Ensure that log_planner_stats flag is disabled for all PostgreSQL instances. |

## Detailed Remediation Steps
1. Log into the Google Cloud Platform Console.
2. Scroll down the left navigation panel and click on "SQL". </br> <img src="/resources/google/sql/postgresql-log-planner-stats/step2.png">
3. On the "SQL" page, click on the three dots next to the name of the PostgreSQL Instance which needs to be verified whether it has the log_planner_stats flag enabled or not and click on "Edit".</br> <img src="/resources/google/sql/postgresql-log-planner-stats/step3.png"/>
4. On the "Edit" instance page, scroll down and click on the arrow next to the "Flags" section and check if the log_planner_stats flag is set to "on". If the value is not set, the PostgreSQL instance has the log_planner_stats flag disabled. </br> <img src="/resources/google/sql/postgresql-log-planner-stats/step4.png"/>
5. Repeat steps number 3-4 to check other PostgreSQL Instances in the project.</br>
6. Navigate to "SQL" and click on it. Click on the three dots next to the name of the PostgreSQL Instance which has log_planner_stats flag enabled and click "Edit".</br> <img src="/resources/google/sql/postgresql-log-planner-stats/step3.png"/>
7. On the Edit Instance page, scroll down to the Flags section, expand it and set the value for log_planner_stats flag to "off" or click on the trash icon to remove it altogether. Then click "Save".</br> <img src="/resources/google/sql/postgresql-log-planner-stats/step7.png"/>
8. Repeat steps number 7-8 to disable log_planner_stats flag for all other PostgreSQL Instances in the project.</br>
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.