Skip to content

LUNA PLATFORM v.5.51.6#

Changes#

  • Support for ECS logging format has been added.

    To use the new format, you need to set the value "ecs" in the "format" setting of the "LUNA_service_LOGGER" section.

    When using the "ecs" value, the following fields will be used:

    • "http.response.status_code" - contains the HTTP response status code (e.g., 200, 404, 500, etc.).
    • "http.response.execution_time" - contains information about the time taken to execute the request and receive the response.
    • "http.request.method" - contains the HTTP request method (GET, POST, PUT, etc.).
    • "url.path" - contains the path in the request's URL.
    • "error.code" - contains the error code if the request results in an error.

  • The ability to create a schedule for Reporter task has been added.

  • A new parameter "base_image" has been added to the requests "create lambda" and "update lambda", allowing you to explicitly specify the name of the base image for building a Docker container.

    Previously, it was possible to use only two images that were previously transferred to the user registry - "lpa-lambda-base" (basic functionality) and "lpa-lambda-base-fsdk" (basic functionality and functionality for using FSDK).

    A custom lambda image is intended for complex lambdas that lack the capabilities implemented in the "lpa-lambda-base" and "lpa-lambda-base-fsdk" base images (for example, multi-stage creation of a Docker container or the inclusion of large libraries or data in a Docker container).

    For a custom lambda image, the following conditions must be met:

    • the image must be based on the "lpa-lambda-base" or lpa-lambda-base-fsdk images"
    • the image must not remove or change any installed dependencies (python3, gcc, etc.)
    • the image must be in the same registry as other base lambda images.

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

    For example, you can send data about how long it took to upload or process images.

    For more information, see the "Monitoring" section of the Lambda service development manual.

  • The logic of processing bounding boxes in the generate stream events (beta) request has been updated.

    Now the source body image (the "body" parameter) is not required to save the bounding boxes of the face/body (field "events" > "detections" > "samples" > "face"/"body" > "detection" > "rect").

  • In the LUNA PLATFORM license activation manual, a section "Vendor change" has been added with instructions on changing the HASP vendor to Guardant and vice versa.

Fixed errors#

  • Removed the unused parameter "FETCH_EXTERNAL_IMAGE_TIMEOUTS" from the API service settings.

  • Fixed the "Internal server error" error occurring when performing a "get system info" request when the required measurements were missing in the Influx database.