Monitoring¶
Data for monitoring¶
There are two types of events that are monitored: request (all requests) and error (failed requests only).
Every event is a point in the time series. The point is represented using the following data:
series name (e.g. requests and errors)
start request time (timestamp of the request start)
- The tag is an indexed data in storage. It is represented as a dictionary, where
keys - string tag names,
values - string, integer or float.
- The field is a non-indexed data in storage. It is represented as a dictionary, where
keys - string field names,
values - string, integer or float.
‘Requests’ series. Saving data for ‘Requests’ is triggered on every request. Each point contains data about the corresponding request (execution time and etc.).
tags
tag name
description
service
always “luna-licenses”
route
concatenation of a request method and a request resource (GET:/version)
status_code
HTTP status code of response
fields
fields
description
request_id
request ID
execution_time
request execution time
‘Errors’ series. Saving data for ‘Errors’ is triggered when a request fails. Each point contains error_code of LUNA error.
tags
tag name
description
service
always “luna-licenses”
route
concatenation of a request method and a request resource (GET:/version)
status_code
HTTP status code of response
error_code
LUNA error code
fields
fields
description
request_id
request ID
Every handler can add additional tags or fields.
‘Licensing’ series. Triggered on license check when starting the service as well as scheduled daily at midnight. Each point contains license check data.
tags
tag name
description
service
always “luna-licenses”
license_status
license status (“ok”, “warning”, “error”)
fields
fields
description
license_period_rest
number of days before the license expires
warnings
license warning messages
errors
license error messages
Database¶
Monitoring is implemented as data sending to an influx database. You can specify your database credentials in configuration file in section “monitoring”.