I might be doing something stupid here, if so, apologies, but I have this logging conf

Please show me some of that. <a href="htt

File not logging at INFO about dropwizard HOT 7 CLOSED

dropwizard commented on May 13, 2024

File not logging at INFO

from dropwizard.

Comments (7)

codahale commented on May 13, 2024

What are the levels of the statements you see when you change the threshold to ALL?

from dropwizard.

dehora commented on May 13, 2024

Ah; nothing, unless logging/level is DEBUG. I removed the loggers to get to this

logging:
  level: INFO
  file:
    enabled: true
    threshold: ALL
    currentLogFilename: migration.log
    archivedLogFilenamePattern: migration-%d.log.gz
    archivedFileCount: 5
    timeZone: UTC

Otoh, This will log to file

logging:
  level: DEBUG # @@@
  file:
    enabled: true
    threshold: ALL
    currentLogFilename: migration.log
    archivedLogFilenamePattern: migration-%d.log.gz
    archivedFileCount: 5
    timeZone: UTC

But also outputs jersey/jetty, which I'm trying to skip.

from dropwizard.

codahale commented on May 13, 2024

You said "If I change file/threshold to DEBUG/ALL, I see file logging." Please show me some of that.

from dropwizard.

codahale commented on May 13, 2024

I think you might just want to leave the thresholds alone and use a specific logger for your application:

logging:
  loggers:
    com.myapp.service: ALL

from dropwizard.

dehora commented on May 13, 2024

Please show me some of that.

https://gist.github.com/2dd4540d760a84293300

leave the thresholds alone

Can't get any file logging without logging/level. I can set these to reduce noise,

com.sun.jersey: WARN
com.yammer.dropwizard: WARN
org.hibernate.validator: WARN

But if i do this,

org.eclipse.jetty: WARN

No logging to file. Logs to file -

logging:
  level: DEBUG
  loggers:
    net.amadan.sal.migration: INFO
    com.sun.jersey: WARN
    com.yammer.dropwizard: WARN
    org.hibernate.validator: WARN
  file:
    enabled: true
    currentLogFilename: migration.log
    archivedLogFilenamePattern: migration-%d.log.gz
    archivedFileCount: 5
    timeZone: UTC

Does not log to file -

logging:
  level: DEBUG
  loggers:
    net.amadan.sal.migration: INFO
    com.sun.jersey: WARN
    com.yammer.dropwizard: WARN
    org.hibernate.validator: WARN
    org.eclipse.jetty: WARN # ಠ_ಠ 
  file:
    enabled: true
    currentLogFilename: migration.log
    archivedLogFilenamePattern: migration-%d.log.gz
    archivedFileCount: 5
    timeZone: UTC

Am fairly sure I'm doing something stupid.

from dropwizard.

codahale commented on May 13, 2024

You might want to read the Logback documentation to learn how it works.

I would suggest using this configuration:

logging:
  loggers:
    net.amadan.sal.migration: DEBUG
  file:
    enabled: true
    currentLogFilename: migration.log
    archivedLogFilenamePattern: migration-%d.log.gz
    archivedFileCount: 5
    timeZone: UTC