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. |
Was this page helpful?