tencent cloud

Feedback

Access Point Gateway Engine Monitoring

Last updated: 2024-07-31 17:31:54
    DLC provides monitoring services for the access point gateway engine based on TCOP service, ensuring you can understand the gateway status in real time.

    Notes

    Before using DLC's monitoring service, you need to activate the TCOP service (for usage details, see TCOP Documentation). If the service has not been activated yet, it can be activated using the root account. TCOP service usage may incur related tariffs, for detailed tariff information, see TCOP Billing Overview.

    Monitoring Entrance

    Entrance one: DLC Console

    1. Log in to the <1>Standard Engine> page, and select the Service Region.
    2. Select the Standard Engine, and click on Monitoring at the access point to enter the monitoring data display interface.

    Configuration Entrance: TCOP

    1. Log in to the TCOP Console, the account must have the relevant permissions.
    2. From the left menu, select Cloud Product Monitoring, enter the Policy Management page under Alarm Management, select Data Lake Computing, and choose the corresponding Access Point Gateway Engine.

    Access Point Gateway Engine Monitoring Configuration Type

    Creating alarm policy

    1. DLC Access Point Gateway supports alarm capabilities. Log in to TCOP, click Alarm Management, and select the Policy Management page.
    2. Click New Policy, for policy type choose "Data Lake Computing". Access Point Gateway supports alarms for three dimensions, including:
    "Gateway" alarm dimension is: appid/gatewayid.
    "Gateway (Multi-dimensional)" alarm dimension is: appid/gatewayid/instanceid.
    "Gateway Engine (Multi-dimensional)" alarm dimension is: appid/gatewayid/engineid/processid.
    Name
    Supported Dimensions
    Advantages and Use Cases
    Gateway (Multi-dimensional)
    Supports: CPU, Memory, Disk, Network Fine-grained Alerting.
    For example, to configure an alert for the CPU utilization of an Access Point Gateway, you can choose to configure one, several instances under a specific Access Point Gateway, or any instance node triggering the threshold to alert.
    Alert supports more dimensions, and the alert method is more flexible.
    Basic Metrics are recommended to use this approach.
    API Gateway
    Mainly aimed at monitoring the overall load situation of the current gateway, aggregating basic metrics according to Access Point Gateway Nodes, and supporting Service-level Metric Alerts.
    For example: execute_statement_num (number of statements executed), opened_operation_num (number of operations opened), launch_engine_num (number of engines started), engine_process_thread_num (number of threads started by the engine).
    Supports Dashboard. Suitable for Single-node access point gateway or service metric alert.
    Gateway Engine (Multidimensional)
    The Gateway Engine refers to the monitoring and alarm of the process of starting the DLC engine by the Access Point Gateway.
    For example: engine_process_thread_num (number of threads started by the engine), mainly aimed at monitoring the process information of the engine started by the current Access Point Gateway
    Supports fine-grained alerting, for example: commonly configure any engine's process count under a specific Access Point Gateway ID to reach the threshold to trigger an alert. Suitable for alerting on process metrics started by the Access Point Gateway.
    
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support