Type 1c-xml

Expand all | Collapse all

The 1c-xml connector type is used to retrieve data from 1C registration logs. When the connector handles multi-line events, it converts them into single-line events. This type of connector is available for Linux Agents. Settings for a connector of the 1c-xml type are described in the following tables.

Basic settings tab

Setting

Description

Name

Unique name of the resource. Maximum length of the name: 128 Unicode characters.

Required setting.

Tenant

The name of the tenant that owns the resource.

Required setting.

Type

Connector type. You need to select 1c-xml.

Required setting.

URL

The full path to the directory with the files that you want to interact with, for example, /var/log/1c/logs/.

Limitations when using prefixes in file paths

Required setting.

Description

Description of the resource. Maximum length of the description: 4000 Unicode characters.

Advanced settings tab

Setting

Description

Character encoding

Character encoding. The default value is UTF-8.

Buffer size

Connector buffer size in bytes for accumulating events in the RAM of the server before sending sending them for further processing or storage. The value must be a positive integer. Default connector buffer size: 1,048,576 bytes (1 MB). Maximum connector buffer size: 67,108,864 bytes (64 MB).

Poll interval, ms

The interval, in milliseconds, at which the connector will reread files in the directory. The interval is applied only if there the file has no changes. For example, if the file is constantly being modified, and in the Poll interval, ms, you entered 5000, the files in the directory are reread constantly instead of every 5 seconds. If the file has no changes, files in the directory are reread every 5 seconds. Default value: 0 corresponding to 700 ms.

Debug

Resource logging. The toggle switch is turned off by default.

Connector operation diagram:

  1. The files containing 1C logs with the XML extension are searched within the specified directory. Logs are placed in the directory either manually or using an application written in the 1C language, for example, using the ВыгрузитьЖурналРегистрации() function. The connector only supports logs received this way. For more information on how to obtain 1C logs, see the official 1C documentation.
  2. Files are sorted by the last modification time in ascending order. All the files modified before the last read are discarded.

    Information about processed files is stored in the file /<collector working directory>/1c_xml_connector/state.ini and has the following format: "offset=<number>\ndev=<number>\ninode=<number>".

  3. Events are defined in each unread file.
  4. Events from the file are processed one by one. Multi-line events are converted to single-line events.

Connector limitations:

Page top