servicesLoad

URI

<serverStatus uri>/servicesload[.<format>]

Supported methods

Parent resource

Introduction

servicesLoad is the monitoring resource of server concurrent requests. Through this resource, you can monitor the concurrent requests of the current server, view the server loading, and know server running status.

Supported Methods:

GET: View the detailed info of the server concurrent requests.
HEAD: Check whether the servicesLoad resource exists. or to access the servicesLoad resource.

Supported output formats: rjson, json, html, xml.

Resource hierarchy

HTTP request methods

Implement the HTTP request on the following URI, where supermapiserver is the server name, with rjson being the output format.

http://supermapiserver:8090/iserver/manager/serverstatus/servicesload.rjson

GET request

View the detailed info of the server concurrent requests.

Response structure

The structure of the response returned by implementing the GET request on the servicesLoad resource is as follows:

Field	Type	Description
averageTime	int	The average response time of the server. The unit is second.
currentCount	int	The current concurrency.
historicalAccessCounts	int[]	Record the concurrency of server in 5 minutes.
interval	int	The time interval of service accessing statistics. Default is 1 second.

Response example

Implement the GET request on the servicesLoad resource http://localhost:8090/iserver/manager/serverstatus/servicesload.rjson. Return rjson results:

{ "averageTime": 0, "currentCount": 0, "historicalAccessCounts": [ 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 4, 4, 4, 0, 0, 0, 0, 0, 0, 0, 1, 0, 1, 0, 0, 1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 4, 0, 0, 1, 0, 0, 1, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1, 3, 1, 0, 4, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 4, 4, 4, 4, 0, 0, 0, 0, 1, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 4, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 4, 4, 0, 4, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0 ], "interval": 1 }

HEAD request

Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. The meta-information includes the media-type, content-encoding, transfer-encoding, content-length, etc.

HEAD request can be used to check if the servicesLoad resource exists, or if the servicesLoad resource can be accessed by clients. It can also determine if the servicesLoad resource supports an output format <format> if performed on a URI with .<format> included.

URI