Skip to main content

General information about the Logs service

The Logs service is designed for collecting, storing, and analyzing logs from Servercore products that support logging:

Logs can be used to identify bottlenecks in application and infrastructure performance and to quickly detect errors.

Records of log operations are saved in audit logs.

How it works

Events related to a resource create a record in a log file. Events in a log file can be combined logically into event streams. Event streams can be grouped.

An event (event) is a record of application activity, for example, the occurrence of an error. An event is a single record consisting of two parameters:

  • timestamp – event time;
  • message – event name.

Event streams (stream) are a sequence of events (event) originating from a single source. The identifier of an event stream is its name. The name is an immutable parameter.

A log group (group) is a set of event streams combined based on storage parameters. The name is an immutable parameter of a log group. All log groups created by Servercore products start with the s/ prefix and contain the product abbreviation. For example, in the record s/lbaas/my-loadbalancer, the prefix is s/, and the product abbreviation is lbaas.

How to work with the Logs service

You can view and analyze logs:

You can export logs to your own storage using:

You can also add logs to the Logs service using:

Logs are stored in the service for 30 days. You can change the log retention period via the Control Panel.

You can check the availability of the Logs service in the regions in the Logs availability matrix.

Pricing

Currently, the Logs service is provided free of charge. In the future, the service will become paid—we will notify you of any changes to the terms in advance.