Categories:
Aura File Manager metrics
List of metrics available in Aura File Manager
http_request_duration_seconds
This metric is intended to store the information related to all the incoming HTTP requests received by aura-file-manager.
It is stored as a Summary in Prometheus. So every sample, besides the defined labels, also includes its duration.
It measures the duration since the request lands in aura-file-manager until its HTTP response is returned, indicating to the client that Aura is processing the request to obtain a proper answer.
The metric allows measuring the behavior of the requests from any given endpoint:
- The number of requests during a time
- The average/min/max duration of these requests
Labels:
method: HTTP method used by the request being stored (GET,POST,PUT,DELETE, etc.)host: host and domain where the request is being sentpath: specific endpoint of the requeststatus_code: HTTP status code returned in the response
outgoing_request_duration_seconds
This metric is intended to store the processing time related to all the outgoing HTTP requests made by aura-file-manager.
It is stored as a Summary in Prometheus so every sample, besides the defined labels, also includes its duration.
This metric allows measuring the behavior of the requests to any given endpoint:
- The number of requests during a time
- The average/min/max duration of these requests
Labels:
method: HTTP method used by the request being stored (GET,POST,PUT,DELETE, etc.)host: host and domain where the request is being sentpath: specific endpoint of the requeststatus: HTTP status code returned in the response
outgoing_message_duration_seconds
This metric is intended to store the processing time of aura-bot requests arriving to aura-file-manager.
It is stored as a Summary in Prometheus, so every sample, besides the defined labels, also includes its duration.
As aura-file-manager is an asynchronous server, the processing of a request does not end when the HTTP response is returned, but when the proper answer for the user is sent back to the client callback. This metric measures the duration since the request lands in aura-file-manager until the last message of its answer is sent to the client callback.
Labels:
path: specific endpoint of the request.httpStatus: HTTP status code returned in the response.origin:aura-bot
incoming_message_duration_seconds
This metric is intended to store the processing time of aura-bot requests arriving to aura-file-manager.
It is stored as a Summary in Prometheus, so every sample, besides the defined labels, also includes its duration.
As aura-file-manage is an asynchronous server, the processing of a request does not end when the HTTP response is returned, but when the proper answer for the channel or skill is sent back to the client callback. This metric measures the duration from when the request arrives at aura-file-manager until it is processed to send the response.
Labels:
path: specific endpoint of the request.httpStatus: HTTP status code returned in the response.originStatus: status sent in the body of the response in the happening of an error.origin:aura-bot
aura_component_version
This metric is intended to store the number of aura-file-manager instances (pods) running each version of the code. It is stored as a Gauge in Prometheus.
Labels:
version: version field in thepackage.jsonfile included in the running docker container.component: name of the component that is writing the metric.
aura_server_unhandled_error
This metric is intended to store the number of unhandled errors happening in aura-file-manager.
It is stored as a Counter in Prometheus.
Labels:
error: exception message that forced the unhandled error.
aura_token_generate
This metric is intended to store the processing time of aura-file-manger to get/refresh kernel token.
It is stored as a Summary in Prometheus, so every sample, besides the defined labels, also includes its duration.
Labels:
path: specific endpoint of the request.httpStatus: HTTP status code returned in the response.originStatus: status sent by Direct Line in the body of the response in the happening of an error.origin: kernel client identifier
file_validation_duration_seconds
This metric is intended to store the validation time of a file.
It is stored as a Summary in Prometheus, so every sample, besides the defined labels, also includes its duration.
Labels:
path: specific endpoint of the request.code: OK when file is valid.origin: specific endpoint of the request.
services_status
This metric is intended to store the number of success or errored checks of modules of the server. It is stored as a Counter in Prometheus.
Labels:
moduleId: Id of the module.status: OK or ERROR