question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Reduce trace log levels to just `off|error|verbose`

See original GitHub issue

We have all of these log levels = ‘off’ | ‘error’ | ‘warn’ | ‘info’ | ‘debug’ | ‘verbose’;

Do we need warn|info|debug, why not just have verbose.

@roblourens @rchiodo @DavidKutu @IanMatthewHuff @joyceerhl /cc

Questions:

  • Can we have just one instead of info|debug|verbse
  • Do we even need off, why would we never display errors?

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
roblourenscommented, Aug 23, 2021

😁 image

0reactions
roblourenscommented, Aug 23, 2021

It seems like overkill at this point to have log categories. If you don’t want to see DA messages, you are probably not using the debugging features, and then there will be no DA messages logged.

And when I’m looking at DA logs, I do want to see most kernel logs, it’s just that there are a few that are very verbose, like it is constantly being logged 20 times consecutively. Maybe you know what it means, but it doesn’t seem helpful to me. So I would suggest logging those at a “verbose” level, and logging DA traffic at a “debug” level. But, I would probably prefer we just do your proposal without the categories vs complicating it with categories.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Logging Levels: What They Are & How to Choose Them
The log levels can help to reduce the information noise and alert ... TRACE – the most fine-grained information only used in rare...
Read more >
Log Levels Explained and How to Use Them - Better Stack
Log levels are labels that indicate the severity or urgency of a log entry. This article will help you understand why they are...
Read more >
When to use the different log levels - Stack Overflow
I generally subscribe to the following convention: Trace - Only when I would be "tracing" the code and trying to find one part...
Read more >
Logging levels - IBM
By setting different logging levels for different services you can reduce the amount ... Use Full logging and Trace levels only for detailed...
Read more >
How to Choose Levels of Logging - Section.io
You can use the TRACE log level to query parameters in the code or interpret the algorithm's steps. ALL. This log level logs...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found