ICMP monitors
Fetch detailed availability metrics and aggregated or non-aggregated ICMP Monitor metrics across custom time ranges. For example, you can get the p99 and p95 of latency metrics together with the packet loss percentage for any time range. Rate-limiting is applied to this endpoint, you can send 30 requests / 60 seconds at most.
Path parameters
Query parameters
Custom start time of reporting window in unix timestamp format. Setting a custom "from" timestamp overrides the use of any "quickRange".
Custom start time of reporting window in unix timestamp format. Setting a custom "from" timestamp overrides the use of any "quickRange".
Custom end time of reporting window in unix timestamp format. Setting a custom "to" timestamp overrides the use of any "quickRange".
Custom end time of reporting window in unix timestamp format. Setting a custom "to" timestamp overrides the use of any "quickRange".
Preset reporting windows are used for quickly generating report on commonly used windows. Can be overridden by using a custom "to" and "from" timestamp.
Preset reporting windows are used for quickly generating report on commonly used windows. Can be overridden by using a custom "to" and "from" timestamp.
The time interval to use for aggregating metrics in minutes. For example, five minutes is 5, 24 hours is 1440.
The time interval to use for aggregating metrics in minutes. For example, five minutes is 5, 24 hours is 1440.
Filter based on whether a check result was either failing or passing
Filter based on whether a check result was either failing or passing
[ "failure" ]
Determines how the series data is grouped. Note that grouped queries are a bit more expensive and might take longer.
Determines how the series data is grouped. Note that grouped queries are a bit more expensive and might take longer.
Available metrics for ICMP Monitors. You can pass multiple metrics as a comma separated string.
Available metrics for ICMP Monitors. You can pass multiple metrics as a comma separated string.
Limit the number of results
Limit the number of results
Page number
Page number
Headers
Your Checkly account ID, you can find it at https://app.checklyhq.com/settings/account/general
Your Checkly account ID, you can find it at https://app.checklyhq.com/settings/account/general
Response
Success
Changes
Changed in 1 of the 4 revisions of this API.6569
- ▲
for the
pathrequest parameterid, the minLength was increased from0to1request-parameter-min-length-increased
- ▲
for the
headerrequest parameterx-checkly-account, the type/format was changed fromstring/tostring/uuidrequest-parameter-type-changed
- ▲
for the
pathrequest parameterid, the type/format was changed fromstring/tostring/uuidrequest-parameter-type-changed
- ▲
the
fromresponse's property type/format changed fromstring/datetostring/date-timefor status200response-property-type-changed
- ▲
the
series/items/response's property type/format changed fromstring/toobject/for status200response-property-type-changed
- ▲
the
toresponse's property type/format changed fromstring/datetostring/date-timefor status200response-property-type-changed
- ●
for the
queryrequest parameterpage, the exclusiveMinimum was set totruerequest-parameter-exclusive-min-set
- ●
for the
queryrequest parameterpage, the min was set to0.00request-parameter-min-set
- ●
removed the optional property
attributesfrom the response with the401statusresponse-optional-property-removed
- ●
removed the optional property
attributesfrom the response with the429statusresponse-optional-property-removed
- ●
removed the optional property
metadata/stringfrom the response with the200statusresponse-optional-property-removed
- ○
added the non-success response with the status
400response-non-success-status-added
- ○
added the non-success response with the status
404response-non-success-status-added
- ○
added the optional property
metadata/availabilityto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvgto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvg_avgto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvg_maxto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvg_medianto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvg_minto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvg_p50to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvg_p90to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvg_p95to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvg_p99to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvg_stddevto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyAvg_sumto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMaxto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMax_avgto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMax_maxto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMax_medianto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMax_minto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMax_p50to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMax_p90to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMax_p95to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMax_p99to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMax_stddevto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMax_sumto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMinto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMin_avgto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMin_maxto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMin_medianto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMin_minto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMin_p50to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMin_p90to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMin_p95to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMin_p99to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMin_stddevto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyMin_sumto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDevto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDev_avgto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDev_maxto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDev_medianto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDev_minto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDev_p50to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDev_p90to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDev_p95to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDev_p99to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDev_stddevto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/latencyStdDev_sumto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLossto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLoss_avgto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLoss_maxto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLoss_medianto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLoss_minto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLoss_p50to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLoss_p90to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLoss_p95to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLoss_p99to the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLoss_stddevto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/packetLoss_sumto the response with the200statusresponse-optional-property-added
- ○
added the optional property
metadata/retriesto the response with the200statusresponse-optional-property-added
- ○
the response property
messagebecame required for the status401response-property-became-required
- ○
the response property
messagebecame required for the status403response-property-became-required
- ○
the response property
messagebecame required for the status429response-property-became-required
- ○
removed the
401.00enum value from thestatusCoderesponse property for the response status401response-property-enum-value-removed
- ○
removed the
403.00enum value from thestatusCoderesponse property for the response status403response-property-enum-value-removed
- ○
removed the
429.00enum value from thestatusCoderesponse property for the response status429response-property-enum-value-removed
- ○
removed the
Forbiddenenum value from theerrorresponse property for the response status403response-property-enum-value-removed
- ○
removed the
Too Many Requestsenum value from theerrorresponse property for the response status429response-property-enum-value-removed
- ○
removed the
Unauthorizedenum value from theerrorresponse property for the response status401response-property-enum-value-removed
- ○
added the required property
series/items/datato the response with the200statusresponse-required-property-added
This revision also has 566 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲