Quality of Service
The quality of service rules are used to lay down which of a service’s parameters are to be monitored and what requirements are to be made of the service.
- Performance (Response Time)
-
This field is for defining the maximum amount of time that a correct response to a request to a service can take.
The time is stated in milliseconds.
If the actual measured value is above this tolerance value, a notification is given. - Capacity (Number of simultaneous requests)
-
This field is for defining the number of simultaneous monitoring request (minimum of 1 and maximum of 30 requests on a monitoring trigger release).
We recommend to stay with "1" request as load test shall be executed temporarily and not continuously. - Availability
-
This defines the number of times that a service must be reachable or accessible on average. If this value (expressed in %) is not reached, the system sends a corresponding message.
- Status
-
- Service available
-
If any information is to be sent when HTTP errors occur, this notification rule needs to be activated.
- Service Exception
-
If the user wishes to be informed of service type specific exceptions, this parameter needs to be activated.
- Expectation
-
Choose those expectations that shall be tested for each service response of this monitoring job.
|
service type specific exceptions
A service type specific exception is either a response marked as exception due to the returned content type (http header value) or (in combination with a http status code of 200 (OK)) the existence of some content returned in the response body.
This can either be an OGC Service Exception or an Esri JSON response containing an |