Need


Change the loggers' configuration to be able to grab more detailed logs.


Summarized Solution


Using the platform CLI, you can use the following commands:

# Retrieve the actual configuration
sem dm admin logging --json > loggingconfig.json
# Edit it and set it
sem dm admin logging set -i loggingconfig.json


More details about the commands can be found in the documentation.


Detailed Solution


The user need the System admin role to runs the commands!


1. First, set up and authenticate the CLI:


Set up the Semarchy Platform CLI following the documentation.
Authenticate using:

sem auth login <url>


This command outputs a link to open with your web browser. Authenticate in your web browser, and come back to the terminal.


You are now authenticated!

You can now access the actual logging configuration of the DM module on the Semarchy Data Platform:

sem dm admin logging


The result of this command should look like:

com.semarchy: INFO
com.semarchy.commons.sql: INFO
com.semarchy.mdm.datahub.services.query.datamgr.IDataManager: INFO
com.semarchy.mdm.dataui.domain.dataexport: INFO
com.semarchy.mdm.dataui.domain.dataimport: INFO
com.semarchy.platform.engine: INFO
com.semarchy.platform.engine.PluginExecution: INFO
com.semarchy.platform.engine.core.impl.product.SL4JExecutionMonitor: INFO
com.semarchy.platform.product.notification.PlatformNotificationHandler: INFO
com.semarchy.platform.repository.domain.restclient.RestClientInstance: INFO
com.semarchy.platform.setup.IPlatformManager: INFO
com.semarchy.ui.platform.console.actions.CheckConsistencyAction: INFO
com.semarchy.xdm.rest.accesslog: INFO
com.sun.xml: INFO
com.zaxxer.hikari: INFO
jakarta.xml.bind: INFO
org: INFO
org.apache.aries.blueprint: WARN
org.apache.aries.blueprint.container: WARN
org.apache.aries.blueprint.container.BlueprintContainerImpl: "OFF"
org.apache.aries.blueprint.container.ServiceRecipe: "OFF"
org.apache.aries.spifly: WARN
org.apache.commons.beanutils.converters: WARN
org.apache.cxf: WARN
org.apache.cxf.jaxrs.impl.WebApplicationExceptionMapper: ERROR
org.apache.cxf.services: WARN
org.apache.cxf.services.WebClient: WARN
org.apache.directory.shared.asn1.ber.Asn1Decoder: ERROR
org.apache.jasper.servlet: INFO
org.apache.kafka: WARN
org.ops4j.pax.logging: WARN
org.quartz: WARN
org.springframework.jdbc.core.JdbcTemplate: WARN
org.springframework.jdbc.core.StatementCreatorUtils: WARN
 
REST API call successful


 2. Export the logging configuration in a JSON format, modify it, and then import it into the platform.

sem dm admin logging --json > loggingconfig.json


You can modify the JSON file according to your needs, and then you can set the logging configuration using the JSON file.

sem dm admin logging set -i loggingconfig.json


3. Finally, after checking the now-more-detailed logs, you can reset the logging configuration. This can be crucial, as some loggers can noticeably slow down the application:

sem dm admin logging reset