Logging components
- Last Updated: June 13, 2019
- 1 minute read
- DataDirect Connectors
- JDBC
- Aha! 6.0
- Amazon Redshift 6.0
- Apache Cassandra 6.0
- Apache Hive 6.0
- Apache Spark SQL 6.0
- Atlassian Jira 6.0
- Autonomous REST Connector 6.0
- Cloudera Impala 5.1
- + 24
Drivers that support Java logging use the Java Logging API to configure the loggers (individual logging components) used by the drivers. The Java Logging API is built into the JVM.
The Java Logging API allows applications or components to define one or more named loggers. Messages written to the loggers can be given different levels of importance. For example, errors that occur in the drivers can be written to a logger at the CONFIG level, while progress or flow information may be written to a logger at the FINE or FINER level. Each logger used by the drivers can be configured independently. The configuration for a logger includes what level of log messages are written, the location to which they are written, and the format of the log message.
The Java Logging API defines the following levels:
- SEVERE
- WARNING
- INFO
- CONFIG
- FINE
- FINER
- FINEST
Setting the log threshold of a logger to a particular level causes the logger
to write log messages of that level and higher to the log. For example, if the threshold is
set to FINE, the logger writes messages of levels FINE,
CONFIG, INFO, WARNING, and SEVERE to its log. Messages of level FINER or FINEST are not
written to the log.
The drivers expose loggers for the following functional areas:
- JDBC API
- SQL Engine
- Web service adapter