Skip to content

LUNA PLATFORM v.5.5.0#

Changes

  • New resource "/handles/handler_id/events/raw" was added to API and Handlers services. Request fields are filled in when sending the request.

    The format of the generated event is similar to the format returned by the "handlers/handler_id/events" resource. The "event_id" and "url" fields are not specified when creating a request. They are returned in the response after the event is created.

    Notifications using web sockets are sent when events are created using this resource.

    The resource enables you to set your logic for filling in event fields, which is different from the logic using handlers. For example, when you want to extract descriptors only for a part of the detections and not for all the detections.

  • The resource "/ws" was added to the API service. Now web sockets configuration and Sender responses proxying are performed via the API service. This provides a single entry point to the LP through the API service and enables you to avoid sending requests directly to the Sender service.

    Configuring web sockets directly via Sender is still available. It can be used to reduce the load on the API service. In other cases, it is recommended to use the API service.

  • The new filters "event_id__gte" and "event_id__lt" are supported for receiving events using the "/events" resource.

    Using these filters, you can perform pagination that is:

    • Faster than the pagination by "page" and "page_size" parameters. It does not slow down with a large number of events.
    • More stable than pagination by "page" and "page_size" parameters. When events number is changed during the pagination process, it does not cause events to be lost or duplicated in the response.

  • The configuration reload mechanics have changed in Faces and Python Matcher services. Now, it's done mostly by restarting appropriate processes. The mechanism provides a more reliable update of service settings.

    Please note that requests made at the time of changing the settings may end with an error. The service may be unavailable for some time.

  • The values of "user_data" and "external_id" fields are now set to "" by default.

  • Cache sharing was added for the Python Matcher service when running multiple worker processes (workers) of the same service. Now each of the worker processes uses the same descriptors cache. Previously, when creating multiple workflows, each of them had a separate descriptors cache.

    This change can both speed up and slow down the service. If you need to ensure that the cache is stored in each of the Python Matcher processes, you should run each of the server instances separately.

  • InfluxDB OSS 2.x was supported for monitoring for all LP services. The section "InfluxDB OSS 2", which describes how to configure LP to work with the second version of the database, was added to "LP_Administrator_Manual". The database in the LP package was not updated to the new version.

Fixed errors

  • The face patch by "null" value of "event_id" field is supported in the Faces service in PATCH request to "/faces/{face_id}".

  • The problem with the delimiter character escaping in the report columns has been fixed in the Tasks service. If the delimiter character is found in the report column, it is now escaped.

  • Proper handling of the services communication errors that occurred during tasks processing was added to the Tasks service. For example, if the service is unavailable or there are problems with the connection, the corresponding errors are correctly displayed in the list of errors after the task execution.