---
title: "Management"
slug: "cla-use-management"
updated: 2026-10-08T07:17:08Z
published: 2026-10-08T07:17:08Z
canonical: "guide.ncloud-docs.com/cla-use-management"
---

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

# Management

Available in Classic and VPC

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 Management interface includes the following components: ![cla-use-management-screen_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/cla-use-management-screen_en.png?sv=2026-02-06&spr=https&st=2026-10-27T14%3A11%3A29Z&se=2026-10-27T15%3A11%3A29Z&sr=c&sp=r&sig=LoVwsnDznI8vovQWYGJSIS0HD4R%2F1oFRV4s7OQgHpUk%3D)

| Component | Description |
| --- | --- |
| ① Menu name | Current menu name and the number of services being viewed. |
| ② Basic features | [Set daily reports](/docs/en/cla-use-management#DailyReport%EC%84%A4%EC%A0%95), view Cloud Log Analytics details, [export a list of services as an Excel file](/docs/en/cla-use-management#%EC%84%9C%EB%B9%84%EC%8A%A4%EB%AA%A9%EB%A1%9D%EB%8B%A4%EC%9A%B4%EB%A1%9C%EB%93%9C), 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](/docs/en/cla-use-management#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91%EC%84%A4%EC%A0%95) and [Disable collection](/docs/en/cla-use-management#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91%ED%95%B4%EC%A0%9C) of server logs. |
| ⑤ Search bar | Enter the service name or the server's private IP and click ![i-cla-find](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/i-cla-find.png?sv=2026-02-06&spr=https&st=2026-10-27T14%3A11%3A29Z&se=2026-10-27T15%3A11%3A29Z&sr=c&sp=r&sig=LoVwsnDznI8vovQWYGJSIS0HD4R%2F1oFRV4s7OQgHpUk%3D) to search. |
| ⑥ List | A list of your services and their details. |

## View and download 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.

### View service list

To view a list of services available for log collection and their details through Cloud Log Analytics:

1. In the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Management & Governance** > **Cloud Log Analytics**.
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**: Name of the server you have.
    - **Server image name**: Server image of the server you have.
    - **Status**: Operation status of the server.
    - **Private IP**: Private IP of the server.
    - **VPC**(VPC)/**Zone**(Classic): VPC/Zone where server is located.
    - **Settings status**: Log collection settings.
    - Details
      - **OS**: OS of the server.
      - **Creation date and time**: Creation date and time of the server.
      - **Running date and time**: Running date and time of the server.
      - **Log collection settings date and time**: Date and time log collection was set.
      - **Public IP**: Public IP of the server.
      - **Number of log collection types**: Number of log types set to be collected.
      - **Install key**: Install key used to install the log collection agent.
  - For more information about other services, see the user guide of each service.
    - [Cloud DB for MySQL user guide](/docs/en/clouddbformysql-overview)
    - [Ncloud Kubernetes Service (VPC) user guide](/docs/en/k8s-k8soverview)
    - [Cloud DB for MSSQL user guide](/docs/en/clouddbformssql-overview)
    - [Cloud DB for PostgreSQL (VPC) user guide](/docs/en/clouddbforpostgresql-overview)
    - [Search Engine Service (VPC) user guide](/docs/en/ses-overview)
    - [Cloud Data Streaming Service (VPC) user guide](/docs/en/cdss-overview)

### Download service list

To download the list of services available for log collection through Cloud Log Analytics as an Excel file:

1. In the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Management & Governance** > **Cloud Log Analytics**.
2. Click the **Management** menu.
3. Click the tab that corresponds to the service whose list you want to download.
4. Click **[Download]**.
  - This downloads the list of services and their summaries as an Excel file.

## Collect logs

You can configure server log collection details in 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 [Access and manage clusters](/docs/en/k8s-k8suse-cluster) in the Ncloud Kubernetes Service (VPC) user guide.

To collect logs for a server: [1. Configure log collection in the console](/docs/en/cla-use-management#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91%EC%84%A4%EC%A0%95) [2. Install log collection agent](/docs/en/cla-use-management#2%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91Agent%EC%84%A4%EC%B9%98) [3. View agent process and log collection](/docs/en/cla-use-management#3Agent%ED%94%84%EB%A1%9C%EC%84%B8%EC%8A%A4%EB%B0%8F%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91%ED%99%95%EC%9D%B8)

              Note

              

There are two ways to configure log collection for server logs automatically created through Auto Scaling.

- In Cloud Log Analytics, [configure log collection](/docs/en/cla-use-management#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91%EC%84%A4%EC%A0%95) for each server, then access each server to [install the log collection agent](/docs/en/cla-use-management#2%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91Agent%EC%84%A4%EC%B9%98)
- Use an image from a server whose log collection is already configured with Cloud Log Analytics to create an Auto Scaling group, then simply configure the settings in the console.
  - The logs configured for collection on the server from which the image was created are transferred to Cloud Log Analytics, but they are not actually stored there. To save the logs, simply configure the collection settings in the console. This ensures that the logs are transferred and saved without requiring you to install or configure anything directly on the server.

For more information on Auto Scaling, see the [Auto Scaling user guide](/docs/en/autoscaling-overview).

### 1. Configure log collection in the console

To configure log data required for data collection in the NAVER Cloud Platform console:

1. In the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Management & Governance** > **Cloud Log Analytics**.
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 setting]**.
5. When the log collection setting popup appears, select a log collection template from the **Log Template** drop-down menu.
  - To collect logs not provided via log templates, select **Custom Log**, enter your configuration details, then click **[Add]**.
    - **Log type**: Enter the log type. You can search for the entered log type to display the logs on your dashboard.
    - **Log path**: Enter the path and file name of the log file. You can use wildcards (*) in file names.
      - Example: /home/nginx/log/access*.log — collects all .log files beginning with access.
      - Example: /var/log/httpd/localhost_error_log_* — collects all logs whose file names change when a date is appended.
    - **Use symbolic link**: If you select the checkbox, it is collected even if the **Log path** is a symbolic link.
  - To delete the a log template, click **[Delete]**.
6. Click **[Apply]**.
7. When the guide popup for installing the agent on the server appears, check the details, then click **[Close]**.
  - For more information about agent installation in server, see [2. Install log collection agent](/docs/en/cla-use-management#2%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91Agent%EC%84%A4%EC%B9%98).
  - Click **[Copy to clipboard]** to copy the **log collection agent installation command** into the clipboard.

              Note

              

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

### 2. Install log collection agent

To collect logs via Cloud Log Analytics, [Configure log collection in the console](/docs/en/cla-use-management#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91%EC%84%A4%EC%A0%95) to install the log collection agent on the server. Run the log collection agent installation command to automatically download, install, set up, and run the agent and begin data collection.

To install a log collection agent:

1. Access the server you want to collect logs from.
  - Installation requires root privileges, so you need to work with a root account or an account with the sudo privilege.
  - For more information about accessing servers, see either [Server access (VPC)](/docs/en/server-access-vpc) or [Server access (Classic)](/docs/en/server-access-classic).
2. Run the **log collection agent installation command** on the server that you obtained in step 7 of [1. Configure log collection in the console](/docs/en/cla-use-management#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91%EC%84%A4%EC%A0%95).
  - 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. View 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. To check this information on each server OS:

#### For Linux servers

1. Access the server.
  - For more information about accessing servers, see either [Server access (VPC)](/docs/en/server-access-vpc) or [Server access (Classic)](/docs/en/server-access-classic).
2. Run the following command in the terminal to check the agent process:

```
ps -ef | grep filebeat
```

![cla-use-management-check-linux](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/cla-use-management-check-linux.png?sv=2026-02-06&spr=https&st=2026-10-27T14%3A11%3A29Z&se=2026-10-27T15%3A11%3A29Z&sr=c&sp=r&sig=LoVwsnDznI8vovQWYGJSIS0HD4R%2F1oFRV4s7OQgHpUk%3D)
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](/docs/en/cla-use-dashboard) or [Search](/docs/en/cla-use-search).

#### For Windows servers

1. Access the server.
  - For more information about accessing servers, see either [Server access (VPC)](/docs/en/server-access-vpc) or [Server access (Classic)](/docs/en/server-access-classic).
2. Enter the following command in Windows PowerShell to check the agent process:

```
Get-Process -Name *beat*
```

![cla-use-management-check-windows](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/cla-use-management-check-windows.png?sv=2026-02-06&spr=https&st=2026-10-27T14%3A11%3A29Z&se=2026-10-27T15%3A11%3A29Z&sr=c&sp=r&sig=LoVwsnDznI8vovQWYGJSIS0HD4R%2F1oFRV4s7OQgHpUk%3D)
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](/docs/en/cla-use-dashboard) or [Search](/docs/en/cla-use-search).

              Note

              

If logs are not collected, check if an error occurred while installing the agent, and proceed with [log collection agent installation](/docs/en/cla-use-management#2%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91Agent%EC%84%A4%EC%B9%98) again.

## Disable log collection

To disable log collection from a server: [1. Disable log collection in the console](/docs/en/cla-use-management#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91%ED%95%B4%EC%A0%9C) [2. Remove log collection agent](/docs/en/cla-use-management#2%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91Agent%EC%82%AD%EC%A0%9C)

### 1. Disable log collection in the console

To disable log collection in the NAVER Cloud Platform console:

1. In the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Management & Governance** > **Cloud Log Analytics**.
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 **[Disable collection]**.
5. When the Disable log collection popup appears, check the information and click **[Apply]**.
6. When the guide popup for stopping server log collection appears, check the details and click **[Close]**.
  - Failing to [delete the log collection agent](/docs/en/cla-use-management#2%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91Agent%EC%82%AD%EC%A0%9C) 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.
  - For Linux and Bare Metal servers, the commands to disable collection are the same.

### 2. Remove log collection agent

After you [disable log collection in the console](/docs/en/cla-use-management#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91%ED%95%B4%EC%A0%9C), you must delete the log collection agent.

To delete a log collection agent:

1. Access the server.
  - For more information about accessing servers, see either [Server access (VPC)](/docs/en/server-access-vpc) or [Server access (Classic)](/docs/en/server-access-classic).
2. Run the **log collection agent deletion command** on the server that you obtained in step 6 of [1. Disable log collection in the console](/docs/en/cla-use-management#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EB%A1%9C%EA%B7%B8%EC%88%98%EC%A7%91%ED%95%B4%EC%A0%9C).
  - When log collection agent deletion is completed, the following message is displayed:
    - For Linux: `Success Remove Agent`
    - For Windows: `Remove Agent`

## Set 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.

To send and receive daily reports:

1. In the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Management & Governance** > **Cloud Log Analytics**.
2. Click the **Management** menu.
3. Click **[Notification settings]**.
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 **[Apply]**.
  - To search for a specific notification group in the list, enter the name of the group and click ![i-cla-find](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/i-cla-find.png?sv=2026-02-06&spr=https&st=2026-10-27T14%3A11%3A29Z&se=2026-10-27T15%3A11%3A29Z&sr=c&sp=r&sig=LoVwsnDznI8vovQWYGJSIS0HD4R%2F1oFRV4s7OQgHpUk%3D).
  - Clicking **[Manage notification recipient group]** 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](/docs/en/cloudinsight-cloudinsightoverview) or the [Notification Recipient user guide](/docs/en/notification-recipient-use).