Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Show all

Flow Control

Updated on 2024-12-02 GMT+08:00

Flow control can be implemented via an independent API.

  1. Log in to the CSS management console.
  2. Choose Clusters in the navigation pane. On the Clusters page, locate the target cluster and click Access Kibana in the Operation column.
  3. In the navigation pane on the left, choose Dev Tools and run the commands to query traffic control information.
    • Check the traffic control status of all nodes.
      GET /_nodes/stats/filter
    • View the traffic control status of a specific node.
      GET /_nodes/{nodeId}/stats/filter

      {nodeId} indicates the ID of the node you want to check.

    Example response:

    {
      "_nodes" : {
        "total" : 1,
        "successful" : 1,
        "failed" : 0
      },
      "cluster_name" : "css-flowcontroller",
      "nodes" : {
        "ElBRNCMbTj6L1C-Wke-Dnw" : {
          "name" : "css-flowcontroller-ess-esn-1-1",
          "host" : "10.0.0.133",
          "timestamp" : 1613979513747,
          "flow_control" : {
            "transport" : {
              "concurrent_req" : 0,
              "rejected_concurrent" : 0,
              "rejected_new" : 0,
              "rejected_deny" : 0
            },
            "http" : {
              "concurrent_req" : 0,
              "rejected_concurrent" : 0,
              "rejected_new" : 0,
              "rejected_deny" : 0
            },
            "memory" : {
              "memory_allow" : 41,
              "memory_rejected" : 0
            },
            "cpu": {
              "rejected_cpu" : 0
            }
            "ip_address" : [
              {
                "ip" : "/10.0.0.198",
                "count" : 453
              },
              {
                "ip" : "/198.19.49.1",
                "count" : 42
              }
            ],
            "url_sample" : [
              {
                "url" : "/*/_search?pretty=true",
                "method" : "GET",
                "remote_address" : "/10.0.0.198:16763",
                "count" : 1
              }
            ]
          }
      }
    }

    In the response, the information of each node is separated. The http field records the numbers of concurrent connections and new connections. The memory records memory flow control statistics. The ip_address field records the recent client IP addresses that are accessed most recently. The url_sample field records the recent URLs that are requested most frequently. The cpu field records CPU flow control statistics.

    Table 1 Response parameters

    Parameter

    Description

    concurrent_req

    Number of TCP connections of a node, which is recorded no matter whether flow control is enabled. This value is similar to the value of current_open of the GET /_nodes/stats/http API but is smaller, because whitelisted IP addresses and internal node IP addresses are not counted.

    rejected_concurrent

    Number of concurrent connections rejected during HTTP flow control. This value is not cleared when HTTP flow control is disabled.

    rejected_new

    Number of new connections rejected during HTTP flow control. This value is not cleared when HTTP flow control is disabled.

    rejected_deny

    Number of requests rejected based on the blacklist during HTTP flow control. This value is not cleared when HTTP flow control is disabled.

    memory_allow

    Number of allowed requests during memory flow control. This parameter takes effect when memory flow control is enabled, and its value is not cleared after memory flow control is disabled. The requests from the paths in the allow_path whitelist are not recorded. If allow_path is set to **, no requests are recorded.

    memory_rejected

    Number of rejected requests during memory flow control. This parameter takes effect when memory flow control is enabled, and its value is not cleared after memory flow control is disabled. The requests from the paths in the allow_path whitelist are not recorded. If allow_path is set to **, no requests are recorded.

    rejected_cpu

    Number of requests rejected when the CPU flow control threshold is exceeded. This parameter takes effect when CPU flow control is enabled, and its value is not cleared after CPU flow control is disabled.

    ip_address

    IP addresses and the number of requests. For details, see Table 2.

    url_sample

    Request path sampling. The number of URLs of a request are collected based on the configured time and sampling interval. For details, see Table 3.

    Table 2 ip_address

    Parameter

    Description

    ip

    Source IP address for accessing the node.

    method

    Number of access requests from an IP address.

    Table 3 url_sample

    Parameter

    Description

    url

    Request URL

    method

    Method corresponding to the request path

    remote_address

    Source IP address and port number of the request

    count

    How many times a path is sampled

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback