Logfiles

The Database Connector uses SLF4J with logback, which is the same logging infrastructure used in  .

Log MDC entries for configuration path, the querySet name, the query name, correlation.id, tenant id, subject.id. These will be captured when processing client requests.

11:37:25.394 |-WARN  [http-nio-8082-exec-8] [c.f.c.d.s.MetaDataService] [mycompany ] [26d27ffe-1213-4c82-890b-cdc1a2e00e87 ] [  ] - Could not find retrieve operation for query STUDENT/addStudent. Skipping ...
11:37:27.186 |-ERROR [http-nio-8082-exec-8] [    c.f.c.d.QueryResource] [mycompany ] [26d27ffe-1213-4c82-890b-cdc1a2e00e87 ] [  ] - Error processing request for querySet STUDENT

Exceptions are properly logged with their stacktraces. This makes it easier to diagnose errors, which sometimes are frevvo/DBConnector specific and sometimes database specific.

All JDBC statements are logged in the DEBUG logging level. This includes the actual SQL statement used, the actual arguments, the number or rows returned and whether it was successful.

There are different logfiles for the Standalone and tomcat bundle installations.

Standalone mode

1. Three logfiles are created in the \database\database-connector-2.5.01\logs directory:
   
   1. DbConnector.err.log - there is no content in this log at this time
   2. DbConnector.out.log - database connector standard out file. You can see the results version of the queryset/queries validation along with non-error log lines that are appended to the database connector that is running in this file.
   3. DbConnector.wrapper.log - Date/Times of connector starts/stops when the Database Connector is running as a service.
2. dbconnectordatabase-connector.YYYY-MM-DD.log - this log This is created in the current working directory when the connector starts  - database\database-connector-2.5.0 when you unzip the database.zip file. This log replicates the DbConnector.out.log content in JSON formatthe main logfile for the Database Connector. You can see the results of the queryset/queries validation and output error messages in this file.
   
   

Tomcat bundle

When debugging database queries refer to output error messages in <frevvo-home>\tomcat\logs\catalina.log and frevvo_database-connector.YYYY-MM-DD.log

Log levels are controlled by the default or configured profile. profiles. The prod profile is the default.

• prod - connector log level will be set to INFO for production environments. When this profile is loaded, log levels are set to:

  • logging.level.=WARN 

  • logging.level.com.frevvo=INFO

To change the log level to DEBUG, add a property to the <frevvo-home>\tomcat\conf\dbconnector.properties file to load the dev profile.

spring.profiles.active=dev

When this profile is loaded:

• dev - connector log level will be set to DEBUG , Log levels are set to
  • logging.level.=INFO
    
  • logging.level.com.frevvo=DEBUG