-
I have an Android project with 124 modules and use Jetifier that used Artifact transform API, so essentially all Android modules use it (more than 100 in my case) and I see multiple logs per each arti…
-
### What happened?
When opening the log query type in the Elasticsearch explorer, log levels are not recognized in the volume query. See attached screenshot.
### What did you expect to happen?…
-
## Summary
Before outputting Elasticsearch logs to the terminal, `@kbn/es` parses them to add text color codes based on the message level (see `parse_es_logs.ts`), and it works great. The only issu…
-
I think we use logging.warning when we should be doing logging.debug
-
I been working on an extensions that utilizes the `OutputChannel` API for logging things into the output view for different log levels such as: `INFO`, `ERROR`, etc...
Each of these log…
-
Our logs are fairly verbose, re-evaluate which log levels to use for which messages. Our logger has the [following levels available](https://docs.python.org/3/library/logging.html#levels) (also below)…
-
```
% journalctl -u neofs-storage.service -p err
-- No entries --
```
The `No entries` is wrong answer, because there are:
```
% journalctl -u neofs-storage.service | grep error | wc -l
1…
-
**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…
-
### What happened?
Setting a log level in config.js appears to work for jitsi-meet itself, but lib-jitsi-meet still uses the info level.
Probably due to , which appears to run _after_ the config h…
-
**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…