Log Level on "info" despite configured otherwise

Are you using correct MIX_ENV?

I am not setting it explictly, just running iex -S mix. Should I be doing this? If so, where and how?

Checking the env tells me that its in dev mode: (which is what I want, I am on my development machine)

iex(3)> Mix.env
:dev

In which file is your logger config? And is that file actually loaded from your config.exs.

My config is in a file called sys.exs. This file is loaded in the first line of my config.exs. The file also contains several other options (such as the Ecto Repo, etc.) which are working.

use Mix.Config

import_config "sys.exs"

Interestingly enough, all values other than the log level are also loaded:

iex(3)> Application.get_env :logger, :level
:info
iex(4)> Application.get_env :logger, :console
[metadata: :all, level: :debug, format: {Sahnee.Logger, :format}]

There also do not seem to be any other places where this config value is changed:

image240×191 7.4 KB

What happens if you switch from use Mix.Config to import Config?

Same result, all config values except this single one are applied:

iex(1)> Application.get_all_env :logger
[
  utc_log: false,
  translator_inspect_opts: [],
  compile_time_application: nil,
  handle_sasl_reports: false,
  truncate: 8096,
  compile_time_purge_level: :debug,
  level: :info, # <--
  sync_threshold: 20,
  discard_threshold_for_error_logger: 500,
  handle_otp_reports: true,
  discard_threshold: 500,
  console: [metadata: :all, level: :debug, format: {Sahnee.Logger, :format}],
  compile_time_purge_matching: [],
  backends: [:console],
  discard_threshold_periodic_check: 30000,
  translators: [
    {Plug.Cowboy.Translator, :translate},
    {Logger.Translator, :translate}
  ]
]

config.exs:

#use Mix.Config
import Config

import_config "sys.exs"

# snip...

sys.exs:

#use Mix.Config
import Config

# snip...

config :logger,
  level: :debug

config :logger, :console,
  metadata: :all,
  level: :debug,
  format: {Sahnee.Logger, :format}

# snip...

What is in # Snip parts? Are you sure that you do not set that key to different value later?

Unfortunately not, no. I posted a screenshort earlier where I searched for :logger in my entire project. The term has only three occurences: Two for the two config entries posted above and one in extra_application to actually start the logger (I think, been a while since I set it up).

image256×206 8.71 KB

image535×146 12.7 KB

image396×150 10.8 KB

If you absolutely want to see the full config I can post it, but since its roghly 150 lines I’d prefer to spare you the wall of text. (Also worried about forgetting to remove a production secret :D)

Just use paste bin. However it is hard to tell you where the bug can be. Unfortunately logger isn’t external application so it isn’t that simple to edit it.

Try searching for Logger, maybe there is some rouge call that changes it in the application itself.

• config.exs: config.exs - Pastebin.com
• sys.exs: sys.exs - Pastebin.com
• local.exs: I cannot post this file under any circumstances since its only purpose is to store secrets that should not be commited to git. (Neither :logger nor Logger are used or configured within this file.)

Try searching for Logger , maybe there is some rouge call that changes it in the application itself.

Which terms would be of interest to search? It’s a large application (by my standards) so there are hundrets of Logger calls. Logger.configure is not called. Asides from normal log statements a lot of metadata is being set, but no metadata entry is called level or contains the value info if that could be a culprit.

Thanks to everyone who has posted so far. This is probably going to be an embarassing “oops” kind of mistake that I made, but the source of it eludes me.