Type 1c-log

The 1c-log connector type is used to retrieve data from 1C technology logs. Strings delimiter: \n. The connector accepts only the first line from a multi-line event record. This type of connector is available for Linux Agents. Settings for a connector of the 1c-log 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-log. 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 Prefixes that cannot be used when specifying paths to files: /* /bin /boot /dev /etc /home /lib /lib64 /proc /root /run /sys /tmp /usr/* /usr/bin/ /usr/local/* /usr/local/sbin/ /usr/local/bin/ /usr/sbin/ /usr/lib/ /usr/lib64/ /var/* /var/lib/ /var/run/ /opt/kaspersky/kuma/ Files are available at the following paths: /opt/kaspersky/kuma/clickhouse/logs/ /opt/kaspersky/kuma/mongodb/log/ /opt/kaspersky/kuma/victoria-metrics/log/ 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. All 1C technology log files are searched. Log file requirements:
   • Files with the LOG extension are created in the log directory (/var/log/1c/logs/ by default) within a subdirectory for each process.

     Example of a supported 1C technology log structure

     

   • Events are logged to a file for an hour; after that, the next log file is created.
   • The file names have the following format: <YY><MM><DD><HH>.log. For example, 22111418.log is a file created in 2022, in the 11th month, on the 14th at 18:00.
   • Each event starts with the event time in the following format: <mm>:<ss>.<microseconds>-<duration in microseconds>.
2. The processed files are discarded. Information about processed files is stored in the file /<collector working directory>/1c_log_connector/state.json.
3. Processing of the new events starts, and the event time is converted to the RFC3339 format.
4. The next file in the queue is processed.

Connector limitations:

• Installation of a collector with a 1c-log connector is not supported in a Windows operating system. To set up transfer of 1C log files for processing by the KUMA collector:
  1. On the Windows server, grant read access over the network to the folder with the 1C log files.
  2. On the Linux server, mount the shared folder with the 1C log files on the Windows server (see the list of supported operating systems).
  3. On the Linux server, install the collector that you want to process 1C log files from the mounted shared folder.
• Only the first line from a multi-line event record is processed.
• The normalizer processes only the following types of events:
  • ADMIN
  • ATTN
  • CALL
  • CLSTR
  • CONN
  • DBMSSQL
  • DBMSSQLCONN
  • DBV8DBENG
  • EXCP
  • EXCPCNTX
  • HASP
  • LEAKS
  • LIC
  • MEM
  • PROC
  • SCALL
  • SCOM
  • SDBL
  • SESN
  • SINTEG
  • SRVC
  • TLOCK
  • TTIMEOUT
  • VRSREQUEST
  • VRSRESPONSE

Page top