4.10.11. eventlog mode

4.10.11.1. General information

Allows you to operate directly with the event log without connecting to the infobase.

4.10.11.2. export

Exports event log events to the console or the specified file in one of the supported formats. The command does not establish the connection to the infobase. So, it does not require the corresponding parameters.

Parameter

Description

--format=<format>

-f <format>

Determines the export format.

Possible values:

  • xml. Export in XML format.
  • json. Export in JSON format.

Default value: xml.

--skip-root

Allows you not to write the root XML element or the enclosing JSON object to the resulting file, in other words, to record each event as a separate entity of the selected format.

--from=<date>

Date of the export start in YYYY-MM-DDThh:mm:ss[.mmmmmm] format. In other words, the date to start the export from. If not specified, the export starts with the first available log event.

--to=<date>

The date of the export end in YYYY-MM-DDThh:mm:ss[.mmmmmm] format. In other words, the date till which the events must be exported. In not specified, the export ends with the last available log event.

--follow=<timeout> <ms>

-F <timeout> <ms>

The frequency of expecting new events for export in milliseconds. If the parameter name is specified without a value, the default value is used. If the parameter is not specified, new records are not expected.

Default value: 1,000 ms (milliseconds)

--out=<file>

-o <file>

Path to the export file.

If the parameter is not specified, the output is performed to the standard output stream (stdout).

<path to the log directory>

The unnamed parameter that specifies the path to the directory where the event log is stored.

4.10.11.3. model export

The command exports the event log event model as an XSD scheme with the target http://v8.1c.ru/eventLog namespace URI. The scheme version (the version attribute) corresponds to the 1C:Enterprise platform version. The command does not establish the connection to the infobase. So, it does not require the corresponding parameters.

Parameter

Description

<Path to the XSD scheme file>

The unnamed parameter that contains a full name of the file where the XSD scheme of the event log of the current version will be located.

Icon/Social/001 Icon/Social/006 Icon/Social/005 Icon/Social/004 Icon/Social/002