Metrics in Prometheus Exposition Format wrapped as Json array of strings.
Property | Type | Constraints | Description |
---|---|---|---|
limit |
Integer | Page size of result page | |
metrics |
[String] | Metrics in Prometheus Exposition Format. A single metric is represented by a single line. They have a name, labels (dimensions), a value and a time-stamp. Example: OCAPI request: total time metric:
The individual elements of a metric line are the metric name, metric dimensions
(denoted by label / value pairs in curly braces), the actual metric value (in
milliseconds or in operations / second for metrics ending in
name The metric name will have both path segments and parameters separated by ‘_’. Path segments in the metric name are in lower-case whereas path parameters are formatted in camel-case. method the HTTP method of the OCAPI request, one of version the version of the OCAPI request, e.g. v20.8 path1 .. pathN The path segments (not including the path-parameters) of the OCAPI request, from
the example above, the path segments will be mapped to labels as:
breakdown Sub-timings of the request, in particular:
status
quantile
serviceId (only for metrics where breakdown = thirdParty) the |
|
offset |
Integer | Offset of result page | |
total |
Integer | Total number of metrics |