edit-icon download-icon

Entry points

Last Updated: Mar 07, 2018

The HTTP interfaces, RPC services, and Java methods that are accessed and called by users or other systems are called entry points and displayed on the Entry Points page.

The Rate Limiting and Degradation module detects entry points automatically, based on which you can conveniently configure rate limiting on a specific entry point.

The Entry Points page includes the Entry Points and Dependencies tabs, grouping entry points by service type:

  • Entry Points: Displays the inbound traffic volume of the current application, and you can apply rate limiting to control the traffic.
  • Dependencies: Displays the outbound traffic of the services that this application provides, and you can also apply rate limiting and degradation to these services.

The Entry Points tab displays the real-time QPS and accumulated service volume in the last one minute.

The rate limiting status indicates whether rate limiting is enabled depending on whether rate limiting rules are available. If no rate limiting rules are available, rate limiting is disabled.

Note:The system loads the entry points of alive instances in the default group. To check entry points of a specific instance, change the IP address.

Add rate limiting rules

  1. Log on to the EDAS console, click Applications on the left-side navigation pane, and select a deployed service provider application.

  2. On the left-side navigation pane of the application details page, click Rate Limiting and Degradation > Entry Points.

  3. On the Rate Limiting Monitor page, select the entry point to apply rate limiting, and click Add Rate Limiting in the Actions column.

  4. Set rate limiting rules on the Configure Rules page.

    Field description:

    • Resource: This option is already selected on the rate limiting monitoring page and cannot be changed. The QPS and threads of the resource will be restricted after you configure rate limiting rules.
    • Applications: This option specifies whether the rate limiting applies to all applications or specified applications.
    • Granularity: This option specifies whether the rate limiting applies at QPS level or thread level. QPS rate limiting restricts the number of requests per second, and thread rate limiting restricts the number of threads. Generally, the larger the number of threads, the larger the QPS value is. However, the QPS of a thread is usually larger than 1. The thread sends requests continuously and the response time is only 10 ms to 99 ms.
    • Rate Limiting Threshold: Rate limiting is triggered when the value exceeds the threshold.
  5. Click OK.

Thank you! We've received your feedback.