Skip to content

LUNA PLATFORM v.5.57.0#

LP changes

  • A "notification_policy" has been added to all tasks, which enables you to send notifications about changes in the status of tasks using the callback mechanism.

    Callbacks enable you to send data to a third-party system at the specified URL.

    The parameters from the new policy are similar to the parameters set in the corresponding handler policy ("authorization", "content_type", "timeout", etc.).

    You can also set up notifications for tasks in the schedule settings.

    If necessary, you can get information about the current status of the schedule or update it using the get task notification policy and replace task notification policy resources.

  • In the "create token" request, the ability has been added to specify the "account" > "view" permission to be able to get the data of the account to which the token itself was issued.

  • The "luna-handlers" client has been added for Tasks-lambda, which enables you to send user events to the Handlers service.

    See the detailed information about clients in the "Luna services clients" section of the development manual.

  • The ability to create custom monitoring points for Lambda task instances has been added to the Lambda service.

    See detailed information about monitoring in the "Lambda monitoring" section of the development manual.

  • An offline version of the website with online documentation has been added to the LUNA PLATFORM distribution package, replacing the previous HTML documents.

LP fixed errors

  • Now, when executing "generate events" and "generate stream events (beta)" requests with samples, bounding boxes will not be sent to the Remote SDK service, because they are not used.

  • The unused parameters raw_event_detections_limit, raw_event_arrays_limit and result_candidate_limit have been removed from the LUNA_REMOTE_SDK_LIMITS section. The only parameter left is received_images_limit.

  • Fixed the error where the Python Matcher Proxy service was using 100% CPU when the "indexed_matcher" plugin was enabled (when using LIM).

  • Fixed the error due to which, if the location query parameters were not filled in in the "generate events", "save event", "generate stream events (beta)" requests, the values "null" were still written to the Events database.

    Now, if no location parameters are specified, then no record will be created in the "location" table.