Use case: Something strange is happening in my Semarchy xDM application and I want to see the details of what happened...
...
- com.semarchy.commons.sql: with TRACE: SQL executed from REST web services calls before v4.3
- org.springframework.jdbc.core.JdbcTemplate: with DEBUG: All SQL executed REST web services calls (since v4.3)
- org.springframework.jdbc.core.StatementCreatorUtils: with TRACE: log parameters set in prepared statements.
- org.apache.cxf.services: With INFO: REST request, response, and fault between backend and frontend (Semarchy 4.4.x and above only)
- org.apache.cxf.interceptor.LoggingInInterceptor and org.apache.cxf.interceptor.LoggingOutInterceptor: with INFO : REST request, response, and fault between backend and frontend (before Semarchy 4.4.x)
Data Notifications loggers
com.semarchy.mdm.datahub.datanotif: with DEBUG, logs every action done on Data Notifications during runtime (creation, modification, processing, deletion...)
Job loggers
- com.semarchy.platform.engine.core.impl.DefaultStandaloneEngineImpl: with DEBUG level it logs all submitted jobs, ERROR level can be used to log panic shutdown of the engine
- com.semarchy.platform.integration.polling.IntegrationLoadDequeuer: with DEBUG level it logs every polled interval (even if no batches are retrieved)
- com.semarchy.platform.engine.core.impl.product.SL4JExecutionMonitor: with DEBUG level, it logs execution progress of engine jobs, see /wiki/spaces/TKB/pages/4227077 for more informations
- com.semarchy.platform.product.notification: Job notification, with DEBUG level shows calls to notification servers and ERROR logging for notification failures
for http notifications:- org.apache.http.headers: DEBUG shows the headers that were sent
- org.apache.http.wire: DEBUG shows the data sent in the http request
...
- com.semarchy.commons.sql: with TRACE: SQL executed from workbench and admin
- com.semarchy.commons.mda.persistence.massdelete.ObjectTreeDeleter: With TRACE: displays the delete queries (triggered from execution logs delete) (Semarchy 4.4+).
Platform loggers
- com.semarchy.mdm.datahub.services.query.datamgr.IDataManager: Logs database operations performed by the platform for the MDM applications while browsing data. DEBUG logs all queries and execution times
- com.semarchy.platform.setup.IPlatformManager: Logs platform status changes. INFO traces normal status changes. ERROR traces abnormal statuses
License Synchro loggers
log4j.logger.org.apache.cxf.services.WebClient: with DEBUG (since 5.3 only), logs http exchanges between xdm and license server
Plugins loggers
- com.semarchy.platform.engine.PluginExecution: DEBUG Plugin enrichers and validators feedback, TRACE logs enricher and validation result for all rows
...
- com.semarchy.commons.util.groovy.GroovyEvaluatorService: DEBUG
User access (from KB: Best Practice - configuring user access for a DEV instance)
- log4j.logger.org.springframework.security.ldap=TRACE – New in 5.3 to log both LDAP and AD IDP
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/semarchy].level = ALL
org.apache.catalina.realm.level = ALL
org.apache.catalina.realm.useParentHandlers = true
org.apache.catalina.authenticator.level = ALL
org.apache.catalina.authenticator.useParentHandlers = true
- com.semarchy.tool.jee.tomcat.level = ALL if using the com.semarchy.tool.jee.tomcat.JNDIRealm class
...