GITBOOK-736: No subject

Author: nhilth-vngcloud

English/.gitbook/assets/Kafka-Cluster-Database.jpg

@@ -2,7 +2,7 @@
 
 Kafka Cluster DB is a new service on the vDB platform, providing a powerful and flexible Kafka server cluster to manage real-time event streaming. With Kafka Cluster DB, you can easily build large-scale data processing applications, messaging systems, and centralized logging with high scalability, data durability, and outstanding performance.
 
-<figure><img src="../../.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/Kafka-Cluster-Database.jpg" alt=""><figcaption></figcaption></figure>
 
 ## Features <a href="#tinh-nang-moi" id="tinh-nang-moi"></a>
 
@@ -32,14 +32,12 @@ Kafka Cluster DB is a new service on the vDB platform, providing a powerful and
 
 Comparison between Kafka Cluster DB Managed Service and Traditional Kafka Cluster (self-managed)
 
-| **Criteria**                | **Kafka Cluster DB Managed Service**                                                                                 | **Traditional Kafka Cluster**                                                                     |
-| --------------------------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
-| **Cluster management**             | The service provider (GreenNode vDB) is responsible for managing, maintaining, upgrading and monitoring the Kafka cluster.              | Users self-manage the entire Kafka cluster, including installation, configuration, maintenance, upgrades and monitoring. |
-| **Configuration and deployment**  | Easy to configure and deploy through web interface or API.                                                     | Requires in-depth Kafka knowledge and system administration skills for installation and configuration.         |
-| **Scaling**                 | Easy to scale by adding resources through the management interface.                                               | Requires manual scaling process, which can be complex and time-consuming.                              |
-| **Monitoring and troubleshooting** | The service provider (GreenNode vDB) provides monitoring tools and troubleshooting support.                                | You self-monitor and troubleshoot, requiring expertise and experience.                       |
-| **Cost**                 | Typically lower long-term costs due to savings on infrastructure investment, operational costs and personnel costs. | Higher long-term costs due to the need to invest in infrastructure, operations and personnel.                      |
-| **Flexibility**          | May be limited in customization and control compared to self-managed clusters.                                         | Allows full customization and control of the Kafka cluster.                                               |
-| **Suitable for**             | Businesses that want to focus on application development and don't want to invest heavily in infrastructure management.                    | Businesses with strong technical teams that want full system control and can handle incidents themselves. |
-
-&#x20;
+| **Criteria**                       | **Kafka Cluster DB Managed Service**                                                                                       | **Traditional Kafka Cluster**                                                                                            |
+| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| **Cluster management**             | The service provider (GreenNode vDB) is responsible for managing, maintaining, upgrading and monitoring the Kafka cluster. | Users self-manage the entire Kafka cluster, including installation, configuration, maintenance, upgrades and monitoring. |
+| **Configuration and deployment**   | Easy to configure and deploy through web interface or API.                                                                 | Requires in-depth Kafka knowledge and system administration skills for installation and configuration.                   |
+| **Scaling**                        | Easy to scale by adding resources through the management interface.                                                        | Requires manual scaling process, which can be complex and time-consuming.                                                |
+| **Monitoring and troubleshooting** | The service provider (GreenNode vDB) provides monitoring tools and troubleshooting support.                                | You self-monitor and troubleshoot, requiring expertise and experience.                                                   |
+| **Cost**                           | Typically lower long-term costs due to savings on infrastructure investment, operational costs and personnel costs.        | Higher long-term costs due to the need to invest in infrastructure, operations and personnel.                            |
+| **Flexibility**                    | May be limited in customization and control compared to self-managed clusters.                                             | Allows full customization and control of the Kafka cluster.                                                              |
+| **Suitable for**                   | Businesses that want to focus on application development and don't want to invest heavily in infrastructure management.    | Businesses with strong technical teams that want full system control and can handle incidents themselves.                |

English/.gitbook/assets/step2-after-click-create-kafka.png

@@ -11,29 +11,32 @@ Refer to the GreenNode login guide [here](../../identity-and-access-management-i
 
 ## Step 2: Create a Kafka Cluster
 
-1.  Click the "Create Kafka Cluster" button. 
+1. Click the "Create Kafka Cluster" button.
+
+<figure><img src="../../.gitbook/assets/step2-create-kafka.png" alt=""><figcaption></figcaption></figure>
 
-    <figure><img src="../../.gitbook/assets/image (744).png" alt="" width="228"><figcaption></figcaption></figure>
 2. Fill in the following information:
-   * **Name:** Name your Kafka cluster for easy identification and management.
-   * **Kafka Version:** Choose the Kafka version that suits your needs. Different versions may have different features and performance.
-   * **Flavor (CPU, RAM):** Select the hardware configuration (CPU and RAM) for brokers in the Kafka cluster. This configuration affects the processing capability and performance of the cluster.
-   * **Number of Brokers:** Determine the number of brokers in the Kafka cluster. The number of brokers affects the fault tolerance and scalability of the cluster.
-   * **Storage per Broker (IOPS and Capacity):** Choose the storage capacity and IOPS (Input/Output Operations Per Second) for each broker. This affects the data storage capacity and read/write performance of the cluster.
-   * **Network (VPC, Subnet):** Select the virtual network (VPC) and subnet where the Kafka cluster will be deployed. When initialized, the Kafka cluster will be in private mode (accessible only from within the VPC). After successful initialization, you can enable public access if needed.
-   * **Access Method Control (mTLS, SASL):** Choose the authentication and authorization method for clients connecting to the Kafka cluster. mTLS uses client and server certificates, SASL uses username and password.
-   * **Encryption Mode:** Choose the data encryption mode. By default, encryption in transit (data encrypted when transmitted between client and broker) and within cluster (data encrypted when stored on brokers) are enabled.
-   * **Config Group:** Select the configuration group to apply to the Kafka cluster. The configuration group contains detailed settings for Kafka operations.
-3.  Click the "Create" button to start the Kafka cluster creation process.&#x20;
-
-    <figure><img src="../../.gitbook/assets/image (745).png" alt=""><figcaption></figcaption></figure>
+
+* **Name:** Name your Kafka cluster for easy identification and management.
+* **Kafka Version:** Choose the Kafka version that suits your needs. Different versions may have different features and performance.
+* **Flavor (CPU, RAM):** Select the hardware configuration (CPU and RAM) for brokers in the Kafka cluster. This configuration affects the processing capability and performance of the cluster.
+* **Number of Brokers:** Determine the number of brokers in the Kafka cluster. The number of brokers affects the fault tolerance and scalability of the cluster.
+* **Storage per Broker (IOPS and Capacity):** Choose the storage capacity and IOPS (Input/Output Operations Per Second) for each broker. This affects the data storage capacity and read/write performance of the cluster.
+* **Network (VPC, Subnet):** Select the virtual network (VPC) and subnet where the Kafka cluster will be deployed. When initialized, the Kafka cluster will be in private mode (accessible only from within the VPC). After successful initialization, you can enable public access if needed.
+* **Access Method Control (mTLS, SASL):** Choose the authentication and authorization method for clients connecting to the Kafka cluster. mTLS uses client and server certificates, SASL uses username and password.
+* **Encryption Mode:** Choose the data encryption mode. By default, encryption in transit (data encrypted when transmitted between client and broker) and within cluster (data encrypted when stored on brokers) are enabled.
+* **Config Group:** Select the configuration group to apply to the Kafka cluster. The configuration group contains detailed settings for Kafka operations.
+
+3. Click the "Create" button to start the Kafka cluster creation process.
+
+<figure><img src="../../.gitbook/assets/step2-after-click-create-kafka.png" alt=""><figcaption></figcaption></figure>
 
 ## Step 3: Create a Topic
 
 1. After the Kafka cluster is successfully created, access the management page of that Kafka cluster.
 2. Find and click the "Create Topic" section.
 
-<figure><img src="../../.gitbook/assets/image (748).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/step3-create-topic.png" alt=""><figcaption></figcaption></figure>
 
 3. Fill in the following information:
 
@@ -48,14 +51,14 @@ Refer to the GreenNode login guide [here](../../identity-and-access-management-i
 
 1. In the Kafka cluster management page, find and click the "Create Kafka User" section.
 
-<figure><img src="../../.gitbook/assets/image (749).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/step5-topic-user.png" alt=""><figcaption></figcaption></figure>
 
-2. Fill in the following information:
+1. Fill in the following information:
 
 * **Name:** Name the Kafka user.
 * **Permissions:** In the permission section, click "Add Permission" to select Produce (write data to topic) and Consume (read data from topic) permissions for each topic this user needs to access.
 
-<figure><img src="../../.gitbook/assets/image (750).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/step4-permission-button.png" alt=""><figcaption></figcaption></figure>
 
 * **Access Method:** Choose the access method for the Kafka user (mTLS or SASL) depending on the method enabled for the Kafka cluster.
 
@@ -89,9 +92,10 @@ wget https://archive.apache.org/dist/kafka/3.7.0/kafka_2.13-3.7.0.tgz
 tar -xzf kafka_2.13-3.7.0.tgz
 ```
 
-5.  Next, download the TLS certificates to access the Kafka cluster.&#x20;
+5. Next, download the TLS certificates to access the Kafka cluster.
+
+<figure><img src="../../.gitbook/assets/step5-topic-user.png" alt=""><figcaption></figcaption></figure>
 
-    <figure><img src="../../.gitbook/assets/image (746).png" alt=""><figcaption></figcaption></figure>
 6. On the newly initialized server, upload and extract the TLS certificates and unzip using the command below:
 
 Note: The User ID will be the directory name after extracting the downloaded certificate
@@ -119,7 +123,7 @@ You need to allow this server to access the Kafka cluster as a private client by
 
 Note: Port 9094 for mTLS and 9096 for SASL
 
-<figure><img src="../../.gitbook/assets/image (751).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/step5-port.png" alt=""><figcaption></figcaption></figure>
 
 8. Produce message to Kafka topic
 

English/.gitbook/assets/step2-create-kafka.png

@@ -1,10 +1,8 @@
-# Push data or event logs from Logstash into an initialized OpenSearch Cluster
+# Push data or event logs from Logstash into an OpenSearch Cluster
 
 ## Prerequisites
 
-Suppose you have successfully initialized an OpenSearch Cluster with the following parameters: 
-
-<figure><img src="../../../.gitbook/assets/opensearch5.png" alt=""><figcaption></figcaption></figure>
+Suppose you have successfully initialized an OpenSearch Cluster with the following parameters:
 
 Next, proceed to push sample data into OpenSearch Dashboards or push event logs from Logstash into OpenSearch.
 
@@ -33,16 +31,15 @@ curl -H "Content-Type: application/json" -X PUT "https://<<OpenSearch_ReceiveLog
 
 You can get the `OpenSearch_ReceiveLogs_Endpoint` information from the vDB Portal and replace `<<Master_User_Password>>` with the master account password you previously created.
 
-Example:&#x20;
+Example:
 
 ```bash
 # 2. Create index and data.
 curl -H "Content-Type: application/json" -X PUT "https://open-search-dem-53461-5cfxl-hcm03.vdb-opensearch.vngcloud.vn:9200/ecommerce" -k -H "Authorization: Basic $(echo -n 'master-user:123456789aA@' | base64)" --data-binary "@ecommerce-field_mappings.json"
 curl -H "Content-Type: application/json" -X PUT "https://open-search-dem-53461-5cfxl-hcm03.vdb-opensearch.vngcloud.vn:9200/ecommerce/_bulk" -k -H "Authorization: Basic $(echo -n 'master-user:123456789aA@' | base64)" --data-binary "@ecommerce.ndjson"
 ```
 
-[\
-](https://liemnt5-cidr-11430-2ue3z-hcm03.vdb-opensearch.vngcloud.tech)The result will display as follows:&#x20;
+[<br>](https://liemnt5-cidr-11430-2ue3z-hcm03.vdb-opensearch.vngcloud.tech)The result will display as follows:
 
 ```bash
 curl -H "Content-Type: application/json" -X PUT "https://open-search-dem-53461-5cfxl-hcm03.vdb-opensearch.vngcloud.vn:9200/ecommerce" -k -H "Authorization: Basic $(echo -n 'master-user:123456789aA@' | base64)" --data-binary "@ecommerce-field_mappings.json"
@@ -56,7 +53,7 @@ curl -H "Content-Type: application/json" -X PUT "https://open-search-dem-53461-5
 **Step 3: Check data on OpenSearch Dashboards**
 
 1. Access and log in to **OpenSearch Dashboards**
-2. Go to **Management**, select **Dashboard Management**&#x20;
+2. Go to **Management**, select **Dashboard Management**
 
 <figure><img src="../../../.gitbook/assets/image (7) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
@@ -158,7 +155,7 @@ If logs appear, it means Logstash has successfully sent data to OpenSearch.
 #### **Step 5: View logs on OpenSearch Dashboards**
 
 1. Access and log in to **OpenSearch Dashboards**
-2. Go to **Management**, select **Dashboard Management**&#x20;
+2. Go to **Management**, select **Dashboard Management**
 
 <figure><img src="../../../.gitbook/assets/image (7) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>