This section contains resources related to the Metric
. The endpoints in this section enables you to interact with the metrics data collected by the app. Through the API you can create as well as retrieve metrics data.
For more information please refer to Getting Started With Metrics
Here is the list of endpoints for Metrics
.
POST $BASE_URL/v1/metrics/{bucketId}
GET $BASE_URL/v1/metrics/{bucketId}
GET $BASE_URL/v1/metrics_overall/{bucketId}
Creates metric
entry. You can use Konso App to evaluate the metrics data. This is done using the endpoint:
POST $BASE_URL/v1/metrics/{bucketId}
The request object contains an instance of an object that is to be sent to create a new metric
entry. The object is transferred as part of the request's body.
The attributes refers to elements that makes up the request object:
POST $BASE_URL/v1/metrics/{bucketId}
{
"timeStamp":1621961380,
"tags":null,
"appName":"TestApp",
"correlationId":null,
"duration": 123,
"name": "GET v1/testapi",
"responseCode": 200,
"tags": ["test", "mvp"]
}
Returns entries matching the query filters and sorting. The following endpoint is used for this:
GET $BASE_URL/v1/metrics/{bucketId}
Lists and filters metrics entries. Entries are kept in our storage according to retention days setting.
The attributes refers to elements that makes up the filter parameters:
timeStamp
field, the value is in Unix epoch format.timeStamp
field, the value is in Unix epoch format.correlationId
specified.appName
specified.
GET $BASE_URL/v1/metrics/{bucketId}
?fromDate=1619636000
&toDate=1619637000
&name=GET
&correlationId=
&appName=testApp
&tags=tag1
&tags=tag2
&sort=2
&from=0
&to=100