> For the complete documentation index, see [llms.txt](https://docs.vngcloud.vn/vng-cloud-document/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vngcloud.vn/vng-cloud-document/vmonitor/dashboards/logs/lam-viec-voi-product-logs/lam-viec-voi-vlb-log.md).

# Working with vLB-Log

To view vLB logs, access vMonitor Platform at [the link](https://hcm-3.console.vngcloud.vn/vmonitor) , then go to **Infrastructure list/vLB Log.** Here you can see a list of all vLBs on your HCM03. On this screen, you will see basic information columns such as:

* **vLB Project** : name of vLB.
* **Log Project** : log project will contain vLB logs when you enable "Detailed Monitoring".
* **Log Project Usage** : information about the usage level of the Log Project that you have attached to this vLB.
* **Monitoring Status** : monitoring status of vLB. If "Detailed Monitoring" has not been enabled, the status will be INACTIVE, if enabled, the status will be ACTIVE, and if vLB has been deleted, it will be DELETED.
* **Detailed Monitoring** : enable or disable monitoring of Logs of this vLB.

<figure><img src="https://docs.vngcloud.vn/~gitbook/image?url=https%3A%2F%2F3672463924-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FB0NrrrdJdpYOYzRkbWp5%252Fuploads%252FDpanZuQOFYSchmvjqYgq%252Fimage.png%3Falt%3Dmedia%26token%3Db83f8d09-82ce-4f5c-a437-b309a76932d5&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=b0948de&#x26;sv=1" alt=""><figcaption></figcaption></figure>

To enable monitoring, you need to click **enable** in the **Detailed Monitoring column.**

The system will display a Popup and you need **to select Log Project** to contain the logs of this vLB, then click " **enable** ". If you don't have any Log Project yet, you can click "Create a log project" in the popup or go through the Quota & Usage tab to create a Log Project first.

After enabling, you will see the status of this vLB change to **ACTIVE** , and you can access the Log Project you just selected to view the logs.

If you need to change the Log Project containing Logs, you can select the 3-dot button and select " **Edit Log Project** " to change.

If you no longer need to view vLB logs, you can **disable the Detailed Monitoring** column .

***

### Data fields: <a href="#lamviecvoivlb-log-cacfieldsdulieu" id="lamviecvoivlb-log-cacfieldsdulieu"></a>

For Application Load Balancer, you will see HTTP Access Logs with the fields:

* httpRequest.clientIp
* httpRequest.clientPort
* httpRequest.requestMethod
* httpRequest.requestUrl
* httpRequest.requestSize
* httpRequest.responseSize
* httpRequest.status
* httpRequest.latency
* httpRequest.userAgent
* httpRequest.referer

For Network Load Balancer, you will see TCP Connection Logs with the fields:

* jsonPayload.connection.clientIp
* jsonPayload.connection.clientPort
* jsonPayload.connection.requestSize
* jsonPayload.connection.responseSize
* jsonPayload.connection.rtt

***

## Export vLB access logs to vDB

In addition to viewing logs on vMonitor Platform, you can export vLB **access logs** to your own **vDB Kafka** or **vDB OpenSearch** cluster, so you can store, search, and analyze logs on your own terms.

The two destinations are independent: you can export to Kafka only, to OpenSearch only, or enable both at the same time for a single vLB.

### Prerequisites

**If exporting to vDB Kafka**, you need on vDB Kafka:

* A running Kafka Cluster with public access enabled.
* A Topic in the Cluster to receive access logs.
* A Kafka user with issued credentials and write permission on that Topic.

**If exporting to vDB OpenSearch**, you need on vDB OpenSearch:

* A running OpenSearch Cluster with a public log-ingest endpoint.
* An account (Username/Password) with write permission on the Cluster.

### Enable export to vDB Kafka

1. Open the vLB in the log mapping list, then select **Enable log to vDB Kafka**.
2. Toggle **Enable logging** on.
3. Select:

| Field       | Notes                                                                                                     |
| ----------- | --------------------------------------------------------------------------------------------------------- |
| **Cluster** | The Kafka Cluster that will receive access logs.                                                          |
| **Topic**   | The Topic in the selected Cluster.                                                                        |
| **User**    | The Kafka user used to write logs.                                                                        |
| **Mode**    | Authentication mechanism — choose **mTLS** or **SASL** (whichever both the Cluster and the user support). |

4. Click **Save**.

{% hint style="info" %}
The system automatically fetches the Kafka user's credentials from vDB — you do not need to enter any credential manually.
{% endhint %}

### Enable export to vDB OpenSearch

1. Open the vLB in the log mapping list, then select **Enable log to vDB OpenSearch**.
2. Toggle **Enable logging** on.
3. Select and enter:

| Field        | Requirement                                                                                                   |
| ------------ | ------------------------------------------------------------------------------------------------------------- |
| **Cluster**  | The OpenSearch Cluster that will receive access logs.                                                         |
| **Username** | Account with write permission on the Cluster. 3–31 characters, made of letters, digits, and `_`, `.`, `-`.    |
| **Password** | At least 8 characters, including uppercase, lowercase, digit, and one special character from `@ $ ! % * ? &`. |

4. Click **Save**.

{% hint style="warning" %}
The system verifies the connection to the OpenSearch Cluster right when you click **Save**. If the Username or Password is incorrect, the action is rejected at this step.
{% endhint %}

### Switch to another Cluster

Reopen the corresponding dialog, select the new Cluster (and update related fields if needed), then click **Save**. The system automatically redirects the access log export to the new Cluster.

### Disable access log export

Reopen the corresponding dialog, toggle **Enable logging** off, and click **Save**. The system stops exporting access logs to that Cluster.

### Troubleshooting

| Message                                         | Cause & action                                                                                  |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Error about Cluster, Topic, User, or permission | The matching resource on vDB is not ready. Check its status and permissions on vDB, then retry. |
| OpenSearch connection error on **Save**         | Wrong Username or Password. Re-enter the correct credentials and save again.                    |

***

#### Some notes: <a href="#lamviecvoivlb-log-motsochuy" id="lamviecvoivlb-log-motsochuy"></a>

* After being created, the vLB will take about minutes (maximum 10 minutes) to synchronize to vMonitor Platform.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vngcloud.vn/vng-cloud-document/vmonitor/dashboards/logs/lam-viec-voi-product-logs/lam-viec-voi-vlb-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.