For more logging you can add a dedicated log file for the CData with logging level. Log files will be created on Incorta local storage under the specified location on all of Incorta nodes: Logfile=/<location>/<logs_file_name>.log;verbosity=2
Set the verbosity level. The verbosity level determines the amount of detail that the driver reports to theLogfile.Verbositylevels from 1 to 5 are supported. These are described in the following list:
SettingVerbosityto 1 will log the query, the number of rows returned by it, the start of execution and the time is taken, and any errors.
SettingVerbosityto 2 will log everything included inVerbosity1, cache queries, and additional information about the request.
SettingVerbosityto 3 will additionally log HTTP headers, as well as the body of the request and the response.
SettingVerbosityto 4 will additionally log transport-level communication with the data source. This includes SSL negotiation.
SettingVerbosityto 5 will additionally log communication with the data source and additional details that may be helpful in troubleshooting problems. This includes interface commands.
The verbosity level should not be set to greater than 1 for normal operation. Substantial amounts of data can be logged at higher verbosities, which can delay execution times.
Verbosity 3: The full body of the request and the response, which includes all the data returned by the driver
Verbosity 4: SSL certificates
Verbosity 5: Any extra transfer data not included at Verbosity 3, such as non-human-readable binary transfer data
When Java logging is enabled inLogfile, verbositywill instead map to the following logging levels.
5. Advanced Logging
You may want to refine the exact information that is recorded to the log file. This can be accomplished using theLogModulesproperty.
This property allows you to filter the logging using a semicolon-separated list of logging modules.
All modules are four characters long.Please note that modules containing three letters have a required trailing blank space. The available modules are:
EXEC: Query Execution. Includes execution messages for original SQL queries, parsed SQL queries, and normalized SQL queries. Query and page success/failure messages appear here as well.
INFO: General Information. Includes the connection string, driver version (build number), and initial connection messages.
HTTP: HTTP Protocol messages. Includes HTTP requests/responses (including POST messages), as well as Kerberos related messages.
SSL: SSL certificate messages.
OAUT: OAuth related failure/success messages.
SQL: Includes SQL transactions, SQL bulk transfer messages, and SQL result set messages.
META: Metadata cache and schema messages.
TCP: Incoming and Ongoing raw bytes on TCP transport layer messages.