Skip to content

W-14773860 - Updating Traffic Management limits #546

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 19, 2024
Merged

W-14773860 - Updating Traffic Management limits #546

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b5d72ee
W-14773860 - Updating Traffic Management limits
hernanrivero Jan 12, 2024
cc1856f
Fix
hernanrivero Jan 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions modules/ROOT/pages/create-instance-task-flex.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ image:multiple-upstreams.png[Flex Gateway manages the traffic to multiple upstre

=== Routes

Each API instance supports up to 10 routes and each route can support up to 10 upstream services. Configure what requests a route can receive by defining route rules and a route order. At least one route per API instance is required.
Each API instance supports up to 50 routes and each route can support up to 10 upstream services. Configure what requests a route can receive by defining route rules and a route order. At least one route per API instance is required.

Before adding additional routes, enter an optional *Route label* for clarity.

Expand Down Expand Up @@ -139,7 +139,7 @@ For example, in a configuration in which route one has the `GET` method defined

You can use multiple upstream services in a single route to direct requests to similar services. For example, to test the performance of a new beta upstream service without sending all traffic to the new service, you can direct half of the traffic to a stable upstream service and half to the new upstream service.

Each API instance route can support up to 10 upstream services, but at least one upstream service is required for each route.
Each API instance route can support up to 50 upstream services, but at least one upstream service is required for each route.

What upstream service within the route each request is sent to is random and independent of any previous request. The upstream *Weight* defines the percentage chance of a request being sent to a particular upstream service.

Expand Down