> ## Documentation Index
> Fetch the complete documentation index at: https://cloudanix.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Sql log hostname flag remediation

### Triage and Remediation

<Tabs>
  <Tab title="Remediation">
    ### Remediation

    <AccordionGroup>
      <Accordion title="Using Console" defaultOpen="true">
        To remediate the PostgreSQL Log Hostname Flag Should Be On misconfiguration for GCP using GCP console, please follow the below steps:

        1. Open the Google Cloud Console and select the project containing the PostgreSQL instance.

        2. In the left navigation menu, select "SQL" to open the Cloud SQL instances page.

        3. Select the PostgreSQL instance for which you want to remediate the misconfiguration.

        4. Click on the "Edit" button at the top of the page to open the instance settings.

        5. Scroll down to the "Flags" section and click on "Add item".

        6. In the "Name" field, enter "log\_hostname" and in the "Value" field, enter "on".

        7. Click on the "Save" button to save the changes.

        8. Wait for the changes to be applied. This may take a few minutes.

        9. Once the changes are applied, verify that the PostgreSQL Log Hostname Flag is now turned on by checking the PostgreSQL logs.

        By following these steps, you should be able to remediate the PostgreSQL Log Hostname Flag Should Be On misconfiguration for GCP using GCP console.

        #
      </Accordion>

      <Accordion title="Using CLI">
        To remediate the PostgreSQL Log Hostname Flag Should Be On misconfiguration for GCP using GCP CLI, you can follow the below steps:

        Step 1: Open the Cloud Shell in your GCP console.

        Step 2: Run the below command to set the log\_hostname flag to on for the PostgreSQL instance:

        ```
        gcloud sql instances patch [INSTANCE_NAME] --database-flags log_hostname=on
        ```

        Note: Replace \[INSTANCE\_NAME] with the name of your PostgreSQL instance.

        Step 3: Verify the configuration change by running the below command:

        ```
        gcloud sql instances describe [INSTANCE_NAME] | grep log_hostname
        ```

        Note: Replace \[INSTANCE\_NAME] with the name of your PostgreSQL instance.

        This command should return the output "log\_hostname: on" which indicates that the flag has been set to on.

        Step 4: Repeat the above steps for all the PostgreSQL instances in your GCP project to ensure that the misconfiguration is remediated.

        By following the above steps, you can remediate the PostgreSQL Log Hostname Flag Should Be On misconfiguration for GCP using GCP CLI.
      </Accordion>

      <Accordion title="Using Python">
        To remediate the PostgreSQL Log Hostname Flag Should Be On misconfiguration in GCP using Python, you can follow these steps:

        1. Create a service account with the necessary permissions to access the PostgreSQL instance.

        2. Install the `google-cloud-sql` library using pip.

        3. Use the following Python code to update the PostgreSQL instance configuration to enable the `log_hostname` flag:

        ```python theme={null}
        from google.cloud import sql_v1beta4
        from google.oauth2 import service_account

        # Set the project ID, instance name, and configuration name
        project_id = 'your-project-id'
        instance_name = 'your-instance-name'
        config_name = 'your-config-name'

        # Set the service account credentials
        credentials = service_account.Credentials.from_service_account_file('path/to/credentials.json')

        # Create the SQL Admin API client
        client = sql_v1beta4.CloudSqlInstancesServiceClient(credentials=credentials)

        # Get the current configuration settings
        instance_path = f'projects/{project_id}/instances/{instance_name}'
        instance = client.get(instance_path)
        settings = instance.settings

        # Update the configuration settings to enable the log_hostname flag
        settings.database_flags['log_hostname'] = 'on'
        settings.settings_version += 1

        # Update the instance configuration
        config_path = f'projects/{project_id}/configs/{config_name}'
        update_mask = {'paths': ['database_flags']}
        operation = client.patch(instance_path, instance, update_mask=update_mask)

        # Wait for the operation to complete
        operation.result()
        ```

        Note: Replace `your-project-id`, `your-instance-name`, and `your-config-name` with your actual values. Also, replace `path/to/credentials.json` with the path to your service account credentials file.

        This code will update the PostgreSQL instance configuration to enable the `log_hostname` flag.
      </Accordion>

      <Accordion title="Using Terraform">
        ```hcl theme={null}
        resource "google_sql_database_instance" "POSTGRES_INSTANCE" {
          name             = "POSTGRES_INSTANCE_NAME"        # replace with your instance name
          database_version = "POSTGRES_14"                   # replace with your PostgreSQL version
          region           = "GCP_REGION"                    # replace with your GCP region

          settings {
            tier = "DB_TIER"                                 # e.g. "db-custom-2-7680"

            # Other settings …

            database_flags {
              name  = "log_hostname"
              value = "on"
            }
          }
        }
        ```

        Changing this flag does not replace the instance but will cause a restart of the Cloud SQL instance when applied.

        Verification: `terraform plan` should show an in-place update to `google_sql_database_instance.POSTGRES_INSTANCE` adding or changing `settings[0].database_flags[*].name = "log_hostname"` with `value = "on"`.
      </Accordion>
    </AccordionGroup>
  </Tab>
</Tabs>