Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged.

Data Type

string

Default Value

""

Remarks

The driver writes details about each operation it performs into the logfile specified by the Logfile connection property.

Each of these logged operations are assigned to a themed category called a module, and each module has a corresponding short code used to labels individual driver operations as belonging to that module.

When this connection property is set to a semicolon-separated list of module codes, only operations belonging to the specified modules are written to the logfile. Note that this only affects which operations are logged moving forward and doesn't retroactively alter the existing contents of the logfile. For example: INFO;EXEC;SSL;META;

By default, logged operations from all modules are included.

You can explicitly exclude a module by prefixing it with a "-". For example: -HTTP

To apply filters to submodules, identify them with the syntax <module name>.<submodule name>. For example, the following value causes the driver to only log actions belonging to the HTTP module, and further refines it to exclude actions belonging to the Res submodule of the HTTP module: HTTP;-HTTP.Res

Note that the logfile filtering triggered by the Verbosity connection property takes precedence over the filtering imposed by this connection property. This means that operations of a higher verbosity level than the level specified in the Verbosity connection property are not printed in the logfile, even if they belong to one of the modules specified in this connection property.

The following table lists the available logging modules and submodules, along with a security classification that indicates the risk that their logs may expose sensitive data. These classifications reflect the driver's intended logging behavior and can help you determine which modules to include when sharing logs. Always review log contents before sharing them outside your organization, as provider-specific code may log additional information under a module:

• Safe: Internal events, lifecycle, protocol status, schema, and metadata. No customer data.
• Caution: SQL with literal values, request filters, or argument values that may indirectly expose customer data.
• Unsafe: Result sets, response bodies, payloads, raw TCP data, bulk uploads, or other customer data.