-
**Is your feature request related to a problem? Please describe.**
**Describe the solution you'd like**
In order to use structured logging and add additional key/values, scorecard.Run() should tak…
-
Hello, I'm seeing log messages like this:
Jul 26, 2019 4:19:10 PM rpc.DefaultConnection processOutgoing
INFO:
Sending REQUEST
...how can I control this log level? I have found these methods:…
-
_Originally posted by @ArchieCoder in https://github.com/unoplatform/uno.extensions/issues/2423#issuecomment-2248723789_
@ArchieCoder suggest changing the log level of these warnings to Debug. This…
-
**Describe the bug**
**To Reproduce**
Steps to reproduce the behavior:
1. Set to `debug`
2. Restart the Harvester pod
3. The log-level reverts to `info`
**Expected behavior**
Persista…
-
**ENHANCEMENT**
1. Describe the enhancement you are requesting. Enhancements include:
Current logger has 3 log levels: `ERROR`, `INFO` and `DEBUG`. Most verbose is of course `DEBUG` level, but it do…
-
**Describe the bug**
Currently in debug logs we get all [INFO]. Can we change it to ERROR or DEBUG too along with respective colors.
**To Reproduce**
Try to generate debug logs
Check .maestr/te…
-
**Is your feature request related to a problem? Please describe.**
To make it easier to debug features, allow the user to set the log level of the container as an environment variable. I think it wou…
-
So this proposal raises a few key questions, most of which have clearly been addressed or are being addressed already.
However, currently I'm unclear about how much data is logged and for how long…
-
I'd like to have the ability to set `log_level` for builtin `Run Process` keyword so that I can specify the loglevel of messages logged by this keyword.
-
Currently logs are overwhelming and not human-readable.
Would be great to sift through the current messages and set appropriate logging levels (also remove sneaky prints that are surely still around…