Ideal Practices to Employ Resilient Browser Grid

The configurations you choose to create your grid plays a monumental part in its resilience when it comes to processing the required requests. To ensure that your grid is optimized, operational, and that it does not encounter the Browser Grid Failure alert, here are a few points to consider while creating your grid:

• Always allocate your grid with the necessary amount of nodes and browsers.

• It is not necessary to create your grid with the maximum configurations possible. If your request load does not demand such configuration, it is best to make a more conscious decision while configuring your grid. This ensures you save resources and curb your grid’s Idle state.

• While Browser Grid is an auto scaling component, you are required to configure the maximum number of nodes allotted to the grid and the maximum number of browsers allotted per node. For this reason, you are advised not to treat your grid as an open grid.

• It is always good practice to check if your grid can accept and process upcoming requests. This ensures that you always have available nodes and associated browsers available to process your requests. To make this check as seamless as possible, Catalyst SmartBrowz offers you the following API:

curl --location 'https://console.catalyst.zoho.com/browser360/v1/project/32940000000022062/browser-grid/2955000000009803/stats?data_to_fetch=live_stats' \
--header 'api-key: 010530e3e2868ac2418224ef9844fede33897db2e9a2d34f4291ed679d6140b2ed87356bd93cd15364485e769a389deb8917a6e06487ae37bfad19846bc3a0bd'

Executing this API will generate a response in the following manner:

{
    "status": "success",
    "data": {
        "session_queue_size": 0,
        "session_count": 0,
        "node_count": 0,
        "free_sessions": 10,
        "is_hub_alive": true
    }
}

In this response, we can see that the value for the key free_sessions is set as 10. Meaning that there are 10 browsers available to process your request.

If the value of free_sessions key is returned as 0, as shown below:

{
    "status": "success",
    "data": {
        "session_queue_size": 0,
        "session_count": 10,
        "node_count": 2,
        "free_sessions": 0,
        "is_hub_alive": true
    }
}

This means that there are no browsers left to process your request. It would be best to wait until the value of free_sessions is at least returned as 1 to process your requests.