Get http response code analytics as categorical data for rejections, errors, and failures.
/apiplatform/analytics/v1/categorical/responses/{statusFilter}
Returns analytics for rejections, errors, and failures as categorical data. Use the statusFilter
parameter to specify the type of measures returned.
This operation returns the intersection of all applied query parameter filters.
Any authenticated user can request this resource. The response contains data the requesting user is authorized to view based on their role and the resources they are issued grants to (APIs, applications, and gateways).
Request
-
statusFilter: string
Pattern:
(rejections|errors|failures)
Filters responses by status.rejections
shows HTTP responses of 4*.errors
shows HTTP responses of 5*.failures
combines rejections and errors.
-
apiIds(optional): array
Collection Format:
multi
Filter data by apiIds as repeated query parameters (like?apiIds=2&apiIds=3
) or a single-comma separated query parameter (like?apiIds=2,3
). -
appIds(optional): array
Collection Format:
multi
Filter data by appIds as repeated query parameters (like?appIds=2&appIds=3
) or a single comma separated query parameter (like?appIds=2,3
). -
gatewayIds(optional): array
Collection Format:
multi
Filter data by gatewayIds as repeated query parameters (like?gatewayIds=2&gatewayIds=3
) or a single-comma separated query parameter (like?gatewayIds=2,3
). -
groupBys(optional): array
Collection Format:
multi
Split the query results into groups based on repeated query parameters (like
?groupBys=gatewayIds&groupBys=nodeIds
) or a single comma separated query parameter (like?groupBys=gatewayIds,nodeIds
). Both of these examples display query results grouped by available gatewayIds and nodeIds.Grouping results by
gatewayIds
,nodeIds
,apiIds
, andappIds
is supported for all endpoints that support thegroupBy
query parameter. Additionally, grouping query results bypolicyVersion
,policyType
, andpolicyInstanceId
are supported for endpoints withpolicies
in the path. -
iterations(optional): array
Collection Format:
multi
Filter data by iterationIds as repeated query parameters (like?iterationIds=2&iterationIds=3
) or a single comma separated query parameter (like?iterationIds=2,3
). -
methods(optional): array
Collection Format:
multi
Filter data by methods as repeated query parameters (like?methods=GET&methods=PUT
) or a single comma separated query parameter (like?methods=GET,PUT
). -
nodeIds(optional): array
Collection Format:
multi
Filter data by nodeIds as repeated query parameters (like?nodeIds=2&appIds=3
) or a single comma separated query parameter (like?nodeIds=2,3
). -
planIds(optional): array
Collection Format:
multi
Filter data by planIds as repeated query parameters (like?planIds=2&planIds=3
) or a single comma separated query parameter (like?planIds=2,3
). -
serviceIds(optional): array
Collection Format:
multi
Filter data by serviceIds as repeated query parameters (like?serviceIds=2&serviceIds=3
) or a single comma separated query parameter (like?serviceIds=2,3
). -
timeEnd(optional): string
End time filter as ISO8601 offset date. Example:
2016-01-01T00:00:00-07:00
,2016-01-01T00:00:00Z
,2016-01-01T00:00:00
. The default value is no filtering. You must use this in conjunction with thetimeSetting=custom
query parameter. -
timeOffsetId(optional): string
ISO8601 time offset ID. Example:
Z
. This parameter overrides the time offset oftimeStart
ortimeEnd
. This parameter is also used when calculating the start of time groups. The value of this parameter defaults toZ
. (GMT).Note: Best effort is made to apply this parameter, but its accuracy may be limited by existing data granularity.
-
timeSetting(optional): string
Time setting mode. Defaults to
custom
. Valid values include:custom
,currentHour
,currentWeek
,currentMonth
,last15minutes
,last60minutes
,last24hours
,last7days
,last30days
,last365days
,january
,february
,march
,april
,may
,june
,july
,august
,september
,october
,november
,december
,year-2015
,year-2016
, etc. -
timeStart(optional): string
Start time filter as ISO8601 offset date. Example:
2016-01-01T00:00:00-07:00
,2016-01-01T00:00:00Z
,2016-01-01T00:00:00
. The default value is no filtering. You must use this in conjunction with thetimeSetting=custom
query parameter.
Response
- application/json
200 Response
object
-
count(optional):
integer(int32)
Response item count.
-
hasMore(optional):
boolean
Default Value:
false
Indicates if there are more results after the current batch. -
items:
array items
The actual response items.
-
limit(optional):
integer(int32)
Paging limit.
-
links(optional):
array links
HATEOAS links.
-
offset(optional):
integer(int32)
Paging offset.
-
states(optional):
array states
An optional list for API states. This is null by default.
-
time(optional):
object TimeMetadata
Metadata describing the time parameters used for the database query.
array
-
Array of:
object A response summary data item.
Contains http response code
array
-
Array of:
object GenericLink
HATEOAS generic link representation.
array
object
-
timeEnd(optional):
string
The calculated
timeEnd
used in the database query. -
timeOffsetId(optional):
string
The calculated
timeOffsetId
used in the database query. -
timeSetting(optional):
string
Value of the
timeSetting
query parameter. -
timeStart(optional):
string
The calculated
timeStart
used in the database query.
object
-
api_id(optional):
number
The API's Id.
-
api_name(optional):
string
The API's name.
-
measure:
number
Value of the measure.
-
response_code:
string
The http response code. Example:
HTTP 400
object
-
href:
string
Link reference string.
-
method(optional):
string
HTTP method used with the link.
-
rel:
string
Link relation string Value is either
canonical
or a specific string value. -
templated(optional):
string
Allowed Values:
[ "true", "false" ]
Indicates if the link has templated parts.
400 Response
401 Response
500 Response
Examples
The following example shows how to retrieve the total number of failed requests by submitting a GET request on the REST resource using cURL. For more information about cURL, see Use cURL
curl -i -X GET
-H "Authorization: Bearer access_token
https://example.com/apiplatform/analytics/v1/categorical/responses/failures
Example of Response Header
The following shows an example of the response header.
HTTP/1.1 200 OK Date: Sat, 30 Nov 2017 17:15:41 GMT Server: Oracle-Traffic-Director/12.2.1.0.0 Content-length: 171 Content-type: application/json X-oracle-dms-ecid: lN6_M1qdX00000000 X-oracle-dms-rid: 0:1 Via: 1.1 otd_opc Proxy-agent: Oracle-Traffic-Director/12.2.1.0.0 Transfer-encoding: chunked
Example of Response Body
The following example shows the contents of the response body in JSON format.
{ "count": 6, "time": { "timeEnd": "2017-12-31T00:00:00-07:00", "timeSetting": "custom", "timeGroupSize": 1, "timeStart": "2017-01-01T00:00:00-07:00", "timeOffsetId": "-07:00", "timeUnit": "MINUTE" }, "items": [ { "response_code": "HTTP 403", "measure": 162 }, { "response_code": "HTTP 401", "measure": 59 }, { "response_code": "HTTP 405", "measure": 53 }, { "response_code": "HTTP 400", "measure": 38 }, { "response_code": "HTTP 500", "measure": 27 }, { "response_code": "HTTP 404", "measure": 20 } ] }