Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

set log level doesn't work for standalone mode #302

Open
Gordiievskyi opened this issue Aug 28, 2020 · 0 comments
Open

set log level doesn't work for standalone mode #302

Gordiievskyi opened this issue Aug 28, 2020 · 0 comments

Comments

@Gordiievskyi
Copy link

Gordiievskyi commented Aug 28, 2020

Describe the bug
Log level isn't set by yaml as documentation states git docs.

First want to say thanks for doing this great project.
Guys I realy need it to debug, I have a very strange errors when part of content is missing but info level do not show anything

To Reproduce
Steps to reproduce the behavior:

  1. Download proxy zip
  2. Unpack zip and navigate inside the folder
  3. Navigate to bin folder.
  4. Create conf folder
  5. Create bup-logging.yaml with content:
Configutation:
    name: Default
    Appenders:
      Console:
        name: Console_Appender
        target: SYSTEM_OUT
    Loggers:
      Root:
        level: warn
        AppenderRef:
          - ref: Console_Appender
      Logger:
        - name: com.browserup.bup
          level: warn
          AppenderRef:
            - ref: Console_Appender
  1. Start you proxy ./browserup-proxy-2.0.1/bin/browserup-proxy

Actual result:
[INFO 2020-08-28T14:57:26,184 com.browserup.bup.proxy.Main] - default info level still applied.

Expected behavior
no message appears and log level is warn

Screenshots
If applicable, add screenshots to help explain your problem.

Please complete the following information:

  • OS: MAC OS 10.14.6
  • not applied
  • Version browserup-proxy-2.0.1

Additional context
Java 1.8.0_231-b11

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant