Cloud Log Analytics overview

Prev Next

Available in Classic and VPC

Using the NAVER Cloud Platform’s Cloud Log Analytics service, you can collect, analyze, and store various logs created while using NAVER Cloud Platform services.

Cloud Log Analytics Features

Cloud Log Analytics includes the following features:

  • Real-time Log Collection: Real-time collection of all text-based logs generated across NAVER Cloud Platform's services, including and servers, with a dashboard for easy access.
  • Log Searching: Search all logs collected across multiple services using various search options, such as time, keyword, and Lucene Query searches.
  • Saving and Downloading Log Data: All data collected is distributed across two or more copies in logically separated repositories, and can be downloaded as Excel files or exported to Object Storage.
  • Log Management and Analysis Features (Coming Soon): Real-time keyword notifications, custom dashboards, RESTful APIs, and integrated log collection across NAVER Cloud Platform services.

Cloud Log Analytics user guide

Cloud Log Analytics is available in the Korea, U.S., Singapore, Japan, and Germany Regions. Service details for each Region are identical. For information on how to use Cloud Log Analytics, see the sections below.

Cloud Log Analytics related resources

Beyond the user guide, these resources provide additional context and support for Cloud Log Analytics. Whether you're considering Cloud Log Analytics or need in-depth information for development, marketing, and other purposes, these resources can help:

Cloud Log Analytics FAQs

See the FAQs before reading the user guide for quick answers to frequently answered questions. If your questions are not resolved by the FAQs, see the user guides for the information you want.

Q. What kinds of data can I collect?
A. Cloud Log Analytics can collect any kind of log data file that is generated in text format. Templates are provided for frequently-used logs, but logs without templates can also be collected using the custom log feature. For more information on available log templates, see Cloud Log Analytics prerequisites.

Q. How is stored data managed?

  • Data is distributed and stored as 2 or more copies across logically separate independent repositories.
  • Data is deleted under the following circumstances:
    • Data older than the retention period is deleted daily, starting with the oldest records.
    • If data usage exceeds storage capacity, up to 30% of stored data is sequentially deleted, starting with the oldest records.
    • All data is deleted when you cancel your Cloud Log Analytics subscription.

Q. Can I download all of my saved logs?
A. You can download all of your data through Export to Object Storage. For more information, see Exporting to Object Storage or Export Log.

Q. I can't cancel my subscription.
A. If you use the log management features of Cloud Log Analytics in PaaS services on NAVER Cloud Platform such as Cloud DB for MySQL, Cloud DB for MSSQL, and Cloud DB for MongoDB, you cannot cancel your Cloud Log Analytics subscription. You must first terminate or return the applicable services before you can cancel your Cloud Log Analytics subscription.

Q. Can I try it out for free?
A. The Standard plan for Cloud Log Analytics provides log collection and a monthly average of 1 GB of free log storage. For more information, see Pricing Information.

Q. Can Auto Scaling server logs be automatically sent to Cloud Log Analytics?
A. When you create an Auto Scaling group using an image of a server that is set up for collection in Cloud Log Analytics, logs from the server created by Auto Scaling are sent to Cloud Log Analytics without any additional requirements. For more information, see Collecting Logs.

Q. A "no permission of object storage" error occurs during automatic exports.
A. Check the following items in order:

  1. Check for Bucket deletion
    Make sure the Object Storage Bucket set as the target for automatic export has not been deleted.
  2. Check API Authentication Keys
    See API Authentication Keys to make sure your API authentication key is properly registered. Without an authentication key, access to Object Storage is restricted.
  3. Check Bucket Access Permissions
    If the access controls have been configured for the Object Storage Bucket, or if permissions have been removed, automatic export may fail. Check if the proper read/write permissions have been granted.

If the problem persists even after checking the above items, contact Customer Support.

Q. During automatic export, a "no access key" issue occurs.
A. The issue occurs when there is no Access Key to access Object Storage. The automatic export feature is internally performed using your API authentication key. Check the following items:

  • Check if your account was deleted
    If the account for which automatic export has been configured is deleted or disabled, it can cause errors.
  • Check API Authentication Key validity
    Check if a valid API authentication key is registered in the account for which automatic export is configured. See API Authentication Keys to learn how to verify your API authentication key.
  • Check your automatic export settings account
    Disable the automatic export feature in the main account or a different sub account, then reconfigure the automatic export using an account with your API authentication key to fix log exports.

Q. I heard the automatic export feature was improved. What are the changes?
A. The enhanced automatic export feature has the following differences compared to previous implementations.

  • Changes in how log files are stored
    Previously, all logs were stored as a single file. Now, they are stored separately by date, log type, or time.
    → This allows for more granular logs for easier management and analysis.
  • Changes to storage directories
    The directory structure for Object Storage has been changed. When you configuring automatic export, check the access permissions and settings for the new directory.

The automatic export feature has been improved for more efficient log management and analysis. Configure automatic exports accordingly.

Q. I’ve completed Agent installation and the "Finish Installation" message was shown, but logs aren’t exporting.
A. If logs are not exported after a properly completed installation, check the following:

  • Check your firewall or ACL settings
    Log exports may be blocked due to firewall or Access Control List (ACL) settings in the installed device.
    Check if the port to the log server is blocked.
  • Check if Filebeat is running
    To check if the Agent is running normally, enter the command below.
ps -ef | grep filebeat

If the process is not running, restart it manually.

  • Check the configuration file
    To check if the configuration file for errors, enter the following command.
cat /etc/filebeat/filebeat.yml

Make sure that the log collection path, output target, and format are configured correctly.

Q. I get a "missing configuration file" error when trying to install the Agent in Windows Server 2019. How can I resolve this?
A. This error may occur if the Filebeat or Winlogbeat configuration files have not been properly downloaded.

  • First, check if the following configuration files exist.
  • Configuration file directory
C:\Program Files\cla_windows\winlogbeat-<version>-windows-x86_64\winlogbeat.yml

The configuration file is automatically downloaded upon installation. If the file download fails, logs will not export properly.

  • Solutions
  1. Stop the service and delete the existing installation file.
    • Run the following commands in PowerShell:
Stop-Service filebeat
Stop-Service winlogbeat
cd "C:\Program Files"
del cla_windows
  1. Rerun the installation script.
    • Rerun the Agent installation script. Then, check if the 2 following configuration files have been properly created:
filebeat.yml
winlogbeat.yml
  1. Check the configuration files.
    • The configuration files must include the following collection server addresses (hosts).
hosts: ["collect.vcla.gov-ntruss.com:5043"]

※ If the configuration files are empty or the above content does not exist, log collection may fail.

  1. Restart service.
    • Once the files are properly configured, restart the service with the following commands:
Start-Service winlogbeat
Start-Service filebeat

If necessary, you can provide Customer Support with error message and or log file directory for faster support.