v.5.130.0#

Changes

The allowed email formats have been extended for account creation.

Addresses with subdomains are now supported when creating an account. For example, addresses like "username@sub.domain.com," which were previously not validated, are now accepted. However, the restriction remains: the domain portion of the address cannot begin or end with a period.

For more information, see the section "Accounts, tokens and authorization types".
The internal licensing library has been updated to version 1.13.0.
The handling of custom license features has been updated.

The "get license" request response from the Licenses service for custom features now returns information about the expiration date and availability of the function.
Support for group_by aggregation for nested event.* fields has been added to the general events statistics request.

You can now group data by any nested event fields, for example, event.user_info.temperature to analyze the distribution of user temperature readings.

Example request:
```
{
"targets": [
    {"column": "event_id", "aggregator": "count"},
    {"column": "event.user_info.temperature", "aggregator": "group_by"}
]
}
```
Example response:
```
{
"fields": [
    "event.user_info.temperature, aggregator 'group_by'",
    "event_id, aggregator 'count'"
],
"stats": [
    ["36.6", 45],
    ["37.0", 23],
    ["37.5", 34]
]
}
```
Here, "36.6", "37.0", and "37.5" are temperature values, and 45, 23, and 34 are the number of events for each group.

Note: When using the group_by aggregator, the values of the grouped fields are always converted to a string data type.

See the request "get statistics on general events".
A new callback type, luna-kafka, is now available for video analytics. It allows sending event data to Apache Kafka. This expands integration capabilities with systems that use Kafka for stream processing.

The following parameters are used to configure the luna-kafka callback:
- servers - one or more Kafka server addresses
- topic - topic for sending messages
- protocol - security protocol
- username, password - username and password for SASL authentication
For more information about types, see "Send and save analytic results".
The example of using Agent-Lambda with analytics for detecting people in suits has been updated in the Lambda service developer guide.

The example now explicitly specifies the folder name (suit_analytics) for storing custom analytics files and provides a list of required files. See Agent lambda examples for details.
The ability to manage lambda activity through the new parameter eternal has been added for Kubernetes cluster resource optimization.

Now, when creating, updating, and importing, you can use the eternal parameter. It accepts the following values:
- 0 (default value): lambda will be automatically disabled if not used for the time specified in the setting LUNA_LAMBDA_INACTIVE_LAMBDA_CLEAR_INTERVAL.
- 1: lambda will remain active until manually disabled.
For lambdas with eternal = 0, a new last_usage parameter is available, which displays the time the lambda was last active. This value is updated based on the last_activity metric, which the lambda sends each time it is used. See get lambda and get lambdas.

Important: To automatically disable inactive lambdas, you must enable the LUNA_LAMBDA_METRICS_SETTINGS setting.

For more information, see last activity section of the developer guide.
A new parameter group LUNA_LAMBDA_INACTIVE_LAMBDA_CLEAR_INTERVAL has been added to automatically disable inactive lambdas.

This allows Kubernetes cluster resources to be freed up when by disabling lambdas that haven't been used for a specified period of time.

Periodic disabling of inactive lambdas is configured using the parameters in the LUNA_LAMBDA_INACTIVE_LAMBDA_CLEAR_INTERVAL group:
- interval — specifies the inactivity interval. The default value is 3.
- interval_type — specifies the interval type (weeks, days, hours, minutes). The default value is days.
- check_interval — specifies the frequency of checking for lambda activity (in seconds). The default value is 30.
- active — enables/disables automatic disabling of inactive lambdas. The default value is true.
When the active parameter is enabled with the default settings, the system checks for lambda activity every 30 seconds and disables those that haven't been used for more than 3 days.

For more information, see Switch lambda.

Fixed errors

Fixed a segmentation fault error that could previously cause some videos to crash. The decoder's timestamp processing logic has been improved.
The MediaMTX media server, which is used as part of the Streams Retranslator service to convert video streams to HLS format, has been updated. This has improved the stability of HLS retransmission.
Fixed a caching error in the Licenses service that could affect the correct display of features status.