ayhan.rashidov

ayhan.rashidov

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

Showing Posts 1 to 9

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? Top

Trending in Questions Top

Blokh
Hey guys, I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly Do you guys have any suggestions what is the best prac...
New
RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
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
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews