This section contains resources that are related to the Log (log entry)
. The endpoints in this section enables you to interact with the log data collected by the app. Through the API you can create as well as retrieve log data.
For more information please refer to Getting Started With Logs
Here is the list of endpoints for Logs
.
POST $BASE_URL/v1/logs/{bucketId}
GET $BASE_URL/v1/logs/{bucketId}
Creates a Log
entry for further reporting. You can use Konso App to analyze and evaluate the log data. The endpoint below is used to create an entry:
POST $BASE_URL/v1/logs/{bucketId}
The request object contains an instance of an object that is to be sent to create a new Log
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/logs/{bucketId}
{
"message":"Error Message",
"timeStamp":"1619636875",
"correlationId":null,
"appName":"testApp",
"level": "error",
"env": "production",
"machineName": "my-pc",
"eventId": 101010,
"tags": ["test", "mvp"]
}
Returns entries matching the log query filters. The endpoint below is used to get log entries:
GET $BASE_URL/v1/logs/{bucketId}
Lists and filters log 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 Unix epoch.timeStamp
field, the value is Unix epoch.correlationId
specified.appName
specified.
GET $BASE_URL/v1/logs/{bucketId}
?fromDate=1619636000
&toDate=1619637000
&message=login
&correlationId=
&appName=testApp
&tags=tag1
&tags=tag2
&from=0
&to=100
&sort=2