From 961d59b72b416710ae3639ed714a3a8a96e217ac Mon Sep 17 00:00:00 2001 From: Alejandro Dominguez Date: Fri, 18 Mar 2022 12:53:53 +0100 Subject: [PATCH] docs: document the support of maxSessions in selenium grid scaler Signed-off-by: Alejandro Dominguez --- content/docs/2.7/scalers/selenium-grid-scaler.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/2.7/scalers/selenium-grid-scaler.md b/content/docs/2.7/scalers/selenium-grid-scaler.md index 71c30020f..238f06df7 100644 --- a/content/docs/2.7/scalers/selenium-grid-scaler.md +++ b/content/docs/2.7/scalers/selenium-grid-scaler.md @@ -9,9 +9,9 @@ go_file = "selenium_grid_scaler" ### Trigger Specification -This specification describes the `selenium-grid` trigger that scales browser nodes based on number of requests in session queue. +This specification describes the `selenium-grid` trigger that scales browser nodes based on number of requests in session queue and the max sessions per grid. -The scaler creates one browser node per pending request in session queue. You will have to create one trigger per browser capability that you would like to support in your Selenium Grid. +The scaler creates one browser node per pending request in session queue, divided by the max amount of sessions that can run in parallel. You will have to create one trigger per browser capability that you would like to support in your Selenium Grid. The below is an example trigger configuration for chrome node.