Skip to content

FileLogger not using log level correctly #14

@Tri125

Description

@Tri125

Not sure if this is a standard everywhere, but from a logger what I would define as expected usage is that:

  • Any messages below the logger level will not be tracked. It will not be displayed or written to file.
  • Any messages at or above the logger level will be tracked. It will be displayed and/or written to file.

I've set a FileLogger to INFO level. However, one of my Info level messages will not print on console, but it will be written in the file:

 logger.Info(ip, " POST failed validation: ", gridPost)

The above syntax works with fmt.Printf() syntax.

If I switch the message to Warn level, it will still not print on console.

Now, here's where things gets even more interesting.

If I create my FileLogger at WARN level, I still have Info messages being printed out on the console (but not written to file), my Warn messages still doesn't get printed but some are correctly written.

I'm unable to accurately describe examples because it all seems arbitrary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions