question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

LOG_LEVEL change ingnored in v1.3.2

See original GitHub issue

Hello,

if I change LOG_LEVEL in deployment of apicurio-streams image 1.3.2.Final to “DEBUG” like in example below, the log output level of k8s pod is not changed.

spec:
  containers:
    env:
      - name: LOG_LEVEL
         value: "DEBUG"

It works okay in latest-snapshot version, it works okay in red hat 1.0.0 version, but not in this 1.3.2.Final. Unfortunately in some environments I should only use latest Final version in my organization.

I tried the same with QUARKUS_LOG_LEVEL, or with adding JAVA_OPTS parameter -D%prod.quarkus.log.level=DEBUG, but nothing changed.

Is there any other option/workaround to raise log level in v1.3.2, or just wait until higher Final version is released?

Thank you, Peter

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
famartingcommented, Feb 18, 2021

have you tried -Dquarkus.log.level=DEBUG ?

0reactions
EricWittmanncommented, Feb 22, 2021

Interesting, thanks for following up on this @petolexa ! @smccarthy-ie is it worth adding a documentation footnote about this?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Spring debug logging level not working - Stack Overflow
springframework.web.servlet.view.tiles3.TilesConfigurer$CompositeELResolverImpl class will be ignored. The annotations could not be obtained ...
Read more >
Logger v1.12.3 - HexDocs
:level - the logging level. Attempting to log any message with severity less than the configured level will simply cause the message to...
Read more >
Log4j2 Example Tutorial - Configuration, Levels, Appenders
If Log4j2 doesn't find the configuration file, only Root Logger will be used for logging with logging level as ERROR. Below image shows...
Read more >
Changing the logging level - IBM
The logging level for the application can be changed to generate helpful information for identifying and solving issues with this application.
Read more >
Log4j – Changes - Apache Logging Services
Allow trailing and leading spaces in log level. Fixes LOG4J2-2793. Thanks to Renukaprasad C. rgoers. Update, Add support for specifying an SSL ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found