cannot disable certain fields about quarkus-logging-json

[dfa1]

Closing the issue: solved the problem in another way.

[dfa1]

ah looks like I should use "-" to separate words. This is working fine:

quarkus.log.console.json.fields.timestamp.enabled=false
quarkus.log.console.json.fields.sequence.enabled=false
quarkus.log.console.json.fields.logger-class-name.enabled=false
quarkus.log.console.json.fields.logger-name.enabled=false
quarkus.log.console.json.fields.level.enabled=false
quarkus.log.console.json.fields.message.enabled=false
quarkus.log.console.json.fields.thread-name.enabled=false
quarkus.log.console.json.fields.thread-id.enabled=false
quarkus.log.console.json.fields.process-id.enabled=false
quarkus.log.console.json.fields.process-name.enabled=false
quarkus.log.console.json.fields.hostname.enabled=false
quarkus.log.console.json.fields.mdc.enabled=false
quarkus.log.console.json.fields.ndc.enabled=false
quarkus.log.console.json.fields.stack-trace.enabled=false
quarkus.log.console.json.fields.arguments.enabled=false

[dfa1]

would it be possible to have single switch to disable all fields with a single @ConfigItem? (or any other way to get full control of the output)

In my use-case I must create JSON that is valid against a given schema: any extra field added by a new version of this library, will cause hard to track issues.

[DGuhr]

hey @dfa1 @SlyngDK - just a question, bc maybe I understood it wrong: Is it also possible to disable those fields in the default logger, or do I need to create a custom jsonProvider for that? Would actually be nice to be able to control what fields are spit out by the json logs, but setting e.g.

quarkus.log.console.json.fields.ndc.enabled=false which we don't use for Keycloak, leads to:

{"timestamp":"2022-02-15T12:28:30.111+01:00","sequence":1,"loggerClassName":"org.jboss.logging.Logger","loggerName":"io.quarkus.config","level":"WARN","message":"Unrecognized configuration key \"quarkus.log.console.json.fields.ndc.enabled\" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo","threadName":"main","threadId":1,"mdc":{},"ndc":"","hostName":"dguhr-mac","processName":"QuarkusEntryPoint","processId":10082}

Trying to get rid of mdc/ndc here ;)

Context: I want to provide a wrapper in our config log-json-fields-disabled="..." where people could add a comma-separated list of the fields they don't want in the json logs. Using quarkus 2.7.0 and the mvn package from io.quarkus.

[SlyngDK]

@DGuhr This extension has nothing to do with to default quarkus json logging.
This extension supports more customization, but you have to replace and use this extension.
All config options can be found here https://quarkiverse.github.io/quarkiverse-docs/quarkus-logging-json/dev/index.html

[DGuhr]

uargh, my bad, sorry then :)