-
Currently, Zeek uses hex escapes (\x00) to escape non-printable characters (and possibly others) in both TSV and JSON logs.
For TSV, this is fine. However, because JSON requires strict UTF-8 adherenc…
-
### What's wrong?
The JSON generated from https://github.com/grafana/alloy/blob/main/operations/alloy-mixin/dashboards/alloy-logs.libsonnet is broken and throws an error `Status: 500. Message: pars…
-
I love your tool, thank you for your work!
Two features that would be nice to have:
1. Maybe it is something wrong with my terminal (Alacritty) but I can't copy logs from console to send them som…
-
I'm getting this error trying to run OOProlog on a Kensington firmware update utility:
```
Consistency checks failed.
Class 0x587970 inherits from 0x569a4c at offsets 0 and 0x244
Initial sanity …
-
**Is your feature request related to a problem? Please describe.**
Hello.
All my pods logs messages in json to the standard output.
I'd like to see parsed logs with `k9s` if possibl…
-
### What happened?
We've been running Load Tests for quite a while using normal text based logs to stdout, when our team has rewritten the log framework to use a lot of details and started using json…
-
**Desired feature or idea**: What would you like to see happen?
We are adding OTEL standards to our project and need to check if our output format supports the current and future log schemes.
We nee…
-
**Describe the bug**
Using the OpenSearchJsonLayout for logging out of a docker container adds newlines in the generated json-string when a stack-trace is appended. This makes it unnecessarily hard t…
-
I'm following the guide to use logdy with journald logs, but I am running into a seemingly dumb roadblock. My service logs in JSON format, so the `MESSAGE` field returned by `journalctl -o json` conta…
CAFxX updated
22 hours ago
-
AppSignal can attempt to parse the logs that are sent to it as JSON or Logfmt. It would be useful if the same flag that triggers attempting this parsing could be sent alongside the logs, perhaps media…