Strange logs every 15 minutes. "cloudsqlobservabilityadmin"

[mysza]

Hey,
from "2024-01-30" such things started appearing in my logs:

2024-01-30T20:06:15.284266Z 11007229 [Warning] [MY-010235] [Server] Following users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin 'mysql_native_password' to rewrite authentication information (if any) for them: 'cloudsqlobservabilityadmin'@'localhost'

and since then, it appears every ~15 minutes.
Do you know why? How to fix it?

[ms4446]

The log message you're encountering is tied to Cloud SQL's built-in observability features and is a standard part of its operation. Here’s a detailed explanation:

Internal Mechanisms: The cloudsqlobservabilityadmin user plays a vital role in Cloud SQL's internal systems, dedicated to monitoring and ensuring the health of your database. This user is automatically managed by Google Cloud and is tasked with collecting metrics, logs, and other essential data to enhance visibility into your database instance's performance.

Automated Process: Observing this log message every 15 minutes is likely the result of a routine, automated check. This process verifies the existence of the monitoring user and confirms that all components necessary for comprehensive observability are correctly in place.

How to Handle the Messages

Given that these messages are informational and not indicative of any issues, here are your options:

• Ignore Them: This is the simplest approach, as these warnings are harmless and do not impact your database's functionality or performance.

• Adjust Log Filtering: For a more streamlined log experience, you can filter out these specific warnings using your log management tool. The process for setting up filters varies, so we recommend consulting your tool's documentation for detailed instructions.

• Cloud SQL Feedback: Should the frequency or presentation of these messages become burdensome, we encourage you to provide feedback to Google Cloud. This can be done through the Google Cloud Platform support page, issue trackers, or directly within the Google Cloud Console.

Important Note: It's crucial never to manually delete the cloudsqlobservabilityadmin user. Removing this user can significantly disrupt Cloud SQL's monitoring capabilities, affecting your ability to maintain visibility into your database's health.

[mysza]

I didn't do anything, and the logs disappeared on their own, so there must have been something wrong on the GCP side.