3.22.2. Configuration file structure

   

3.22.2.1. General description

Configuration file root item is the <config> item that defines the technological log settings. It may contain several <log> items, one <dump> item, one <leaks> item, one <plansql> item, one <defaultlog> item, one or several <system> items:

<config…>
<log…>…</log>
<log…>…</log>
<log…>…</log>
<dump … />
<leaks>…</leaks>
<mem/>
<plansql/>
<dbmslocks/>
<ftextupd …/>
<query …/>
<inputbystring …/>
<scriptcircrefs/>
<system … />
<system … />
<system … />
<defaultlog … />
</config>

These items have the following functions:

1. <log> item defines the technological log directory and its composition (see article#_ref300244308
2. <log>).
3. <dump> item defines unexpected shutdown dumps saving directory.
4. <leaks> item sets tracking for memory leaks (see article <leaks>) that may be caused by the configuration code errors. Memory leak tracking decreases the performance slightly.
5. <mem> item is intended to control memory usage (see article <mem>).
6. <plansql> item is intended to manage collection of the query plans generated during DMBS operations. The query plans themselves are contained in <planSQLText> property of DBMS-related events.
7. <dbmslocks> item is intended to manage collection of the DBMS lock data.
8. <ftextupd> item is intended to manage collection of data on the full-text search index update processes.
9. <query> item manages writing technological log entries on the fields that illegally contain NULL when executing external data source queries (see article <query>).
10. <inputbystring> item is intended to manage collection of data on the usage of input by string functionality.
11. <scriptcircrefs> item manages the functionality of circular references data tracking during 1C:Enterprise language command execution (see article <scriptcircrefs>).
12. <defaultlog> item defines the default technological log directory and lifetime (see article <defaultlog>).
13. <system> item defines system event generation settings (see article <system>).

Items are divided into several groups:

1. Items that control generation of a specific event. Such items include <dump>, <leaks>, <mem>, <plansql>, <ftextupd>, <system>, <query>, <scriptcircrefs>, <inputbystring>. However, if the technological log configuration file does not contain the required item, the system does not generate the respective event. In other words, if, for example, recording of the memory used is not enabled by <mem> item, filtering by MEM event will not affect the technological log contents, as this event is simply not generated.
2. Items that control filtering of the existing technological log data. Such items include <event> and <property>. You can use these items to filter the events generated by the system. These items can only reduce the amount of data recorded to technological log files.
3. Items that control placement of data files for technological log and dumps. Such items include <log>, <defaultlog>, <dump>.

3.22.2.2. <log>

<log> item defines the technological log directory and the filtering criteria used to store the previously generated events in the technological log.

The item attributes:

Name of the directory to save the technological log to.

A number of hours at which information stored the technology log will be removed.

The <log> item may contain<event> and <property> items that determine the conditions for recording each event and event property to the log.

If this item contains no <event> items, no events are recorded to the log.

3.22.2.3. <event>

Sequence of <event> items defines the condition for saving the event to the log. Only the events meeting the condition are saved to the log. In other words, if the condition defined by the <event> items sequence is True, the event is written to the log. The event is added to the log if it meets all the conditions within at least one of the <event> items. The conditions within the <event> item are combined using logical AND, and the <event> items are combined using logical OR.

These items are used to define conditions:

• eq. Equal.
• ne. Not equal.
• gt. Greater than.
• ge. Greater than or equal.
• lt. Less than.
• le. Less than or equal.
• like. Matches the mask.

Each of these items, except like item, defines a simple comparison of the event parameter value (property attribute defines the parameter name) to the value attribute value.

Example:

<event>
<eq property="name" value="proc"/>
</event>

In this case, events referred to the group named PROC will be recorded to the technological log.

The following event names are available:

Event name	Description
ADDIN	Operations with add-ins.
ADMIN	Control actions of 1C:Enterprise server cluster administrator.
ATTN	Records of 1C:Enterprise cluster status monitoring subsystem.
CALL	Incoming remote calls (call target side remote calls).
CLSTR	Execution of actions changing the server cluster operation.
CONFLOADFROMFILES	Execution of configuration restoring from the files.
CONN	Establishment or termination of client connection to a server.
DB2	Execution of DB2 SQL operators.
DBCOPIES	Operations with database copies.
DBMSSQL	Execution of Microsoft SQL Server SQL operators.
DBMSSQLCONN	The event is generated when the 1C:Enterprise server connects Microsoft SQL Server DBMS for the first time when the provider for database is selected.
DBORACLE	Execution of Oracle Database SQL operators.
DBPOSTGRS	Execution of PostgreSQL SQL operators.
DBV8DBENG	Execution of file-based DBMS SQL operators.
DHIST	Execution of data history update.
EDS	Operations with external data sources.
EVENTLOG	Registration of events related to generation of the event log index.
EXCP	1C:Enterprise applications exceptions, which are not handled in standard way and may cause the unexpected shutdown of the server process or client process connected to it.
EXCPCNTX	Events that have started but have not finished, when the abnormal situation occurred.
FTEXTCheck	Occurs when verifying the full-text search index files.
FTEXTUpd	Occurs during the full-text search index files update.
FTS	Registers v2 full-text search events that can be useful for administrators to assess the situation and develop responses.
HASP	The event logs a single dongle access.
InputByString	Occurs when the platform processes the input by string.
LEAKS	Events related to the memory leak, which may be caused by the configuration code errors.
LIC	Events related to retrieval and release of the licenses (both software and HASP), retrieval of licenses for the base versions, regular monitoring of matching the actual hardware and list of hardware, recorded in the license.
MAILPARSEERR	Event generated if an error occurred when parsing the mail message.
MEM	Events related to the increase of memory, used by the server processes (ragent, rmngr, rphost).
PROC	Events related to the entire process and affecting the process performance. For example: startup, termination, abnormal termination, and so on.
QERR	Events related to detection of query compilation errors or database records or fields level restrictions.
SCALL	Outgoing remote calls (call source side outgoing calls).
SCOM	Events of creation or deletion of server contents, usually related to the infobase.
SDBL	Events related to querying the 1C:Enterprise database model.
SDGC	The event occurs when the session data clearing mechanism is triggered.
SESN	Actions related to the session. For example: session start, session end, and so on.
SINTEG	Operations with an external integration service. The event occurs when sending and starting to receive messages.
SRVC	Events related to startup, stopping and notifications of the server cluster services.
SYSTEM	Platform component-related system events intended for analysis by 1C technical experts. Such events are only configured based on the explicit instructions from the technical support and only for a time required to reproduce a specific problem. Otherwise, such configuration may cause the significant increase of log file size and decrease the application performance.
TDEADLOCK	Deadlock in the managed mode is detected.
TLOCK	Transaction lock control in managed mode.
TTIMEOUT	Transaction lock timeout.
VRSCACHE	Server call cache operations.
VRSREQUEST	Request to server for a resource.
VRSRESPONSE	Server response.
WINCERT	Errors related to certificate verification using Windows functionality. Such events may help the specialists to investigate the causes of incorrect certificate verification.

It is also worth noting that events from PROC, SCOM, EXCP, CONN and ADMIN groups are relatively rare and contain small amount of data, while logging of events from SDBL, DB2, DBMSSQL, DBPOSTGRS, DBORACLE groups may cause the significant increase of technological log.

like item determines whether the technological log property matches a mask. The mask is a sequence of characters, some of which represent themselves, and some are templates intended to describe a group of characters.

For example, <like property="SDBL" value="%reference%"/> item means checking if the SDBL property value of the technological log event matches the mask %reference%.

Templates include:

• % – 0 or more arbitrary characters.
• _. 1 arbitrary character.
• [...]. One of the listed characters, where [...] may contain any characters and ranges similar to c-C, where c is the range starting character, C is the range ending character.
• [^...]. Any single character, except for the characters specified in square brackets [].
• \. Prefix character. It is ignored, meaning that the next character is a regular character that does not represent a template.
• Any other characters. Regular characters representing themselves. Simple characters comparison is case-insensitive.

Sample templates:

• template. String with specific text. In this case comparison using like does not differ from comparison using eq. Case-insensitive.
• %reference%. String, containing reference context in arbitrary position. Case-insensitive.
• reference%. String, containing reference context in the beginning. Case-insensitive.
• %reference. String, containing reference context in the end. Case-insensitive.
• %[a-z]. String ending with a lowercase Latin letter.
• %[^a-z]%. String containing at least one character different from a lowercase Latin letter.

Example:

<log location="c:\logs" history="1">
<event>
<eq property="name" value="proc"/>
</event>
<event>
<eq property="name" value="scom"/>
</event>
<event>
<eq property="name" value="conn"/>
</event>
<event>
<eq property="name" value="excp"/>
</event>
<event>
<eq property="name" value="dbmssql"/>
</event>
</log>

This example illustrates how the events from PROC, SCOM, CONN, EXCP and DBMSSQL groups are recorded in the technological log.

3.22.2.4. <property>

3.22.2.4.1. General information

<property> item defines the conditions for an event whose name is the name attribute value to be recorded in a log, provided that the event itself is recorded in the technological log. The conditions are set by the nested <event> items following the event rules.

If there is no <property> item with a specific name, the respective property is not recorded. If <property> item contains no nested <event> items, the property defined by it is recorded for all the events containing this property and recorded in the log. If the <property> item contains nested <event> items, the property will be recorded only for events that meet the condition (if the event itself is recorded in the log and has this property).

<property name="all"> </property> item includes the records of all the event properties to the log.

The <log> item below defines the following events to be recorded in the log: process, server context, connection, exceptions, and execution of SQL operators. However, the SQL operator text will only be saved to the log if its execution took longer than a second. The log is located in C:\logs directory and is stored for 1 hour.

Example:

<log location="c:\logs" history="1">
<event>
<eq property="name" value="proc"/>
</event>
<event>
<eq property="name" value="scom"/>
</event>
<event>
<eq property="name" value="conn"/>
</event>
<event>
<eq property="name" value="excp"/>
</event>
<event>
<eq property="name" value="dbmssql"/>
</event>
<property name="sql">
<event>
<eq property="name" value="mssql"/>
 <gt property="duration" value="10000"/>
</event>
</property>
</log>

Each event has a set of properties. Each property has a name. Several properties with the same names are allowed per event. Property names may be used for events and properties filtering. Comparison of names is case-insensitive. Empty condition in <property> item means that the property is always displayed.

3.22.2.4.2. List of properties

The basic event properties, which may be required for configuration file setup and technological log browsing, are given below:

Property name	Description
Action	Text description of the operation performed while restoring the configuration from files (for CONFLOADFROMFILES event).
Admin	Cluster or central server administrator name.
agentURL	URL of the current process of 1C:Enterprise server agent (production server URL).
All	Enables recording of all the log events.
ApplicationExt	Specification of the functionality assignment rule (for CLSTR event).
AvMem	Value of Available memory indicator when writing to technological log (for FTEXTUPD event).
BackgroundJobCreated	Determines whether full-text search index generation was performed as a background process (true) or not (false) (for FTEXTUpd event).
Body	Size of request/response body in bytes (for VRSREQUEST, VRSRESPONSE events).
Calls	Number of client application calls to server application made over TCP.
Certificate	Verified certificate description (for WINCERT event). Includes the following certificate fields: subject, issuer, and serial number.
Class	Name of class that generated the event (for SYSTEM event).
Classes	Add-in object names separated by "|" (for the ADDIN event).
Cluster	Server cluster main port.
cn	Number of dynamic memory fragments occupied by the process when writing MEM event.
cnd	Change in the number of dynamic memory fragments occupied by the process since the last MEM event.
Component	Name of the platform component that generated the event (for SYSTEM event).
Connection	Infobase connection number.
Connections	Number of connections for which working processes are missing (for the CLSTR event).
ConnLimit	Maximum number of connections per working process (for CLSTR event).
Context	Execution context.
CopyBytes	The overall size of copied values applicable to garbage collection (for SDGC event).
CpuTime	CPU usage time, in microseconds, required to index a portion of the event log file (for the EVENTLOG event).
Crashed	Equals 1 if the operation is completed with an error (for the ADDIN event).
Database	Used database path (for DB2, DBMSSQL, DBORACLE, DBPOSTGRS, DBDA, EXCP, SDBL events). For the client-server version, the database name is generated as a NameServer\BaseName, for the file version, the full path to the 1Cv8.1CD file is displayed.
DBConnID	External data source DBMS connection ID (for EDS event).
DBConnStr	External data source connection string (for EDS event).
DBCopy	Name of the database copy used (for DB2, DBMSSQL, DBORACLE, DBPOSTGRS, DBDA, EXCP, SDBL events). If access to the copy does not occur, this property is not written.
Dbms	Dbms the name of the DBMS used to execute the operation that led to the generation of this technological log (for EDS, DB2, DBMSSQL, DBORACLE, DBPOSTGRS, DBDA, EXCP, SDBL events). Can take the following values: DB2. IBM DB2 (except DBDA event). DBMSSQL. Microsoft SQL Server. DBOracle. Oracle Database. DBPOSTGRS. PostgreSQL. DBV8DBEng. File DBMS (for EXCP, SDBL events only). DBMySQL. MySQL (for EDS event only). DBMSSQLServerAnalysisServices. SQL Server Analysis Services (only for EDS event). DBOracleEssbase. Oracle Essbase (only for EDS event). DBIBMInfosphereWarehouse. IBM Infosphere Warehouse (only for EDS event). DBDA. Data Accelerator (for DB2, DBMSSQL, DBORACLE, DBPOSTGRS, DBDA, EXCP, SDBL events). DBUnkn. Other DBMS (only for EDS event).
Dbpid	String representing the ID of 1C:Enterprise server connection to the database server in database terms (for DBMSSQL, DBPOSTGRS, DB2, DBORACLE events).
DBUsr	External data source DBMS username (for EDS event).
DeadlockConnectionIntersections	List of transaction pairs forming the deadlock (for TDEADLOCK event).
Descr	Software exception description. See article Descr property description for the list of values.
description	Text explaining the action being performed (for DHIST event).
DstAddr	Assigned working process address (for the CLSTR event).
DstId	UUID of the assigned working process (for the CLSTR event).
DstPid	System ID of the assigned working process (for the CLSTR event).
DstSrv	Assigned working process name (for the CLSTR event).
dumpError	Description of an error occurred during the process of dumping.
DumpFile	Name of the dump file.
Duration	Duration of an event in hundreds of microseconds.
Durationus	Duration of an event in microseconds.
Err	Console message type: 0 – information, 1 – error.
errorCode	Error code returned by the handling method of working with the Windows API certificates (for the WINCERT event).
ErrorDescr	Contains an exception text upon error (for the ADDIN event).
Event	Contains a name of the action performed by a cluster of servers (for CLSTR event) and determines the presence of other properties in current event. See article Event property description for description of available values.
Exception	Name of the software exception.
ExcessDurationSec	Memory excess duration in seconds (for the ATTN event).
ExcessStartTime	Timestamp when the memory excess was registered (for the ATTN event).
ExtSrvcUrl	External integration service address (for the SINTEG event).
ExtSrvcUsr	Name of the external integration service user (for the SINTEG event).
FailedJobsCount	Number of the background indexing processes that finished with errors (for FTEXTUpd event).
File	Name of a file in which an event was generated (for SYSTEM event) or in which a problem was detected in the course of checking the index of a full-text search (for FTEXTCHECK event).
FileName	Name of a file with the event log index to be generated (for the EVENTLOG event).
Files	List of files formatted as "file name ... file size" in the directory in which an action is occurring (for FTEXTUPD event). A property is generated only if the logfiles attribute of the ftextupd element is set to value True (see article <ftextupd>).
FilesCount	Number of files in the directory in which an action is occurring (for FTEXTUPD event). A property is generated only if the logfiles attribute of the ftextupd element is set to value True (see article <ftextupd>).
FilesSize	The overall size of storage in bytes (for SDGC event).
FilesTotalSize	Number of files in the directory in which an action is occurring (for FTEXTUPD event). A property is generated only if the logfiles attribute of the ftextupd element is set to value True (see article <ftextupd>).
FillRefsPresent	If a property does exist, it means that the cache of links from the user list of values is used instead of a full-text data search (for the INPUTBYSTRING event).
FindByString	Name of a configuration object for which input by string is performed.
findTicks	Time spent while searching the database, in ms (for INPUTBYSTRING event).
Finish	Reason for ending the process.
fixedState	New timestamp in the state file till which indexing was performed, in ISO 8601 format. For the FTS event.
Folder	Directory in which the action is occurring (for FTEXTUPD event). Could be a temporary directory or a directory for files with an index of a full-text search. A property is generated only if the logfiles attribute of the ftextupd element is set to value True (see article <ftextupd>).
FreeMemory	Available RAM of a computer with a server cluster (for the ATTN event).
ftextResultCount	Number of links found in the course of a full-text search (for INPUTBYSTRING event).
ftextSearchCount	Number of calls to the full-text search (for INPUTBYSTRING event).
ftextTicks	Time spent on full-text search, in ms (for INPUTBYSTRING event).
fullKey	Full key to search for a record in the search engine. For the FTS event.
Func	Name of the action. See article The property values of Func for the list of values.
Headers	HTTP request / response headers (for VRSREQUEST, VRSRESPONSE events).
Host	Computer name.
hResultOLEDB, hResultNC2005, hResultNC2008, hResult2012	Contains a hexadecimal return code when trying to connect through a one or another provider (OLE DB, SQL Server Native Client versions 2005, 2008, 2012). If the attempt to connect through provider was not performed, a property will be unavailable. Attempts to connect begin with the provider corresponding to the most current version of Microsoft SQL Server and then all providers are to be sorted out in order to lower the version. After a successful connection is completed, all further attempts to establish a connection through other providers are stopped.
IB	Name of an infobase in the client/server mode.
IBLimit	A determined maximum number of infobases per each working process (for CLSTR event).
IName	Name of the interface being transmitted, whose method is called remotely (for SCALL and CALL events).
InBytes	Amount of data read from hard drive during a call (in bytes).
Info	Crash info (for FTEXTCheck event). Number of attempts to establish a connection with the process completed with an error (for the ATTN event).
Infobases	Number of infobases for which working processes are missing (for the CLSTR event).
InstanceID	Storage UUID (for the SDGC event). Integer.
JobCanceledByLoadLimit	Flag indicating that the background indexing process has been canceled because a load limit for the working process has been reached (for FTEXTUpd event).
jobId	Indexing background job ID. For the FTS event.
Level	Event severity level (for SYSTEM and CONFLOADFROMFILES events). Possible event values are provided in the description of element <system> from the file logcfg.xml containing configuration of technology log (see article <system>). Message severity level. Possible values: ERROR WARNING INFO For the FTS event.
Line	String number in the file where SYSTEM event was generated.
Location	Contains add-in location or object ID for the ADDIN event.
LockDuration	Duration of storage lock in the period when garbage collector is in operation, in milliseconds (for SDGC event).
Locks	A list of managed transaction locks (for TLOCK event).
logFrom	Initial timestamp of the data chunk in the event log in ISO 8601 format. For the FTS event.
logTo	Final timestamp of the data chunk in the event log in ISO 8601 format. For the FTS event.
MDX	Text of MDX request to OLAP system.
MDX	Text of the executed request to OLAP system (only for EDS event).
Memory	Amount of memory in bytes used but not released, per server call.
MemoryLimits	Set memory limits (for the ATTN event).
MemoryPeak	A peak value of memory in bytes used but not released, per server call.
MemoryUsed	The maximum size of dynamic memory used during the call (for FTEXTUpd event).
Message	Message that is specified when calling an add-in event (for the ADDIN event).
MessageUid	A unique ID of mail message, a parsing of which resulted in an error. Value is equal to the property ID of the object InternetMailMessage.
metaDataId	Table metadata object UUID. It can be used to search for an object in a configuration exported to XML. For the FTS event.
Method	HTTP method of accessing the resource (for VRSREQUEST, VRSRESPONSE events) or a method of InternetMail object during which an error in parsing the mail message (for MAILPARSEERR event) occurred, or a name of the method being called which is different from call method (for CALL event or current action of garbage collector (for SDGC event). For the event MAILPARSEERR can take the values: GET. A problem was detected during execution of the Select () method. GETHEADERS. A problem was detected during execution of the GetHeaders () method. SETRAW. A problem was detected during execution of the SetInitialData ()method. For the CALL event, this property contains a number of the called method of the interface; wherein the ID of the called interface is specified in the Interface property. For SDGC event can accept the following values: Compact. Compaction of stored data. Analyze. Storage state analysis. No compaction required.
MethodName	Name of an add-in method whose call is displayed in this technological log record (for the ADDIN event).
MinDataId	Minimum ID of the indexed data in the chunk passed from the cluster manager into working process and back (for FTEXTUpd event).
MName	Name of the remotely called method (for SCALL and CALL events).
MyVer	Current server state version (for CLSTR event).
Name	Event name.
NeedResync	The server data synchronization is required (for CLSTR event whose Event property is equal to current version older).
Nmb	Session number (for SESN event).
NParams	Number of parameters of SQL operator for the file version of infobase (for DBV8DBENG event). Parameters whose amount has been specified in a given property, are being used to transfer long binary data.
Obsolete	Number and UUIDs of obsolete working processes (for the CLSTR event).
OSException	Description of the operating system exception.
OSThread	Number of a thread indexing the event log file (for the EVENTLOG event).
OutBytes	Amount of data (in bytes) recorded on hard drive during a call.
p:processName	Name of server context which usually matches the name of infobase.
PacketCount	Actual number of packets written to the index file during current file processing (for the EVENTLOG event).
parallelism	Number of background jobs that can be started at the same time. Affects indexing speed and resource usage of CPU and RAM. For the FTS event.
Phrase	Text phrase corresponding to the status code (for VRSRESPONSE events).
PID	Process ID of the operating system. Operating system process ID of the main cluster manager (for the ATTN event).
planSQLText	Query plan contained in Sql property (for DBV8DBENG, DBMSSQL, DBPOSTGRS, DB2, DBORACLE, EDS events).
Port	Number of the main network port of a process.
Process	Name of an application module, as interpreted by the operating system (the file name of the booting application's module).
ProcessId	Main cluster manager UUID (for the ATTN event).
ProcessName	Name of a process.
procURL	Server process address of 1C:Enterprise system to which the event relates.
Query	Text of query in the 1C:Enterprise language during the execution of which NULL value was detected in the field for which such a value is invalid (for QERR event).
QueryFileds	List of query fields in which NULL values have been detected (for QERR event).
Reason	Reason for non-availability of working process (for CLSTR event).
recordCount	Number of records before or after indexing in a specific data chunk. For the FTS event.
recordRef	Internal reference to the table record. For the FTS event.
Ref	Infobase name.
Regions	Names of spaces of the controlled transactional locks (for TLOCK event).
Registered	Number and UUIDs of new working processes (for the CLSTR event).
reindexCount	Number of tables sent for reindexing. For the FTS event.
Released	Number and UUIDs of backup working processes that became the main processes (for the CLSTR event).
Report	Name of the metadata object of the report being executed (being performed in the background job).
Request	Connection request ID (for the CLSTR event).
res	Describes the action performed by the licensing system (for LIC event).
Result	Result of checking full-text search index files (for the FTEXTCheck event): 1. No errors. 0. There are errors. Result of performing an operation with an add-in (for the ADDIN event). 0. Successful completion. 1. Completed with an error.
RetExcp	An exception occurred during execution of the server call and transmitted to client as a result of call (for CALL events).
Rows	A number of database records retrieved.
RowsAffected	A number of the modified database records.
RunAs	A process start mode (application or service).
SafeLimit	Safe memory usage per call (for the ATTN event).
Sdbl	A query text in the 1C:Enterprise language of the database model.
SearchByMask	If set to TRUE or "1", a database search without the full-text search results is performed (for INPUTBYSTRING event).
Separation	A division (for FTEXTCHECKevent) is enabled or not.
SepId	An index of the split area if split is enabled (for FTEXTCHECK event).
ServerComputerName	Working server name.
ServerId	Server UUID (for the ATTN event).
ServiceName	The name of a server cluster (for CLSTR event).
SessionID	A session number assigned to the current thread. If no session has been assigned to the current thread, a property is not added.
skippedRecords	Number of records skipped due to indexing errors. For the FTS event.
Source	Source specified when calling an event from an add-in (for the ADDIN event).
Sql	SQL statement text.
SrcAddr	Preferred working process address (for the CLSTR event).
SrcId	UUID of the preferred working process (for the CLSTR event).
SrcPid	System ID of the preferred working process (for the CLSTR event).
srcProcessName	It is recorded when the overall data from infobase is retrieved by working process. A value of the property ProcessName is the name of the overall data at the time of its retrieval. A value of the property srcProcessName is the name of the overall data from infobase at the time of its formation.
SrcURL	A preferred address of production server (for CLSTR event).
SrcVer	A version of server cluster status (for CLSTR event) received.
SrvcName	Name of the integration service metadata object for which connection to the external integration service is executed (for the SINTEG event).
State	A start or end of the update operation on the full-text search index (for FTEXTUPD event) has been committed.
Status	HTTP status code (for VRSRESPONSE events).
SyncPort	An auxiliary network port number of a process.
Sz	An amount of dynamic memory (in bytes) taken up by process at the time MEM event is executed.
Szd	Change in the amount of dynamic memory (in bytes) taken up by process since the previous MEM event execution.
t:applicationName	ID of a client application.
t:clientID	ID of TCP connection with a customer.
t:computerName	Name of a client computer.
t:connectID	ID of connection with infobase.
tableCode	Table code. It is displayed when the table name is unavailable. For the FTS event.
tableCount	Number of tables before or after indexing in a specific data chunk. For the FTS event.
tableName	Table name. For the FTS event.
tableRef	Human-readable reference to the configuration object. For the FTS event.
Text	Text entered when entering by string (for INPUTBYSTRING event).
Time	Time of writing to the technology log (for FTEXTUPD event). Operation execution time. It is displayed either in milliseconds or as a time interval in the ddd.hh:mm:ss.fff format. For the FTS event.
tooManyResults	If set to TRUE or "1", there are too many links in the index matching the request; a full-text search is not used (for INPUTBYSTRING event).
TotalJobsCount	A number of background processes generated during indexing (for FTEXTUpd event).
TotalMemory	RAM of a computer with a server cluster (for the ATTN event).
totalRecords	Total (accumulated) number of records in a data chunk. For the FTS event.
Trans	ID of the transaction activity at the start of an event: 0. A transaction has not been opened. 1. A transaction has been opened.
Txt	Text of informational message. See article Txt property description for the list of values.
Type	Name of a type for which an object is created or deleted (for the ADDIN event).
URI	A resource being accessed (for VRSREQUEST, VRSRESPONSE events).
Url	Main cluster manager URL (for the ATTN event).
UsedSize	Size of used storage space in bytes (for SDGC events).
Usr	The infobase user name (if no users have been defined in the infobase, this property will be set to DefUser). A property value is taken from the assigned session.
Val	A value, the meaning of which depends on a value of Func.
WaitConnections	A list of the connections being collided with on the managed transactional locks (for TLOCK and TTIMEOUT events).
Word	A word, if defined (for FTEXTCheck event).

By using the properties of the item <property>, the execution context can be recorded in the technology log. The execution context can be: 1C:Enterprise language context or interface context. The embedded 1C:Enterprise language context is a list of the embedded language statements. It contains:

• Module name.
• Module line number.
• Text presentation of an item from the 1C:Enterprise language call list of the corresponding module line.

The interface context includes:

• Full form name.
• Type of the active form item.
• Name of the active form item.
• Name of the command bar button (if clicked).
• Action performed by the form item.

For example, a context of the embedded 1C:Enterprise language in the technological log might look like this:

Document.GoodsReceipt:23: Records.ProductAccounting.Write();
ApplicationModule:18:CheckIdleHandlerConnection(True);
ApplicationModule:230:IfnpGetDefaultValue(mainCurrentUser,"UseReminders");
GeneralModule.npUserSettings:481:Selection=Query.Execute().Select();

The interface context in the technological log file might look like this:

{Document.Document1.ListForm}/{TabularField: DocumentList}/{RefreshDisplay} {Document.Document1.Form.DocumentForm}/{CommandBar: MainFormActions}/{MainFormActionsOK} {Document.Document1.Form.DocumentForm}/{Button: Button1}/{Click}

To enable a context record, it is needed to record the item <property name = "Context"> or the item <property name = "all"> among the property filters.

If you need to record the events SDBL (SDBL-queries) and DBMSSQL (SQL statements to the MS SQL Server DBMS) with the execution context, the content of the technological log configuration file will look like this:

<config xmlns="http://v8.1c.ru/v8/tech-log">
<log location="c:\v8\logs" history="1">
<event>
<eq property="name" value="sdbl"/>
</event>
<event>
<eq property="name" value="dbmssql"/>
</event>
<property name="context">
</property>
</log>
</config>

To record the SDBL (SDBL queries) and DBMSSQL events (SQL statements to the MS SQL Server DBMS) without the execution context, the technological log configuration file must be filled in, as follows:

<config xmlns="http://v8.1c.ru/v8/tech-log">
<log location="c:\v8\logs" history="1">
<event>
<eq property="name" value="sdbl"/>
</event>
<event>
<eq property="name" value="dbmssql"/>
</event>
</log>
</config>

To record the SDBL (SDBL queries) and DBMSSQL events (SQL statements to the MS SQL Server DBMS) without execution context but with all other properties, the configuration file should contain:

<config xmlns="http://v8.1c.ru/v8/tech-log">
<log location="c:\v8\logs" history="1">
<event>
<eq property="name" value="sdbl"/>
</event>
<event>
<eq property="name" value="dbmssql"/>
</event>
<property name="all">
</property>
<property name="context">
<eq property="name" value=""/>
</property>
</log>
</config>

In order to record the SDBL events (SDBL queries) with the execution context and DBMSSQL (SQL statements to the MS SQL Server DBMS) without the execution context, the content of the configuration file should look like this:

<config xmlns="http://v8.1c.ru/v8/tech-log">
<log location="c:\v8\logs" history="1">
<event>
<eq property="name" value="sdbl "/>
</event>
<event>
<eq property="name" value="dbmssql"/>
</event>
<property name="context">
<event>
<eq property="name" value="sdbl"/>
</event>
</property>
</log>
</config>

If item <property name = "Context"> is present, it means that context information will be recorded for the technological log events if the conditions specified in this item are met. After that, information about execution context in current process will be added to each technological log event, and after the event, an instant event carrying information about the execution context of client process will be added.

Technological log may contain messages related to the exceptions linked to the lock manager. For that, a configuration file should look like this:

<config xmlns="http://v8.1c.ru/v8/tech-log">
<log location="c:\v8\logs" history="7">
<event>
<eq property="name" value="excp"/>
</event>
<event>
<eq property="name" value="tlock"/>
<gt property="duration" value="100000"/>
</event>
<property name="all"/>
<property name="context">
<event>
<eq property="name" value=""/>
</event>
</property>
</log>
<dump location="c:\v8\dumps" create="1" type="2"/>
</config>

In the above example, all exceptions associated with locks will be recorded (in particular, DEADLOCK are connections interlocks and TIMEOUT is expiration of a predetermined time, wherein in both cases, a number of the connection that caused this exception) and the periods of waiting exceeding 10 seconds will be included in the message text about the exception. Wherein information about all properties except Context will be recorded.

3.22.2.4.3. The property values of Func

Func property can take the following values:

VALUE	Description
AcceptPartialIndex	Accept partial indexes.
addCopy	Adding the database copy (for DBCOPIES event).
agentAuthenticate	Central server administrator authentication.
applyServiceAssociationRules	Application of the requirements related to functionality assignment.
Attach	An assignment of the session to a connection (an event of SESN kind is being output at the moment of unassignment to a connection of the session). A duration indicates how long the session was assigned to a connection. Add-in attachment (for the ADDIN event) and the action result.
authenticateInfoBaseAdmin	Authentication of the infobase administrator.
authenticateSrvrUser	Authentication of a cluster administrator in working process.
authenticateSrvrUser	Authentication of a cluster user in working server.
authenticateStarter	Authentication of a remote central server.
beginTransaction	A transaction starts (an event of SDBL kind is displayed in the log at the moment when the said transaction starts and has no duration).
Busy	A session has already been assigned to a connection (SESN event is being output when an attempt is made to assign a session that has already been assigned to the connection). Has no duration
Call	Add-in object method call (for the ADDIN event) and the action result.
changeInfoBaseParams	Change in infobase parameters: server licensing, external session management, mandatory external session management, security profile, security profile of the secure mode.
changeLocale	Change in the national database settings.
CheckIndexes	Verification of the full-text search indexes is being executed.
commitTransaction	Transaction commitment.
Connect	Connection with an external data source or external integration service.
continueFillTable	Resumption of initial filling in database copy table (for DBCOPIES event).
copyMoveFile	Copying / moving a fragment of an application between database table entries.
Crash	Add-in host process crash (for the ADDIN event).
createFile	Create a file.
createInfoBase	Create an infobase.
CreateObject	Add-in object creation (for the ADDIN event) and the action result.
deleteFile	Delete a file.
deserializeTable	Recovery of data pertained to the database table from a file.
disconnect	Disconnection from the external data source.
dropInfoBase	Delete an infobase.
erase<X>	Delete an entry from the security profile where <X> is: Virtual directory. SecurityProfileVirtualDirectory. External module.SecurityProfileExternalModule. Add-in. SecurityProfileAddIn. Internet resource. SecurityProfileInternetResource. Application. SecurityProfileApplication.
eraseAgentUser	Delete a central server administrator.
eraseIBRegistry	Delete a central server cluster.
eraseIBRegistry	Delete a cluster.
eraseRegServer	Delete a working server.
eraseRegServer	Delete a working server.
eraseRegUser	Delete cluster administrators.
eraseRegUser	Delete a cluster user.
eraseSeance	Delete a session.
eraseSecurityProfile	Delete a security profile.
eraseServerProcess	Delete a working process.
eraseServiceAssociationRule	Delete a functionality assignment requirement.
ExternalEvent	External event generated by an add-in (for the ADDIN event).
fillTable	Execution of initial filling in database copy table (for DBCOPIES event).
fillTableBlocksKeyFields	Fill in the database copy table by key values (for DBCOPIES event).
fillTableBlocksKeyFieldsTableParts	Fill in the database copy table containing reference data (for DBCOPIES event).
fillTableOne	Fill in the database copy table with one query (for DBCOPIES event).
finish	The end of session (an event of SESN kind is logged at the time of a session being ended and the event duration is equal to a duration of the entire session).
Finish indexing file	Finish writing an index file for the completed event log file (for the EVENTLOG event).
FtextMngrIndexChanges	A full-text search index is being updated in the file mode of infobase.
FtextMngrRHostIndexChanges	A full-text search index is being updated in the client-server mode of infobase.
get<X>	Read the full list of security profiles or their entries, where <X> is: Virtual directory. SecurityProfileVirtualDirectory. External module.SecurityProfileExternalModule. Add-in. SecurityProfileAddIn. Internet resource. SecurityProfileInternetResource. Application. SecurityProfileApplication.
getAgentUsers	Read data on the agent administrators.
getClusterManagers	Read the list and parameters of cluster managers.
getConnections	Read the list of connections.
GetDataForIndexing	Get the list of modified objects to be included in the full-text search index
getIBRegistry	Read the list and parameters of clusters.
getInfoBaseParams	Read the infobase parameters.
getInfoBases	Read a list of infobases.
getObjectLocks	Read a list of cluster object locks.
GetProperty	Add-in object property receipt (for the ADDIN event) and the action result.
getRegUsers	Read data on the cluster administrators.
getSeances	Read a list of sessions.
getServerProcesses	Read a list and parameters of working processes.
getServiceAssociationRules	Read a list of functionality assignment rules.
getServicesDistribution	Read data on the distribution of services between cluster managers.
getServicesInfo	Read information about available cluster services
getTransactionSplitter	Get a totals separator.
holdConnection	Hold connection.
IndexObjects	Perform indexing of a portion of objects.
initialize	Initialize a licensing subsystem (for LIC events only).
insertAgentUser	Creating a central server administrator.
insertAgentUser	Add a central server user.
insertIBRegistry	Add a cluster to the central server.
insertIBRegistry	Create a cluster.
insertRecords	Add a record to the database table.
insertRegServer	Add a working server.
insertRegServer	Add a working server.
insertRegUser	Add a cluster administrator.
insertRegUser	Add a cluster user.
insertServerProcess	Add a working process.
insertServerProcess	Add a working process.
isProperLocale	Validate database local settings.
killClient	Disconnect a client from 1C:Enterprise cluster server.
Load	Add-in import to a host-process (for the ADDIN event) and the action result.
lockRecord	Locked record.
lookupTmpTable	Get/create a temporary database table.
MergeSynchro	Merge files with full-text search indexes.
modifyFile	Update a file.
moveFile	Move a file.
quickInsert	Quick insert of data into a database table.
readFile	Read a file.
reFillTable	Refill and resume filling in of the database copy table (for DBCOPIES event).
regAuthenticate	Cluster administrator authentication.
regAuthenticate	Perform cluster authentication.
Regular indexing, 1000 packets written	Finish writing each thousand packets to the event log index (for the EVENTLOG event).
ReleaseObject	Add-in object deletion (for the ADDIN event) and the action result.
removeCopy	Delete a database copy (for DBCOPIES event).
restoreObject	Restore an object.
resumeIndexing	Resume database table indexing.
returnTmpTable	Release a temporary database table.
rollbackTransaction	Cancel a transaction.
saveObject	Save an object.
searchFile	Search a file.
securedInsert	Insert records with restrictions on data access.
selectFileName	Select a file name.
serializeTable	Save table data to a file.
setClusterRecycling	Change settings for restarting the cluster working processes (except for fault tolerance level).
setFaultToleranceLevel	Change the cluster fault tolerance level.
setInfoBaseConnectingDeny	Change infobase session start blocking parameters.
setInfoBaseConnectingDeny	Set locking mode for establishing connections with infobase.
setInfoBaseDescr	Change description of an infobase.
setInfoBaseDescr	Set description of an infobase.
setInfoBaseScheduledJobsDeny	Change infobase scheduled job locks.
SetProperty	Add-in object property setting (for the ADDIN event) and the action result.
setRegDescr	Change description of a cluster.
setRegDescr	Set description of a cluster.
setRegMultiProcEnable	Enable support of multiple working processes for a cluster.
setRegSecLevel	Change level of the secure cluster connection.
setRegSecLevel	Set cluster security level.
setRollbackOnly	Set a flag indicating errors in transaction (such transaction can only be rolled back).
setSecurityProfile	Create or modify a security profile.
setSecurityProfileAddIn	Create/modify an entry in the security profile (add-in).
setSecurityProfileApplication	Create/modify an entry in the security profile (application).
setSecurityProfileComClass	Create/modify an entry in the security profile (COM class).
setSecurityProfileExternalModule	Create/modify an entry in the security profile (external module).
setSecurityProfileInternetResource	Create/modify an entry in the security profile (Internet resource).
setSecurityProfileVirtualDirectory	Create/modify an entry in the security profile (virtual directory).
setServerProcessCapacity	Set throughput capacity of a working process.
setServerProcessCapacity	Set performance capacity of a working process.
setServerProcessEnable	Set flag indicating that a working process is allowed to start.
setServerProcessEnable	Set status of a working process.
setServiceAssociationRule	Create or modify a functionality assignment rule.
setSingleUser	Set exclusive mode.
setSrcProcessName	Create common infobase data in a working process and assign a common name to this data. An event is recorded when the first user connects to infobase through this working process or when performing a dynamic update of the infobase configuration.
setTableState	Change the state of the database copy table (for DBCOPIES event).
start	Start a session (an event of SESN type is logged at the time when a session starts and has no duration).
Start indexing file	Start writing a new event log index file (for the EVENTLOG event).
suspendIndexing	Cancel indexing of database tables.
takeKeyVal	Get a value of a table record key.
transaction	Start a transaction (an event of SDBL type starts at the beginning of a transaction, ends when it is finished).
transferChangesTable	Transfer changed objects to the database copy (for DBCOPIES event).
transferTrLogs	Transfer transaction logs to the database copy (for DBCOPIES event).
updateCopyContent	Change content of the database copy tables (for DBCOPIES event).
updateCopyProperties	Change parameters of a database copy (for DBCOPIES event).
updateRegServer	Modify parameters of a working server.
updateTimeIsOver	Completion of the database copy update (for DBCOPIES event).
wait	Wait for an assignment (an event of SESN type is output when waiting period of assigning a session to a connection is finished). Duration of an event is equal to the time spent while waiting for a connection. If a connection is assigned with a session which has already been assigned, then the current thread of the current connection is waiting for cancellation of the session assignment to another connection.
xlockTables	Set an exclusive lock on a table.
xlockTablesShared	Set a shared lock on a table.

3.22.2.4.4. Description of the res property for the LIC event

The following values are possible:

• seize. A new license is used.
• reuse. A license is reused. If the res property is set to seize or reuse, then the txt property contains the following information:
  • An array with the numbers of received licenses.
  • License recipient:
    • local Designer.
    • local application.
  • A unique ID for a session or server receiving license.
  • An ID of license if it has been received.
  • A kind of a license requested:
    • local Designer. Designer.
    • local application. Client application.
    • local COM connector 32. 32-bit COM connection.
    • local COM connector 64. 64-bit COM connection.
    • local server 32. 32-bit 1C:Enterprise server.
    • local server 64. 64-bit 1C:Enterprise server.
    • remote application. Any 1C:Enterprise application on a remote computer.
  • Information on the viewed license keys or license files:
    • For the hardware licenses:
      • hard.
      • A local or network key used.
      • Key series: client, client 300, client 500, server 32, server 64.
      • Why a license has not been received:
      • not available. Does not exist (en error detected in the API of working with HASP keys).
      • no licenses left. All licenses have run out.
      • no slots left. All licenses have run out.
      • absent. An attempt to use a key that is no longer available (for example, already removed from a computer).
      • local and single key is already used. An attempt to obtain an already occupied license from a local single-user key.
    • Number of licenses (if this information is available).
    • How many licenses have already been obtained (if this information is available).
    • For the software licenses:
      • soft.
      • Name of the activated license file.
      • Reason for a denial of a license:
      • stop list. A license file is blacklisted.
      • bad format. Incorrect file format.
      • bad signature. The Licensing Center signature is invalid.
      • second server lite. Re-license for MINI server.
      • binding error. Binding error.
      • incorrect license type. A license of incorrect kind.
      • no licenses left. All licenses have run out.
      • exception (exception text). Other exception..
    • Option of the Licensing Center Signature
      • Short. For a license obtained by phone.
      • Long. For licenses obtained on media or via Internet.
    • License registration number.
    • License activation PIN code.
    • License type.
    • Maximum number of users.
    • Supporting information.
    • Differences in the list of equipment:
      • For the software licenses activated for version 8.2.14 and earlier:
        • Added in current computer configuration. List of equipment that is currently available but was not available at the moment of obtaining the license..
        • Available at license acquisition time. List of equipment that was available at the moment of obtaining the license..
      • For the software licenses activated for version 8.2.15 and later:
        • Removed after license acquisition. List of equipment that is currently not available but was available at the moment of obtaining the license.
        • Available in current computer configuration. List of equipment that is currently available but was not available at the moment of obtaining the license. Only if such equipment does exist.
  • If a license is acquired, the following data about a key or the software license is provided:
    • For the hardware licenses:
      • Dongle series.
      • Key type.
      • Number of licenses.
      • Number of licenses taken after acquiring the current license.
  • For the software licenses:
    • Name of the activated license file.
    • License type.
    • Number of licenses.
    • Number of licenses taken after acquiring the current license.
• release. A release of license. In this case, the txt property contains the following information:
  • For the software licenses:
    • Internal UUID of the object of the license being released.
    • Creation time of the object of the license being released.
    • Recipient of the license.
    • License being released: client, server32, server64, server lite.
    • Supporting information.
  • For the hardware licenses:
    • Internal UUID of the object of the license being released.
    • Creation time of the object of the license being released.
    • Recipient of the license.
    • Supporting information about a key.
• binding. Verification of compliance of the current list of equipment to the list that was used when activating a soft license. When a mismatch found is critical for a license binding, the txt property contains the following information:
  • Computer binding parameter changed.
  • For each license file that stops working because of the current computer parameters, the following information is displayed:
    • Name of the activated license file.
    • License registration number.
    • License activation PIN.
    • License type.
    • Maximum number of users.
    • Differences in the list of equipment:
      • For the software licenses activated for version 8.2.14 and earlier:
        • Added in current computer configuration. List of equipment that is currently available but was not available at the moment of obtaining the license..
        • Available at license acquisition time. List of equipment that was available at the moment of obtaining the license..
      • For the software licenses activated for version 8.2.15 and later:
        • Removed after license acquisition. List of equipment that is currently not available but was available at the moment of obtaining the license.
        • Available in current computer configuration – List of equipment that is currently available but was not available at the moment of obtaining the license.
• error. An error occurred while accessing the licensing mechanism.
• must be removed. The file with license is not used and must be deleted.

3.22.2.4.5. Descr property description

Descr property content depends on the event accommodating the said property:

• Contains the event description for ATTN event. Depending on the event the technological log records contains different set of properties:
  • Server online. Production server is available.

    Available properties:

    • AgentUrl. Production server URL.
  • Server unavailable. Production server is unavailable.

    Available properties:

    • AgentUrl. Production server URL.
  • Server check error. An unexpected error occurred during the production server survey.

    Available properties:

    • AgentUrl. Production server URL.
  • Main manager inaccessible. Local main manager is unavailable.

    Available properties:

    • Url. Main cluster manager URL.
    • AgentUrl. Production server URL.
    • ProcessId. Cluster process UUID of a cluster manager or a working process.
    • Pid. Operating system ID of a cluster process: a cluster manager or a working process.
  • Main manager not responding. Local main manager is not responding. It might be forcibly terminated according to the Terminate corrupted processes setting.

    Available properties:

    • Url. Main cluster manager URL.
    • AgentUrl. Production server URL.
    • ProcessId. Cluster process UUID of a cluster manager or a working process.
    • Pid. Operating system ID of a cluster process: a cluster manager or a working process.
  • Process online. Cluster process is available.

    Available properties:

    • Url. Process URL.
    • AgentUrl. Production server URL.
    • ProcessId. Cluster process UUID.
    • Pid. Operating system ID of a cluster process: a cluster manager or a working process.
  • Process inaccessible. Cluster process is unavailable.

    Available properties:

    • Url. Process URL.
    • AgentUrl. Production server URL.
    • ProcessId. Cluster process UUID of a cluster manager or a working process.
    • Pid. Operating system ID of a cluster process: a cluster manager or a working process.
    • Info. Number of attempts to establish connection with the process completed with an error.
  • Process not responding. Cluster process is not responding. It might be forcibly terminated according to the Terminate corrupted processes setting.

    Available properties:

    • Url. Process URL.
    • AgentUrl. Production server URL.
    • ProcessId. Cluster process UUID of a cluster manager or a working process.
    • Pid. Operating system ID of a cluster process: a cluster manager or a working process.
    • Info. Number of attempts to establish connection with the process completed with an error.
  • Process obsolete. Process is excluded from the cluster.

    Available properties:

    • Url. Process URL.
    • AgentUrl. Production server URL.
    • ProcessId. Cluster process UUID of a cluster manager or a working process.
    • Pid. Operating system ID of a cluster process: a cluster manager or a working process.
  • Process server unavailable. The process is excluded from the cluster. You cannot determine its status as it is located on an unavailable server.

    Available properties:

    • Url. Process URL.
    • AgentUrl. Production server URL.
    • ProcessId. Cluster process UUID of a cluster manager or a working process.
    • Pid. Operating system ID of a cluster process: a cluster manager or a working process.
  • Process expired. The process is excluded from the cluster but it cannot terminate on its own. It might be forcibly terminated according to the Terminate corrupted processes setting.

    Available properties:

    • Url. Process URL.
    • AgentUrl. Production server URL.
    • ProcessId. Cluster process UUID of a cluster manager or a working process.
    • Pid. Operating system ID of a cluster process: a cluster manager or a working process.
  • Process finished. Cluster process is completed.

    Available properties:

    • Url. Process URL.
    • AgentUrl. Production server URL.
    • ProcessId. Cluster process UUID of a cluster manager or a working process.
    • Pid. Operating system ID of a cluster process: a cluster manager or a working process.
  • Process exceeded critical memory limit. The specified process will be forcibly terminated to free up space as the process memory on the server has exceeded a critical limit.

    Available properties:

    • Url. Process URL.
    • AgentUrl. Production server URL.
    • ProcessId. Cluster process UUID of a cluster manager or a working process.
    • Pid. Operating system ID of a cluster process: a cluster manager or a working process.
  • Memory exceeded temporary allowed limit. The server process memory has exceeded the temporarily allowed limit.

    Available properties:

    • ServerId. Server cluster UUID.
    • Host. Name of the computer running the server cluster.
    • MemoryLimits. Set memory limits.
    • TotalMemory. Total server RAM.
    • ExcessStartTime. Timestamp when the memory excess was registered.
    • ExcessDurationSec. Memory excess duration in seconds.
  • Memory exceeded critical limit. Process memory on the server has exceeded a critical limit.

    Available properties:

    • ServerId. Server cluster UUID.
    • Host. Name of the computer running the server cluster.
    • MemoryLimits. Set memory limits.
    • TotalMemory. Total server RAM.
    • ExcessStartTime. Timestamp when the memory excess was registered.
    • ExcessDurationSec. Memory excess duration in seconds.
  • Memory shortage detected. There is less free RAM left than the safe consumption per call.

    Available properties:

    • ServerId. Server cluster UUID.
    • Host. Name of the computer running the server cluster.
    • FreeMemory. Available server RAM.
    • SafeLimit. Safe memory usage per call.
• Contains performed operation description for SRVC event. For this event, the property text has the following format: <ServiceName>[, <InfobaseName>[, <SessionID>]]:<Action>, where:
  • <ServiceName>. Name of the service on which the operation is performed.
  • <IBName>. Infobase name.
  • <SessionID>. Session UUID.
  • <Action>.Description of the action performed on the cluster service:
    • service notified <notification name> <parameters>. The service receives notification of cluster event.
    • service started. Service instance creation.
    • service finished. Service instance release.
• Contains the operation description (in English) for WINCERT event. This description allows for identifying a call to the Windows API function and restoring the state of environment at the time of a call. The following message options are possible:
  • CertGetCertificateChain failed. Error in building the certificate chain. If such an error occurs, you need to analyze the error code (the errorCode property ). It is possible that the default crypto-provider does not support the algorithm of certificate encryption. To search for information about errors, the Microsoft Internet resources are recommended.
  • CertVerifyCertificateChainPolicy failed. Error in the certification chain verification involving policies. If such an error occurs, you need to analyze the error code (the errorCode property ). A certificate might have been revoked, certain certificates in the chain might be missing, and so on. To search for information about errors, the Microsoft Internet resources are recommended.

3.22.2.4.6. Event property description

Event property values and an array of properties to be additionally set in this event are listed in this section:

• connection assigned. A working process is assigned to the connection. The following properties are defined for the event:
  • ApplicationExt. Clarification of the functionality assignment rule.
  • DstAddr. Assigned working process address.
  • DstId. UUID of the assigned working process.
  • DstPid. System ID of the assigned working process.
  • Ref. Infobase name.
  • Request. Connection request ID.
  • SrcAddr. Preferred working process address.
  • SrcId. UUID of the preferred working process.
  • SrcPid. System ID of the preferred working process.
• current version newer. An active instance of the service received replication with the obsolete version of the service state and rejected it. The following properties are defined for the event:
  • MyVer. Current service status version.
  • NeedResync. Synchronization of service data (for the current version older event) is required.
  • Ref. Infobase name.
  • ServiceName. Cluster service name.
  • SessionID. Session number.
  • SrcVer. Received service status version.
• current version older. An active service instance that received replication with the new service state version must become a backup instance.
• data replication start. Start replicating data from the current active instance of service to a backup instance. The following properties are defined for the event:
  • Ref. Infobase name.
  • ServiceName. Server cluster service name.
  • SessionID. Session number.
• destination version newer. Replication was moved to the active instance of the service with the new version of the service state, replication was rejected and the current service should become backup. The following properties are defined for the event:
  • Ref. Infobase name.
  • ServiceName. Server cluster service name.
  • SessionID. Session number.
• destination version older. Replication was moved to an active service instance with the obsolete service state version.
• finish replication. Replication is finished. The following properties are defined for the event:
  • Ref. Infobase name.
  • ServiceName. Server cluster service name.
  • SessionID. Session number.
• main rmngr is down. Error in calling the cluster service on the main manager. The working process is to be finished. The following properties are defined for the event:
  • ServiceName. The name of the service upon calling on which it was discovered that the main cluster manager is unavailable.
• no process for connection. No acceptable working process to establish connection is found. The following properties are defined for the event:
  • ApplicationExt. Clarification of the functionality assignment rule.
  • DstSrv. Assigned working server name.
  • Ref. Infobase name.
  • Request. Connection request ID.
  • SrcAddr. Preferred working process address.
  • SrcId. UUID of the preferred working process.
  • SrcPid. System ID of the preferred working process.
• performance update. Updated available process performance. The following properties are defined for the event:
  • Data. Values of the parameters used to calculate available process performance listed as comma-separated "parameter"="value".
• process deficit detected. The deficit of working processes is detected. The following properties are defined for the event:
  • Host. Computer name.
  • Connections. The number of connections for which working processes are missing.
  • Infobases. The number of infobases for which working processes are missing.
  • Deficit. The number of missing working processes.
• process restart required. It is required to restart working processes. The following properties are defined for the event:
  • ByMemory. IDs of working processes restarted by occupied memory.
  • ByTime. IDs of working processes restarted by lifetime.
• process requirements changed. Changes in working processes are required. The following properties are defined for the event:
  • Obsolete. The number and UUIDs of obsolete working processes.
  • Registered. The number and UUIDs of new working processes.
  • Released. The number and UUIDs of backup working processes that became the main processes.
• rebalance denied. Rebalance is not required, although the request was received. The following properties are defined for the event:
  • ApplicationExt. Clarification of the functionality assignment rule.
  • Ref. Infobase name.
  • SrcAddr. Working process address.
  • SrcId. Working process UUID.
  • SrcPid. System ID of the working process.
• rebalance required. The rebalance request is satisfied. The following properties are defined for the event:
  • ApplicationExt. Clarification of the functionality assignment rule.
  • DstAddr. Assigned working process address.
  • DstId. UUID of the assigned working process.
  • DstPid. System ID of the assigned working process.
  • Ref. Infobase name.
  • SrcAddr. Preferred working process address.
  • SrcId. UUID of the preferred working process.
  • SrcPid. System ID of the preferred working process.
• register rmngr. Registration of cluster managers.
• register rphost. Registration of the cluster working processes.
• unregister rmng. Unregistering of the cluster managers.
• unregister rphost. Unregistering of the cluster working processes.

3.22.2.4.7. Txt property description

Textproperty content depends on the event accommodating the said property:

• For the HASP event, this property contains source data and the result of accessing the key in the following format: <Operation>(<List of input parameters>)-><List of output parameters>. Further:
  • <Operation>. An operation performed in this key reference.
  • <List of input parameters>. A list of the input parameters and their values separated by commas.
  • <List of output parameters> . A list of the output parameters and their values separated by commas.

    You can find the full list of operations, their parameters, and results in the HASP developer guide (https://sentineldiscussion.safenet-inc.com/viewFile.do?fileId=43161000000036014&forumGroupId=43161000000003001).

• For the event CONN, this property contains a description of this or another event within the borders of the system of monitoring disconnection. A property value looks like ‘EventName: Parameter1=Value1,Parameter2=Value2,…’. The following system events have been defined:
  • Ping direction opened. A new direction of verification in the client process has been emerging.

    Parameters:

    • address: String. Direction address.
    • pingTimeout: Number. Verification timeout.
    • pingPeriod: Number. Verification period.
    • directionID: UUID. Direction ID.
  • Ping direction closed. Completion of verification in the direction of the client process.

    Parameters:

    • address: String. Direction address.
    • pingTimeout: Number. Verification timeout.
    • pingPeriod: Number. Verification period.
  • Connection established for ping direction. The TCP connection has been established to verify the client process.

    Parameters:

    • address: String. Direction address.
    • pingTimeout: Number. Verification timeout.
    • pingPeriod: Number. Verification period.
  • Ping direction switched to TCP mode. A verifying stream on the client process has been switched to the TCP-based verification mode.

    Parameters:

    • address: String. Direction address.
    • pingTimeout: Number. Verification timeout.
    • pingPeriod: Number. Verification period.
  • Ping direction not available. A timeout occurred in the direction of verification on the client process.

    Parameters:

    • address: String. Direction address.
    • pingTimeout: Number. Verification timeout.
    • pingPeriod: Number. Verification period.
  • Ping direction available. A verification direction on the client process has become available again.

    Parameters:

    • address: String. Direction address.
    • pingTimeout: Number. Verification timeout.
    • pingPeriod: Number. Verification period.
  • Connection added to ping direction. Another connection has become associated with this verification direction.

    Parameters:

    • address: String. Direction address.
    • pingTimeout: Number. Verification timeout.
    • pingPeriod: Number. Verification period.
    • clientID: Number. A connection number associated with a verification direction.
  • Connection removed from ping direction. A connection has ceased to be associated with this verification direction.

    Parameters:

    • address: String. Direction address.
    • pingTimeout: Number. Verification timeout.
    • pingPeriod: Number. Verification period.
    • clientID: Number. A connection number associated with a verification direction.
  • Ping direction statistics. Statistics on the verification direction. It is displayed in each direction every 10 seconds and before completing a directional verification.

    Parameters:

    • address: String. Direction address.
    • pingTimeout: Number. Verification timeout.
    • pingPeriod: Number. Verification period.
    • period: Number. Time in milliseconds spent to collect statistical data.
    • packetsSent: Number. A number of packets sent.
    • avgResponseTime: Number. An average response time.
    • maxResponseTime: Number. A maximum response time.
    • packetsTimedOut: Number. Packets not responded to before timeout.
    • packetsLost: Number. Number of packets not responded to but not yet timed out.
    • packetsLostAndFound: Number. A number of responses received on packets sent but not taken into account.
  • Connection added to ping direction on server – One more connection has become corresponding to a verification direction on server process.

    Parameters:

    • directionID: UUID. Direction ID.
    • clientID: Number. A connection number associated with a verification direction.
    • address: String. Direction address.
  • Connection removed from ping direction on server. One connection has ceased to correspond to a verification direction on server process.

    Parameters:

    • directionID: UUID. Direction ID.
    • clientID: Number. A connection number associated with a verification direction.
  • Ping direction opened on server. A new verification direction appeared on server process.

    Parameters:

    • directionID: UUID. Direction ID.
  • Ping direction closed on server. A verification direction has ceased to exist on server process.

    Parameters:

    • directionID: UUID. Direction ID.
  • Ping direction not available on server. Timeout has been detected in a verification direction on server process.

    Parameters:

    • directionID: UUID. Direction ID.
  • Ping direction settings changed on server. A verification period and verification timeout have been transferred to a verification direction on server process.

    Parameters:

    • directionID: UUID. Direction ID.
    • pingTimeout: Number. Verification timeout.
    • pingPeriod: Number. Verification period.

3.22.2.5. <dump>

The item <dump> defines the parameters of dump created when an application crashes. To disable dump recording, set create = "0" or create = "false" in the item <dump>. If <dump> is absent, the directory %USERPROFILE%\Local Settings\Application Data\1C \ 1cv8\dumps (for Windows) will be used to record the dumps.

The item attributes:

The name of a directory in which the dump files will be placed.

Create or not create a dump file.

• 0 (false). Do not create.
• 1 (true). Create.

Dump type – an arbitrary combination of the following check boxes, represented in decimal or hexadecimal system (addition of check box values). A hexadecimal representation must begin with a ‘x’ character; for example, x0002.

The following values are available:

• 0 (x0000). Minimum.
• 1 (x0001). Additional data segment.
• 2 (x0002). Content of the entire memory of a process.
• 4 (x0004). Handle data.
• 8 (x0008). Leave in dump only information needed to restore the server call stacks.
• 16 (x0010). If stack contains references to the modules' memory, then add the check box 64 (0x0040).
• 32 (x0020). To include memory from under the unloaded modules into dump.
• 64 (0x0040). To include memory to which there are links to dump.
• 128 (x0080). To add detailed information about the module files to dump.
• 256 (0x0100). To add local stream data to dump.
• 512 (0x0200). Inclusion of memory from the entire available virtual address space in dump.

Indicates whether to save a screenshot when 1C:Enterprise client crashes. The file name is the same as the dump name but has extension png. The screen copy files are created in the same directory as dumps (see the location attribute).

• 0 (false). Do not create.
• 1 (true). Create.

If 1C:Enterprise crashes, the system displays a dialog box with information about the dump recording process, which is automatically closed after the dump recording is completed.

Controls generation of a crash dump if 1C:Enterprise is running on Windows. The attribute can take the following values:

• 0 (false). A dump is generated by a process that crashes (default value).
• 1 (true). A dump is generated by the external application dumper.exe, which is included in 1C:Enterprise distribution package. When an external program is being used, a possibility of hanging in the process of creating dump is excluded.

If an external program is not detected or some problems are detected during its launch, standard mode for creating dumps (using a crashing process) will be used.

It is recommended to use an external program of generating dumps for 1C:Enterprise servers that work without daily maintenance.

3.22.2.6. <leaks>

The <leaks> item establishes tracking of memory leaks caused by issues in configuration code. By default, leak tracking is disabled and it does not affect the system performance.

To enable leak data collection, add the <leaks> item in the logcfg.xml file: <leaks collect="1"> or <leaks collect="true">.

To disable memory leak tracking, change the <leaks> item: <leaks collect="0"> or <leaks collect="false">.

If a leak tracking is enabled, then creation and deletion of the following objects is controlled by user:

• Form
• ManagedForm
• FixedStructure
• FixedMap
• StructureFormData
• CollectionFormData
• StructureWithCollectionFormData
• CollectionItemFormData
• TreeFormData
• TreeItemCollectionFormData
• TreeItemFormData
• AccountingRegisterManager
• AccountingRegisterRecordSet
• ChartOfAccountsManager
• ChartOfAccountsObject
• ExchangePlanManager
• ExchangePlanObject
• SettingsStorageManager
• AccumulationRegisterManager
• AccumulationRegisterRecordSet
• ChartOfCharacteristicTypesManager
• ChartOfCharacteristicTypesObject
• ConstantManager
• DocumentManager
• DocumentObject
• EnumerationManager
• ExternalDataProcessor
• ExternalReport
• InformationRegisterManager
• InformationRegisterRecordSet
• DataProcessorManager
• DataProcessor
• CatalogManager
• CatalogObject
• ReportManager
• Report
• SequenceRecordSet
• BusinessProcessManager
• BusinessProcessObject
• TaskManager
• TaskObject
• ChartOfCalculationTypesManager
• ChartOfCalculationTypesObject
• CalculationRegisterManager
• CalculationRegisterRecordSet
• RecalculationRecordSet
• COMSafeArray
• KeyAndValue
• Array
• FixedArray
• Map
• Structure
• ValueListItem
• ValueList
• ValueTable
• ValueTableRow
• ValueTree
• ValueTreeRow

Leaks are tracked between the start and end checkpoints in the code. The start checkpoint clears leak data for a current user. At the end checkpoint, the LEAKS event is generated and written to the technological log in which for each unreleased object instance the stack of the embedded 1C:Enterprise language will be indicated at the time of its creation.

The following can be used as checkpoints:

• Starting and ending execution of 1C:Enterprise language commands on the client or server.
• Calling a procedure or function of 1C:Enterprise language and returning from the procedure or function.
• Starting execution of one line of 1C:Enterprise language and finishing execution of another line of 1C:Enterprise language.

The starting and ending checkpoint is defined by the item <point>. In this case, the embedding of checkpoints into each other is allowed but being ignored; a counting of leaks is carried out only on the external checkpoints. For example, if during the execution of the configuration code the checkpoints of Starting1, Starting2, Ending1, Ending2 were passed, then the leaks will be tracked between the points Starting1 and Ending2.

The item <point> can have one of the following formats:

Defines checkpoints at the beginning/end of 1C:Enterprise language execution on the client or on the server. The starting point will be set at the beginning of 1C:Enterprise language execution on the server/client. The ending point will be set at the end of 1C:Enterprise language execution on the server/client.

Defines checkpoints when calling and returning a specific 1C:Enterprise language method. <ModuleName> contains the full name of the metadata object to which the module belongs (without the configuration name). In the same format, the debugger shows the module names. <MethodName> contains the name of method. If the <MethodName> argument is not set, then the checkpoints will be defined at the beginning/ending of the module body execution. Examples of module names:

• SessionModule.Module. Session module.
• ApplicationModule.Module. Application module.
• ManagedApplicationModule.Module. Managed application module.
• ExternalConnectionModule.Module. External connection module.
• CommonModule.Global.Module. Common module. Global.
• Catalog.Counterparties.ObjectModule. Module of the Counterparties catalog item.
• DataProcessor.DataProcessor1.Form.Form1.Form. Module of the Form1 form of the DataProcessor1 data processor.
• DataProcessor.DataProcessor2.Form.MainForm.Form. Module of the MainForm form of the DataProcessor2 data processor.

Defines the starting and ending checkpoints by explicitly specifying the lines of code. The starting checkpoint corresponds to the beginning of execution of code for the string specified in the attribute On. The ending checkpoint corresponds to the end of the execution of code for the string specified in the attribute Off. Line numbering starts with 1. If the starting checkpoint is reached on server, then the ending checkpoint must be reached on server, as well. The ending checkpoint cannot be the last string of the procedure code, function or module body.

An example of item <leaks>:

<leaks collect="1">
<point call="client"/>
<point call="server"/>
<point proc="ApplicationModule/"/>
<point proc="CommonModule.ConnectionProcessing.Module/AtServerNoLeaks"/>
<point on="CommonModule.Services.Module/9" off="CommonModule.Services.Module/11"/>
</leaks>

In this case, leak data collection is enabled. The checkpoints are set:

• At the beginning and at the end of execution of 1C:Enterprise language on client
• At the beginning and at the end of execution of 1C:Enterprise language on server
• At the beginning and at the end of execution of the application module body
• When calling and returning method AtServerNoLeaks() from the common module ConnectionProcessing
• On lines 9 and 11 of the common module Services

Suppose a procedure with the following text causes a memory leak:

Procedure AtServerWithLeak() Export
M=NewArray;
M.Add(NewArray);
M[0].Add (NewArray);
M[0][0].Add(M);
EndProcedure

To detect it, leak tracing in the technological log can be enabled using the following settings:

<config xmlns="http://v8.1c.ru/v8/tech-log">
<log location="C:\ProgramFiles\1cv8\logs" history="24">
<event>
<eq property="name" value="call"/>
</event>
<event>
<eq property="name" value="leaks"/>
</event>
<property name="all">
</property>
</log>
<leaks collect="1">
<point call="server"/>
</leaks>
</config>

When the server is called or a scheduled job is performed, if there is no leak, a technological log fragment will look like as follows:

59:44.4562-2840,CALL,5,process=rphost,p:processName=t76346,t:clientID=428,t:applicationName=JobScheduler,Func=Execute,Module=CommonModule2,Meth=ScheduledTaskNoLeak

59:49.4581-2700,CALL,5,process=rphost,p:processName=t76346,t:clientID=430,t:applicationName=JobScheduler,Func=Execute,Module=CommonModule2,Meth=ScheduledTaskNoLeak

And if a leak occurs, the log will look like this:

59:48.4768-2885,CALL,5,process=rphost,p:processName=t76346,t:clientID=429,t:applicationName=JobScheduler,Func=Execute,Module=CommonModule2,Meth=ScheduledTaskWithLeak

59:48.4769-0,LEAKS,5,process=rphost,Descr='

Array:

CommonModule.CommonModule2:2:AtServerWithLeaks();

CommonModule.CommonModule1:4:M[0].Add(NewArray);



Array:

CommonModule.CommonModule2:2:AtServerWithLeaks();

CommonModule.CommonModule1:2:M=NewArray;



Array:

CommonModule.CommonModule2:2:AtServerWithLeaks();

CommonModule.CommonModule1:3:M.Add(NewArray);

In the above fragment, when method ScheduledJobWithLeak() of module CommonModule2 is executed as a scheduled job (t: applicationName = JobScheduler, Func = Execute), the three Array objects were created and not released. In this case, 1C:Enterprise language call stacks at the time of creation of each object are indicated.

3.22.2.7. <mem>

If the item <mem> is present, 1C:Enterprise server processes monitor:

• Number of allocated and not released fragments of memory
• Total size of allocated and not released memory fragments

If between the moments when the server process was not performing either any calls and any routine task, the number of allocated but not released memory fragments increased, then a MEM event is generated with the following properties:

• sz. A total number of memory fragments allocated but not released by process.
• szd. Its modification since the previous output of the MEM event.
• cn. An overall number of the memory fragments, allocated but not released by process.
• cnd. Its modification since the previous output of the MEM event.

A duration of the MEM event is equal to the period between the last and penultimate moments when the server process was not performing any calls and any routine tasks. It was during this time that the number of memory fragments used by process increased.

For example, with the following configuration, a volume of distributed memory is not collected and the MEM events are not being output:

<config xmlns="http://v8.1c.ru/v8/tech-log">
<log location="C:\ProgramFiles\1cv8\logs" history="24">
<event>
<eq property="name" value="mem"/>
</event>
<property name="all"/>
</log>
</config>

The following configuration of the technological log collects the volume of distributed memory and, as it grows, displays the MEM events:

<config xmlns="http://v8.1c.ru/v8/tech-log">
<log location="C:\ProgramFiles\1cv8\logs" history="24">
<event>
<eq property="name" value="mem"/>
</event>
<property name="all"/>
</log>
<mem/>
</config>

3.22.2.8. <ftextupd>

The <ftextupd> item includes generation of the extended information about the process of updating the full-text search indexes (the event FTETXUpd). If the item is not in file, then the extended information is not included in the technological log.

The item attributes:

A presence of extended information in the FTEXTUpd event:

• 0 (false). Do not include.
• 1 (true). Include.

3.22.2.9. <query>

The <query> item controls placing information to the technological log about fields that contain NULL when executing a request to an external data source but for which such a value is not allowed (the QERR event). If you enable this tracking, it can significantly slow down query execution.

The item attributes:

Manages a collection of information:

• 1 (true). Field information will be collected.
• 0 (false) or the query item is missing in the file. No field information is collected.

3.22.2.10. <plansql>

3.22.2.10.1. General description

If <plansql> is present, a collection of the query plans will be included that generate the DBMS when performing 1C:Enterprise queries. The query plans are located in the planSQLText property of the events related to execution of the requests of a specific DBMS (see article <property>).

<?xml version="1.0"?>
<config xmlns="http://v8.1c.ru/v8/tech-log">
<log location="c:\log" history="2
<event>
<eq property="name" value="dbmssql"/>
</event>
<property name="sql"/>
<property name="plansqltext"/>
</log>
<plansql />
</config>

In the example above, for Microsoft SQL Server (expression <eq property = "name" value = "dbmssql"/> ), a collection of query plans (<plansql/> item) is enabled and they are written into the technology log (expression <property name = "plansqltext"/>) together with the texts of queries themselves (expression <property name ="sql"/>) in the query language of 1C:Enterprise.

3.22.2.10.2. Information on the DBMS query plans

Information on working with specific DBMS query plans is provided in the documentation for these DBMS:

• Microsoft SQL Server 2000:
  • https://msdn.microsoft.com/en-us/library/aa178417(v=SQL.80).aspx
  • https://msdn.microsoft.com/en-us/library/aa259207(v=SQL.80).aspx
  • https://msdn.microsoft.com/en-us/library/Aa259203.aspx
• Microsoft SQL Server 2005:
  • https://msdn.microsoft.com/en-US/library/ms176005(v=SQL.90).aspx
  • https://msdn.microsoft.com/en-us/library/ms187735(SQL.90).aspx
• Microsoft SQL Server 2008:
  • https://msdn.microsoft.com/en-us/library/ms176005(v=SQL.100).aspx
  • https://msdn.microsoft.com/en-us/library/ms187735(v=SQL.100).aspx
• Microsoft SQL Server 2008 R2:
  • https://msdn.microsoft.com/en-us/library/ms176005(v=SQL.105).aspx
  • https://msdn.microsoft.com/en-us/library/ms187735(v=SQL.105).aspx
• Microsoft SQL Server 2012:
  • https://msdn.microsoft.com/en-us/library/ms187735(v=SQL.11).aspx
• PostgreSQL 8.1 Windows/Linux:
  • https://www.postgresql.org/docs/8.1/static/performance-tips.html
• PostgreSQL 8.2 Windows/Linux:
  • https://www.postgresql.org/docs/8.2/static/using-explain.html
• PostgreSQL 8.3 Windows/Linux:
  • https://www.postgresql.org/docs/8.3/static/using-explain.html
• PostgreSQL 8.4 Windows/Linux:
  • https://www.postgresql.org/docs/8.4/static/using-explain.html
• PostgreSQL 9.0 Windows/Linux:
  • https://www.postgresql.org/docs/9.0/static/using-explain.html
• PostgreSQL 9.1 Windows/Linux:
  • https://www.postgresql.org/docs/9.1/static/using-explain.html
• PostgreSQL 9.2 Windows/Linux:
  • https://www.postgresql.org/docs/9.2/static/using-explain.html
• PostgreSQL 9.3 Windows/Linux:
  • https://www.postgresql.org/docs/9.3/static/using-explain.html
• PostgreSQL 9.4 Windows/Linux:
  • https://postgrespro.com/docs/postgresql/9.4/using-explain.htmlhttps://postgrespro.ru/docs/postgresql/9.4/using-explain.html
• PostgreSQL 9.6 Windows/Linux:
  • https://postgrespro.com/docs/postgresql/9.6/using-explain.htmlhttps://postgrespro.ru/docs/postgresql/9.6/using-explain.html
• PostgreSQL 10 Windows/Linux:
  • https://postgrespro.com/docs/postgresql/10/using-explainhttps://postgrespro.ru/docs/postgresql/10/using-explain
• Postgres Pro Standard 9.6 Windows/Linux:
  • https://postgrespro.ru/docs/postgrespro/9.6/using-explain
• Postgres Pro Standard 10 Windows/Linux:
  • https://postgrespro.ru/docs/postgrespro/10/using-explain
• Postgres Pro Standard 11 Windows/Linux:
  • https://postgrespro.ru/docs/postgrespro/11/using-explain
• Postgres Pro Enterprise 9.6 Windows/Linux:
  • https://postgrespro.ru/docs/postgresproee/9.6/using-explain
• Postgres Pro Enterprise 10 Windows/Linux:
  • https://postgrespro.ru/docs/postgresproee/10/using-explain
• Postgres Pro Enterprise 11 Windows/Linux:
  • https://postgrespro.ru/docs/postgresproee/11/using-explain
• IBM DB2 9.1 Windows/Linux:
  • https://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/c0005739.htm
  • https://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0008441.htm
• IBM DB2 9.5 Windows/Linux:
  • https://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.explain.doc/doc/r0052023.html
  • https://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.perf.doc/doc/c0005739.html
  • https://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.sql.ref.doc/doc/r0008441.html
• IBM DB2 9.7 Windows/Linux:
  • https://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.explain.doc/doc/r0052023.html
  • https://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.perf.doc/doc/c0005739.html
  • https://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.sql.ref.doc/doc/r0008441.html
• Oracle Database 10g R2:
  • https://download.oracle.com/docs/cd/B19306_01/server.102/b14211/optimops.htm
• Oracle Database 11g R1:
  • https://download.oracle.com/docs/cd/B28359_01/server.111/b28274/optimops.htm
• Oracle Database 12c R1:
  • https://docs.oracle.com/database/121/TGSQL/tgsql_optcncpt.htm

For PostgreSQL and Oracle Database, the format of a query plan exactly matches the format described in the documentation for a respective DBMS. The format of query plans for Microsoft SQL Server and IBM DB2 is simplified relative to original format. The original field names are saved. Information in these fields is interpreted in accordance with the information on a specific DBMS. These changes are reflected in the following sections.

3.22.2.10.3. The MS SQL Server query plan format

A field planSQLText for Microsoft SQL Server consists of several records (lines), each of which consists of the following fields (in DBMS terms) going in the order of description:

• Rows
• Executes
• EstimateRows
• EstimateIO
• EstimateCPU
• AvgRowSize
• TotalSubtreeCost
• EstimateExecutions
• StmtText

The fields are separated by commas. The last field describing a query plan (StmtText) should be read to the end of the line ignoring the possible characters ",". The lines are separated by line breaks.

3.22.2.10.4. IBM DB2 query plan format

The field planSQLText for IBM DB2 consists of several records (lines), each of which consists of the following fields exposed in descending order. The field names correspond exactly to the fields from the explain tables, i.e. the text IO_COST (EXPLAIN_OPERATOR) means that the IO_COST field from the explain table EXPLAIN_OPERATOR will be placed in the query plan:

• OPERATOR_TYPE (EXPLAIN_OPERATOR)
• TOTAL_COST (EXPLAIN_OPERATOR)
• STREAM_COUNT (EXPLAIN_STREAM)
• IO_COST (EXPLAIN_OPERATOR)
• CPU_COST (EXPLAIN_OPERATOR)
• COMM_COST (EXPLAIN_OPERATOR)
• BUFFERS (EXPLAIN_OPERATOR)
• PREDICATE_TEXT (EXPLAIN_PREDICATE)

The fields are separated by commas. The last field describing a query plan (PREDICATE_TEXT) should be read to the end of line ignoring any commas. The lines are separated by line breaks.

At the end of a query plan description, a line is added that starts with the text Optimized query:; it contains a query text generated by the DBMS optimizer. The original query text is given in the SQL event of the technological log. A query ends with the end-of-line character. IDs from the optimized query variant are used in data located in the PREDICATE_TEXT column.

3.22.2.10.5. Query plan format for the file mode

A query plan for the file mode has the following format:

<Query plan>

[CONST <Conditions>]
<Fields of a selection list>
[<Source description> [<Relation description> […]]]
[WITHOUT DUPLICATES]
[GROUPING]
[SORTING [CUTTING TOP]]
[UNION [ALL] <Query plan>]

In this description:

• WITHOUT DUPLICATES. Indicates that data without duplicates needs to be retrieved.
• GROUPING. Indicates that a grouping of a result needs to be performed.
• SORTING. Indicates that sorting of a result needs to be performed.
• CUTTING TOP. Indicates that after sorting a part of records will be retrieved only.

<Conditions>

WHERE [(POST) | (END)] <Condition> [AND <Condition> […]]

In this description:

• (POST). Indicates that conditions are checked after a connection is made.
• (END). Indicates that conditions are checked after the joins between all the tables are completed.

<Fields of a selection list>

Fields:(<Expression from selection list> [, <Expression from selection list>])

<Scan description>

{{NOT SCAN} | {FULL SCAN} | {DISTINCT SCAN} | {RANGE SCAN}} [UNTIL FIRST NOT NULL] [USING [REVERSE] INDEX (<Index name>) [(<Number of index fields used> fields)]]

In this description:

• NOT SCAN. Indicates that the contents of the table will not be scanned.
• FULL SCAN. Indicates that the contents of the table will be scanned completely.
• DISTINCT SCAN. Indicates that different index values will be bypassed.
• RANGE SCAN. Indicates that a section of the table will be scanned by index.
• UNTIL FIRST NOT NULL. Indicates that records will be scanned until the first record with a value not NULL is received .
• USING INDEX. Indicates that an index will be used for bypassing.
• REVERSE . Indicates that an index will be used in reverse order.

<Source description>

{<Table name> [(TWICE)] <Scan description>} |
{NESTED SELECT <Scan description> (<Query plan>)}
<Conditions>

<Relation description>

{{ NESTED [OUTER] LOOP <Table name> [(TWICE)] <Scan description>} |
{ NESTED [OUTER] LOOP BY SELECT <Scan description> (<Query plan>)}}
<Conditions> [<Conditions>]

In this description:

• (TWICE). Indicates that the table is used in query several times.
• NESTED LOOP. Indicates that for each table entry on the left, a loop will be performed to bypass the table entries on the right.
• OUTER. Indicates that if a record in the right table suitable by the linking condition is not found, the entire record will not be lost.

3.22.2.11. <defaultlog>

The item <defaultlog> defines the default technological log settings. This log has a fixed event filter defined by 1C:Enterprise. This filter cannot be changed and can be represented by the following configuration file:

<log location="C:\Users\<UserName>\AppData\Local\1C\1cv8\logs" history="24" >
<event>
<eq property="name" value="system"/>
<eq property="level" value="error"/>
</event>
<property name="all"/>
</log>

This log records events that are critical for system operability. Composition of the events is not documented. Event generation is configured using the item <system>.

The item attributes:

The name of the directory in which the default technological log will be placed. If the attribute is not specified, then the default technological log is saved to the following directories:

• Windows OS:
  • Windows XP: %USERPROFILE%\Local Settings\1C\1cv8\logs.
  • Windows Vista or later: %LOCALAPPDATA%\1C\1cv8\logs.
• On Linux: ~/.1cv8/logs.

A number of hours at which information stored the technology log will be removed. If a value of this attribute is set to 0, then the technology logging will be disabled by default.

Default value: 24.

Unlike the technological log files, the default technological log files are generated only when the corresponding event occurs.

3.22.2.12. <system>

The item <system> manages generation of the SYSTEM events in the technological log. The technology log configuration file (logcfg.xml) may not contain such an item and may also contain one or more such items.

If the item <system> is not in the file logcfg.xml, then the default technology log is configured as follows: a level of generation of the system events for all system components is defined as Error.

The events SYSTEM will be simultaneously placed in all configured technology logs (including the default technology log).

The item attributes:

Sets the minimum level value for system-generated events. Possible values (in order of increasing importance):

• Trace. The most detailed level.
• Debug. A level of debug information. Intended for the events that are necessary to debug platform mechanisms or to investigate the most difficult problems to be identified.
• Info. A level of information. Intended for the events indicating normal functioning of a one or another platform mechanism.
• Warning. A level of warnings. Intended for the events informing about the occurrence of abnormal, but not critical (in terms of mechanism of a platform) situations.
• Error. A level of errors. Designed for the events informing about the occurrence of erroneous (in terms of mechanism of a platform) situations.
• None. Disabling of fixation of the system events.

Setting this attribute will result in the “1C:Enterprise” system not generating the events not corresponding to the specified level.

So, if logcfg.xml contains fragment <system level = "info" />, 1C:Enterprise will register events with the Info, Warning and Error levels.

Specifies the name of the component for which generation of system events is configured. The component name is case-sensitive.

Specifies the name of the class for which generation of system events is configured. The class name is case-sensitive.

As an example, let's consider the situation where the logcfg.xml file contains the following fragment:

<system level="info"/>
<system level="debug" class="core::FileSystem" />
<system level="warning" component="core82" />

This means:

• SYSTEM events with the Info level (and above) are generated for all system objects.
• However, for the core::FileSystem class, events with Debug level are generated.
• For all classes of the core82 component, events with Warning level and higher are generated.

3.22.2.13. <dbmslocks>

The item <dbmslocks> enabled collection of information about database locks in the technological log. If the item is not in the file, information about database locks is not added to the technological log.

Information on database locks is displayed in the technological log using special properties; for more details, see article Writing information about mutual locks.

3.22.2.14. <scriptcircrefs>

The item <scriptcircrefs> enables collection of information about circular references in the technological log. If the item is not in the file, information about circular references is not added to the technological log.

<?xml version="1.0"?>
<config xmlns="http://v8.1c.ru/v8/tech-log">
<log location="D:\V82\logs" history="96">
<event>
<eq property="name" value="SCRIPTCIRCREFS"/>
</event>
<event>
<eq property="name" value="excp"/>
</event>
<property name="all"/>
</log>
<scriptcircrefs/>
</config>

The example implements these settings:

• Collection of information about cyclical links is enabled (item <scriptcircrefs />).
• Events added to the technological log contain all properties (item <property name = "all" />).
• Only the SCRIPTCIRCREFS and EXCP events are recorded in the technological log (items <event>).

See also:

• Writing information about circular references