GET checks/results?fromUtc={fromUtc}&toUtc={toUtc}&detail_level={detail_level}&fromMillisecondsUtc={fromMillisecondsUtc}&toMillisecondsUtc={toMillisecondsUtc}&include_tag_op={include_tag_op}
Gets check results between two dates.
URL Parameters
Name | Description |
---|---|
include_tag | (Optional) The 'include_tag' parameter defines which checks to include in the response, by filtering on the check 'tags' (see the Filtering by Tags section in Remarks for details). |
exclude_tag | (Optional) The 'exclude_tag' parameter defines which checks to exclude from the response, by filtering on the check 'tags' (see the Filtering by Tags section in Remarks for details). |
fromUtc | Timestamp in UTC format. Example: 2013-08-20T13:32:08. |
toUtc | Timestamp in UTC format. Example: 2013-08-20T13:32:08. |
detail_level | Result detalization level. Allowed values: 0, 1. Default value: 0. |
fromMillisecondsUtc | Timestamp represented as a UNIX Epoch timestamp (millisecs after 1970). Type: numeric. Example: 1376980667000. |
toMillisecondsUtc | Timestamp represented as a UNIX Epoch timestamp (millisecs after 1970). Type: numeric. Example: 1376980667000. |
include_tag_op | AND/OR mode for including tags. Allowed values: 'or', 'and'. Default value: 'or'. |
Remarks
The default context for the route is the user context. To enable customer context (if it's allowed for the user) use the request query parameter customer_context=1.Filtering by Tags
Checks can be filtered on the check 'tags', using tag 'key' and/or 'value'. Tilde '~' is used to indicate values. Multiple values are separated with semicolon ';'. Example: Environment~Dev;Prod (Key: 'Environment', Values: 'Dev' and 'Prod').You can provide the tag key only (all checks with that key) or only the value (all checks with that value in any key). Examples: Environment (key); ~Dev (value).
You can use the tag or key ID, by adding a '.' (period) before the ID. Examples: .4568~Prod (Tag key ID:'4568', value 'Prod'); Environment~.6985 (Tag key: 'Environment', value ID:'6985').
Responses
Request example
curl --request GET "http://api-wpm2.apicasystem.com/v3/checks/results?include_tag=Environment~Dev;Prod&exclude_tag=Environment~Beta&detail_level=0&fromMillisecondsUtc=1376980667000&toMillisecondsUtc=1376980667000&auth_ticket=C471ADC4-19B4-4219-BBF4-671A97EC653E"
Response body model examples and descriptions
When result detalization level is 0
[ { "check_id": 12345, "timestamp_utc": "2023-06-08T18:19:28", "severity": "E", "value": 4637, "unit": "ms" }, { "check_id": 12345, "timestamp_utc": "2023-06-08T18:19:28", "severity": "I", "value": 1234, "unit": "byte" }, { "check_id": 12345, "timestamp_utc": "2023-06-08T18:19:28", "severity": "F", "value": 4637, "unit": "ms" } ]
When result detalization level is 1
[ { "message": "1 url, 148/6797 sent/received bytes.", "identifier": "e046a88b-922d-4de5-aefd-0f09b6ba04c1", "attempts": 1, "result_code": 200, "check_id": 12345, "timestamp_utc": "2023-06-08T18:19:28", "severity": "E", "value": 4637, "unit": "ms" }, { "message": "1 url, 148/6797 sent/received bytes.", "identifier": "13ca717d-00b2-4e9e-baf5-2cc22d4b66e7", "attempts": 2, "result_code": 200, "check_id": 12345, "timestamp_utc": "2023-06-08T18:19:28", "severity": "W", "value": 4637, "unit": "ms" }, { "message": "1 step, 1 page, 1 url, 142/0 sent/received bytes.", "identifier": "f6832395-48f9-4f04-a1fa-765cf0bc5ab0", "attempts": 2, "result_code": 200, "check_id": 12345, "timestamp_utc": "2023-06-08T18:19:28", "severity": "F", "value": 1234, "unit": "ms" } ]
Name | Type | Description |
---|---|---|
message | String |
The result message. |
identifier | Guid |
The result identifier. |
attempts | Integer |
The number of attempts. |
result_code | Integer |
The code of result. |
check_id | Integer |
The numeric identifier of the check. |
timestamp_utc | DateTime |
Result timestamp. |
severity | String |
Result severity. |
value | Integer |
Result value. |
unit | String |
Result unit of measure. |