Management

Prev Next

Available in Classic and VPC

In Management, you can check the log collection status of various NAVER Cloud Platform services and enable/disable log collection. You can also configure daily reports to receive status updates on major events and log collection via email.

Management interface

The basic layout of the Management interface when using Cloud Log Analytics is as follows:
cla-use-management-screen_ko

Component Description
① Menu name Shows the current menu name and number of services being viewed.
② Basic features Configure Daily Reports, view Cloud Log Analytics details, export a list of services as an Excel file, and refresh the page
③ Applicable Services for Collection Services from which logs can be collected via Cloud Log Analytics. Displays the list of your applicable services when clicked
④ Post-Creation Features Enable Collection and Disable Collection of Server Logs
⑤ Search Bar Enter the service name or the server's private IP and click i-cla-findto search
⑥ List A list of your services and their details

Viewing and Downloading Your Service List

You can view a list of services available for log collection and their details through Cloud Log Analytics, as well as download the list as an Excel file.

Viewing Service Lists

To view a list of services available for log collection and their details through Cloud Log Analytics, follow the steps below.

  1. From the NAVER Cloud Platform console, click i_menu > Services > Management & Governance > Cloud Log Analytics menu in order.
  2. Click the Management menu.
  3. Click the tab for the service whose list you want to view.
  4. Check the summary from the service list, or click a server to check its details.
    • The information fields for servers in the [Server(VPC)]/[Server], [Bare Metal Server(VPC)]/[Bare Metal Server] tab menus are as follows:
      • Server Name: The names of your servers
      • Server Image Name: The names of your server images
      • Status: Server operational status
      • Private IP: The server's private IP address
      • VPC(VPC)/Zone(Classic): VPC/Zone where server is located
      • Configuration Status: Log collection configuration status
      • Details
        • OS: Server operating system
        • Created: Server creation date
        • Server Start: Server start time
        • Log Collection Configured: Log collection configuration date
        • Public IP: The server’s public IP address
        • Log Collection Agent Version: The version of the Log Collection Agent installed on the server
        • Number of Log Collection Types: The number of log types you configured your server to collect
        • Install Key: The Install Key for installing your Log Collection Agent
    • For the description of other service information fields, refer to the guide of each service.

Downloading Service Lists

To download the list of services available for log collection through Cloud Log Analytics as an Excel file, follow the steps below.

  1. From the NAVER Cloud Platform console, click i_menu > Services > Management & Governance > Cloud Log Analytics menu in order.
  2. Click the Management menu.
  3. Click the tab that corresponds to the service whose list you want to download.
  4. Click the [Download] button.
    • This downloads the list of services and their summaries as an Excel file.

Log Collection

You can configure server log collection details with the NAVER Cloud Platform console. You can use various default templates provided by the platform or manually configure logs to collect.

  • Logs from the following services are automatically integrated and collected by Cloud Log Analytics without any configuration:
    • DB Server logs from Cloud DB for MySQL, Cloud DB for MongoDB, Cloud DB for MSSQL, and Cloud DB for PostgreSQL
    • Logs from Search Engine Service (VPC) and Cloud Data Streaming Service
  • To configure logs for the Ncloud Kubernetes Service(VPC), go to Ncloud Kubernetes Service(VPC), not Cloud Log Analytics. For more information, see Accessing and Managing Clustersin the Ncloud Kubernetes Service (VPC) User Guide.

To collect logs for a server, follow the steps below.
1. Configure log collection settings
2. Install the Log Collection Agent
3. Check the Agent Process and Log Collection

Note

There are two ways to configure log collection for server logs automatically created through auto scaling:

  • In Cloud Log Analytics, configure log collection for each server, then access each server to install the log collection agent
  • Use an image from a server whose log collection is already configured with Cloud Log Analytics to create an auto scaling group
    • The logs configured for collection on the server from which the image was created are sent to Cloud Log Analytics to be used in the same manner.
    • In the Management page, the Settings status field of an automatically created server is displayed as Not Set.

For further details on auto scaling, see the Auto Scaling User Guide.

1. Configure log collection settings

To configure log data required for data collection in the NAVER Cloud Platform console, follow the steps below.

  1. From the NAVER Cloud Platform console, click i_menu > Services > Management & Governance > Cloud Log Analytics menu in order.
  2. Click the Management menu.
  3. Click the tab for the service whose logs you want to collect.
  4. From your list of servers, select the server whose logs you want to collect, and click [Collection Configuration].
  5. When the log collection settings popup window appears, select a log collection template from the Log Template dropdown menu.
    • To collect logs not provided via log templates, select Custom Log, enter your configuration details, then click [Add].
      • Log Type: Enter your log type. You can search for the entered log type to display the logs on your dashboard.
      • Log Directory: Enter the directory and filename of your log file
      • Enable Symbolic Link: Check the box to collect logs even if the Log Directory is a symbolic link.
    • To delete the a log template, click the [Delete].
  6. Click the [Apply] button.
  7. When the guide popup window for installing the agent on the server appears, check the details, then click [Close].
    • For more information on Agent installation, see 2. Installing the Log Collection Agent.
    • Click [Copy to Clipboard] to copy the log collection agent installation command into the clipboard.
    • When configuring collection for multiple servers with different operating systems, note that the log collection agent installation command is different for each OS type.
Note

If the number of custom log types exceeds 20, it may affect the search and export features.

2. Install the Log Collection Agent

To collect logs via Cloud Log Analytics, Configure Log Collection via the Console to install the log collection agent on the server. Run the log collection agent installation command to automatically download, install, preferences, set up, and run the agent and begin data collection.

To install a log collection agent, follow the steps below.

  1. Access the server you want to collect logs from.
    • Installation requires root permissions, so you need to work with a root account or an account with the sudo permission.
    • For more information about accessing servers, see either Server Access (VPC) or Server Access (Classic).
  2. 1. Run the log collection agent installation command on the server that you identified in step 7 of Configure Log Collection via the Console.
    • When agent installation and configuration are complete, the following message is displayed.
      ================= Finish Installation =================
    • An install key is included in the log collection agent installation command. This must be accurately entered for the agent to be installed successfully.

3. Check the Agent Process and Log Collection

After completing log collection configuration and log collection agent installation, you can check the status of the agent process and log collection. For information on how to check this information on each server OS, follow the steps below.

For Linux

  1. Access the server.
  2. Run the following command in the terminal to check the agent process.
    ps -ef | grep filebeat
    cla-use-management-check-linux
  3. Check logs generated as you run the command in the terminal.
    • Example: Running the logger message_test command leaves a log in SYSLOG.
    • For more information about checking logs, see Dashboard or Search.

For Windows

  1. Access the server.
  2. Enter the following command in Windows PowerShell to check the agent process.
    Get-Process -Name *beat*
    cla-use-management-check-windows
  3. Check logs generated as you install and run the agent.
    • Logs generated as you install and run the agent are classified as Windows event logs.
    • For more information about checking logs, see Dashboard or Search.
Note

If logs are not collected, check if an error occurred while installing the agent, and proceed with Log Collection Agent Installation again.

Disabling Log Collection

To disable log collection from a server, follow the steps below.
1. Disable Log Collection in Console
2. Remove Log Collection Agent

1. Disable Log Collection in Console

The following describes how to disable log collection in the NAVER Cloud Platform console.

  1. From the NAVER Cloud Platform console, click i_menu > Services > Management & Governance > Cloud Log Analytics menu in order.
  2. Click the Management menu.
  3. Click the tab for the service whose log collection you want to disable.
  4. From your list of servers, select the server whose log collection you want to disable, and click the [Disable Collection] button.
  5. When the Disable Log Collection pop-up window appears, check the information and click the [Apply] button.
  6. When the guide popup window for stopping server log collection appears, check the details and click the [Close] button.
    • Failing to delete the log collection agent from the server causes unnecessary internal traffic even after disabling collection.
    • Click [Copy to Clipboard] to copy the log collection agent deletion command into the clipboard.
    • When disabling collection for multiple servers with different operating systems, note that the command is different for each OS type.
      • For Linux and Bare Metal servers, the commands to disable collection are the same.

2. Remove Log Collection Agent

After you Disable Log Collection via the Console, you must delete the log collection agent.

To delete a log collection agent, follow the steps below.

  1. Access the server.
  2. 1. Run the Delete Log Collection Agent command on the server that you identified in step 6 of Disable Log Collection via the Console.
    • When log collection agent deletion is completed, the following message is displayed.
      • For Linux: Success Remove Agent
      • For Windows: Remove Agent

Configure Daily Reports

Cloud Log Analytics includes a daily report feature that allows you to receive a daily email update on the status of major events and log collection for the current month, up to the previous day.

The following describes how to send and receive daily reports.

  1. From the NAVER Cloud Platform console, click i_menu > Services > Management & Governance > Cloud Log Analytics menu in order.
  2. Click the Management menu.
  3. Click the [Notification Settings] button.
  4. Click the Receive Daily Report checkbox to choose whether to receive daily reports.
  5. From the Notification Recipient Group list, select the checkbox for the group you want to send reports, and then click the [Apply] button.
    • To search for a specific notification group in the list, enter the name of the group and click i-cla-find.
    • Clicking [Manage Notification Recipient Groups] sends you to the Notification Recipient page where you can manage notification recipients.
    • For more information on how to manage notification recipients, see the Cloud Insight user guide or the Notification Recipient user guide.