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.
Change logging to warning or error
See original GitHub issue⚠️ Please verify that this bug has NOT been raised before.
- I checked and didn’t find similar issue
🛡️ Security Policy
- I agree to have read this project Security Policy
📝 Describe your problem
Uptime-kuma writes a new line to stdout for each measurement.
This makes very frequent writes.
Would be nice to set log levels to either of DEBUG, INFO, WARN or ERROR, if that’s not already possible.
🐻 Uptime-Kuma Version
💻 Operating System and Arch
🌐 Browser
🐋 Docker Version
No response
🟩 NodeJS Version
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:8 (2 by maintainers)
Top Results From Across the Web
When to use the different log levels - Stack Overflow
For me, you should start with DEBUG , INFO , WARNING and ERROR . Developers should see all levels. SysAdmins up to INFO...
Read more >Log Levels Explained and How to Use Them - Better Stack
You can change this to WARN if you only want to record events that indicate problems or potential problems.
Read more >Logging Levels: What They Are & How to Choose Them
WARN – the log level that indicates that something unexpected happened in the application, a problem, or a situation that might disturb one...
Read more >Changing the logging level - IBM
Changing the logging level ; ERROR: Shows only error messages. No warnings or informational messages is provided. ; WARN: Shows only error and...
Read more >Logging HOWTO — Python 3.11.1 documentation
These are debug() , info() , warning() , error() and critical() . To determine when to use logging, see the table below, which...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Any news on this @ivanbratovic @louislam?
Especially on devices like Raspberry Pi it would be nice to have as few write accesses as possible. However, the logs become significantly large with many monitors due to the log level. It would be nice if this could be configured via environment variables.
This is related to a currently open PR #910