ayhan.rashidov

ayhan.rashidov

Elixir Log Files - how to log info only?

Hello, when I use this for logging in the error.log file I get only error logs but in the info file there are both info and error logs. How can I make it log only info?

config :logger,
  backends: [{LoggerFileBackend, :info},
             {LoggerFileBackend, :error}]

config :logger, :info,
  path: "/path/to/info.log",
  level: :info

config :logger, :error,
  path: "/path/to/error.log",
  level: :error

First 9 of 9 Posts Switch mode

tckb

tckb

may be trying changing the name of backend?

config :logger,
  backends: [{LoggerFileBackend, :info_log},
             {LoggerFileBackend, :error_log}]

config :logger, :info_log,
  path: "/path/to/info.log",
  level: :info

config :logger, :error_log,
  path: "/path/to/error.log",
  level: :error
ayhan.rashidov

ayhan.rashidov OP

Still works fine only for error logs.

tspenov

tspenov

Looking at the docs https://github.com/onkel-dirtus/logger_file_backend, I think that adding metadata_filter that corresponds to {LoggerFileBackend, :info} should work:

config :logger, :info,
  path: "info.log",
  level: :info,
  metadata_filter: [application: :info]
tckb

tckb

wouldn’t that force you add a metadata for each log message?
as in

Logger.info("log log log",application: :info)

ayhan.rashidov

ayhan.rashidov OP

Now it doen’t even create the files.

ayhan.rashidov

ayhan.rashidov OP

It seems to work fine using the third example.

# in a config file:
config :logger,
  backends: [{LoggerFileBackend, :device_1}]

config :logger, :device_1
  path: "/path/to/device_1.log",
  level: :debug,
  metadata_filter: [device: 1]

# Usage:
# anywhere in the code:
Logger.info("statement", device: 1)
tspenov

tspenov

Yes, seems my assumption is wrong :(. Seems that metadata_filter works only when you add the metadata directly in the log message.

tckb

tckb

err, @ayhan.rashidov I am wrong, this is not a bug. Actually, the data you see is 100% correct. When you mention logging level info all the logs that are less or equal to the verbosity will be logged regardless of the backend.

Verbosity levels:
debug > info > warn > error

so “info” level will log all info, warn and error logs and “warn” will log all warn & error logs ., etc.

if you really want only error logs to a file and only info logs in one log ( I would advice against it) . you can use metadata.

config :logger,
  backends: [{LoggerFileBackend, :info},
             {LoggerFileBackend, :error}]

config :logger, :info,
  path: "/path/to/info.log",
  level: :info,
  metadata_filter: [level: :info]

config :logger, :error,
  path: "/path/to/error.log",
  level: :error,
  metadata_filter: [level: :error]

and you may use like –

Logger.info("This is info log",level: :info)
Logger.error("This is info log",level: :error)

— All posts loaded —

Where Next?

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
silverdr
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated! To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead. Sta...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
michallepicki
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
type1fool
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
akoutmos
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New

We're in Beta

About us Mission Statement