Login issues

Available in Classic and VPC

You might run into the following problems when using Cloud Log Analytics: Find out causes and possible solutions.

Delete Logs

I want to delete logs.

Cause

Logs stored in Cloud Log Analytics cannot be deleted arbitrarily.

Solution

As explained in the cause, logs cannot be deleted arbitrarily. The log retention period is up to 30 days, and data older than 30 days is deleted in chronological order. For more information, see Prerequisites for using Cloud Log Analytics.

Disable Log Collection

I am using Cloud DB for MySQL but do not want to use the log collection feature.

Cause

Cloud DB services collect and provide Error logs and Slow Query logs by integrating with Cloud Log Analytics. Because Cloud DB services require the use of Cloud Log Analytics, unsubscribing from Cloud Log Analytics or deleting logs is not allowed.

Solution

As explained in the cause, if you are using Cloud DB services, you cannot unintegrate with Cloud Log Analytics.

View filebeat Logs

After installing the collection agent, I want to check on the server if logs are being sent properly by viewing filebeat logs.

Cause

filebeat logs are configured not to generate log files.

Solution

If you want to keep log files, add the following settings to the filebeat.yml file and restart filebeat.

logging.level: debuglogging.to_files: truelogging.files: path: /var/log/filebeat name: filebeat keepfiles: 7 permissions: 0644