Monitoring

Monitoring is implemented as sending data to the influx database.

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 (requests or errors)

• timestamp of the request start

• tags

• fields

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.

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-api”
  account_id	account id or none
  route	concatenation of a request method and a request resource (POST:/extractor)
  status_code	http status code of response

• fields

  fields	description
  request_id	request id
  execution_time	request execution time

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-api”
  account_id	account ID or none
  route	concatenation of a request method and a request resource (POST:/extractor)
  status_code	http status code of response
  error_code	LUNA PLATFRORM error code

• fields

  fields	description
  request_id	request id

Every handler can add additional tags or fields. For example, handler of resource /handlers/{handlerId}/events adds tag handler_id.

For a resource “/detector”, “/extractor”, “/handlers/{handler_id}/events” there are additional fields:

• fields

  fields	description
  task_execution_time	sdk task execution time
  results_queue_transport_time	transport time by results queue
  detector_queue_transport_time	transport time by detector queue
  extractor_queue_transport_time	transport time by extractor queue
  warp_attributes_estimator_queue_transport_time	transport time by warp attributes queue
  detector_stage_time	detector stage time
  extractor_stage_time	extractor stage time
  warp_estimator_stage_time	warp estimator stage time
  faces_detect_time	face detect time
  descriptors_extract_time	descriptors extract time
  basic_attributes_extract_time	basic attributes extract time
  gaze_direction_estimation_time	gaze direction estimation time
  head_pose_estimation_time	head pose execution time
  eyes_attributes_estimation_time	eyes attributes execution time
  ags_estimation_time	ags estimation time
  quality_estimation_time	quality estimation time
  emotions_estimation_time	emotions estimation time
  mouth_attributes_estimation_time	mouth attributes estimation time
  save_samples_time	save samples to image store time
  save_face_attributes_time	save face attributes to luna-faces time
  load_samples_time	load samples from image-store time
  load_images_for_processing_time	load images for processing time

Database

You can set your database credentials in configuration file in section “monitoring”.

Plugins

You can create your plugin for sending monitoring data. See plugins

class luna_api.plugins.plugins.request_monitoring_example_plugin.RequestMonitoringClass

Example plugin sends a request data for monitoring to third-party source. Only one instance of this class exist during the program execution.

async flushPointToMonitoring(points, logger)

Callback for sending a request monitoring data.

Parameters:

• points – point for monitoring which corresponding the request

• logger – logger

Return type:

None

Classes