Log Storage (logstore)

Table of Contents

Description
Limitations
Parameters
Configuration example
See also

Description

Provides long-term storage of log files from all servers and nodes. Exists within each site independently of others.

Is the data provider for the log file access API. Uses disk storage, the limit of the size of the stored data is configurable in the options, after which the data is automatically cleaned up.

Reserved in Active-Passive mode. Not scalable.

Table 1. System Characteristics

Code	`logstore`
Mode of operation	`Service`
Backup mode	`Active-Passive`
Types of sites	`Any`
Layer	`Service`
Placement	`Internal`
Saving and restoring state on reboot	`Yes`
appendix	`era_logstore`
Own storage	`File system`

Limitations

In the absence of a role, there is no guaranteed storage of log files except that they are available for some time directly on the servers where they were created by roles.

Parameters

Description of columns in the table

Table 2. Parameters
Name	Type	Default	Description
`name`	`str`	required	Name. May consist of Latin letters and numbers, must begin with a letter.
`roletype`	`str`	required	Role Type. Possible values: `"logstore"`.
`iface`	`str`	required	The alias of the server network interface on which the roles will interact internally with each other.
`ext`	`json`	empty	Additional role options. Contains a json object or list.
`enabled`	`bool`	empty	Role activity flag. When set to false, the role does not participate in validation and is not started.
`group`	`int`	required	Group Number. Horizontal scaling within a site is not supported. All role instances on the site must have the same value. Integer from `1` to `9999999`.
`order`	`int`	required	The order of a role instance within a group. Defines in what order the flow in the mode will take place Active-Passive.
`storepath`	`str`	empty	A directory alias on the server to host and store log files. Default: `"/var/lib/era/_workdir/<NODE_NAME>/log/logstore"`. It is expected that a NAS that is accessible to all instances of the role will be connected as a catalog.
`storedays`	`int`	`2`	Number of days to store log files. When reached, outdated data is automatically deleted.
`storesize`	`int`	`100`	Maximum size of stored log files, in GB. When the oldest data is reached, it is automatically deleted.

Configuration example

The configuration is managed in an application available to master domain administrators. The application hides the full content of the configuration, but it is nevertheless accessible via the API.

The configuration contains a section to describe all instances of all roles. Parameters are defined for each specific role instance.

Example node

{
  "name": "logstore1",
  "roletype": "logstore",
  "iface": "eth0",

  "group": 11110,
  "order": 1,

  "storepath": "alias://paths/c"
}

Log Storage (logstore)

Description

Limitations

Parameters

Configuration example

See also