General information about the Logi service
The Logs service is designed to collect, store and analyze logs of Servercore products that support logging:
Logs can be used to identify application and infrastructure bottlenecks and to quickly identify errors.
Records of log operations are stored in audit logs.
Principle of operation

Events that occur with the resource create an entry in the log file.Events in the log file can be combined logically into event streams. Event streams can be combined into groups.
An event is a record of application activity, such as an error.An event is a single record and consists of two parameters:
timestamp- The time of the event;message- event name.
Event streams (stream) - a sequence of events united by one source.The identifier of an event stream is its name.The name is an immutable parameter.
A log group is a set of event streams organized by storage parameters.The name is an immutable parameter of a log group.All log groups that are created by Servercore products start with the prefix s/ and contain the product abbreviation.For example, in the s/lbaas/my-loadbalancer record, the prefix is s/ and the product abbreviation is lbaas.
How to work with the Logi service
You can view and analyze logs:
- through the control panel;
- using the AWS CLI;
- or SDK client.
You can export logs to your repository using:
- of the Fluent Bit plug-in;
- Grafana Alloy' s agent.
You can also add logs to the Logs service with:
- of the Fluent Bit plug-in;
- of the Vector tool.
Logs in the service are stored for 30 days. You can change the logs storage period through the control panel.
To see the availability of the Logi service in the regions, see the Logi availability matrix.
Cost
Now the Logi service is free of charge. In the future the service will become paid - we will warn you about the change of conditions in advance.