Job properties

This tab simply lists all stored information about the job and it’s belonging service.

Service

Most relevant information of a service are:

  • internal service ID

  • the name of the service

  • URL of the service

  • the service type (using an internal naming scheme)

  • owner or creator of this service entry

  • the user group the owner belongs to

  • name of notification template

  • tolerated failures before a notification is sent

  • name of monitoring template

  • name of credential templates (if set)

Job

Relevant information of a job are:

  • internal job ID

  • name of the job

  • job category

  • creation and modification date

  • HTTP request content

  • protection level of job monitoring data
    public or private
    Private data is not publicly available for being requested via REST interface.

  • ArcSDE information: e.g. feature class, feature count, SQL where clause

Last executed request

Concerning the last executed request there are:

  • Timestamp of execution

  • HTTP Status Code

  • Content Type

  • Absolute number of requests

  • Evaluated state

  • Error message (if available)

Monitoring result in detail

Each monitoring observation consists of a set of attributes that describe the monitoring process in terms of its properties and evaluation status. This information can be transferred to Elastic to be analysed there.

Information about the evaluation status of a monitoring observation

field explanation type/values

io

Flag indicating whether the monitoring failed due to an IO error (infrastructural or other reasons for the failure to establish a connection).

format: true|false

Timeout

Flag indicating whether the monitoring ran into a timeout (server responded too slowly).

format: true|false

http

Flag indicating whether the endpoint is considered ‘faulty’ due to HTTP response codes.

format: true|false

unexpected

Flag indicating whether the monitoring has received an unexpected response (e.g. due to an expectation).

Format: true|false

unexpectedReason

Gives detailed textual information about an error

Format: String

noerror

Summarising flag from the fields io, timeout, http, unexpected.

format: true|false

dead

Summarising (inverse) flag from the fields io, timeout, http, unexpected.

Format: true|false

Example - Monitoring of https://some-server.example.com/arcgis/rest/services/myservice/MapServer

field value explanation

io

false

http connection to the server could be established.

timeout

false

http connection did not time out and did not break the set threshold.

http

false

http connection has responded correctly according to the interface API.

unexpected

true

An error occurred while examining the response that did not correspond to the expectation.

unexpectedReason

Evaluated cause: response is server side error message: {‘code’:499, ‘message’: ‘Token Required’, ‘details’:[]}

The http response from the server was syntactically correct, but the content of the response reports an error.

noerror

false

The evaluation of the response resulted in incorrect, unexpected behaviour.

dead

true

The evaluation of the response resulted in incorrect, unexpected behaviour.

Information about the monitoring observation

field explanation type/values

service.id

Id of the monitoring service

format: uuid

service.name

Name of the service

format: string

service.type

Type of the service

format: String

service.owner

Name of the user who created/edited this service

format: String

service.group

Associated group of the user

format: string

service.url

Base URL of the monitoring service

format: string

service.job.id

Id of the job of the service

format: uuid

service.job.name

Names of the monitoring job

format: string

service.job.method

http method used

format: String

service.job.query

Payload of the monitoring request

format: String

response.contenttype

http-content-type of the response

format: String

response.responsecode

http-status-code

format: int

response.length

byte length of the response

format: string

response.responseTime

Duration of the monitoring request

format: String

response.headers

List of the http headers of the response

format: List<key, value>

<more>

Further fields not documented here