-
**Is your feature request related to a problem? Please describe.**
We are exporting logs to datadog, and would like exceptions to show up in a single log line. Via the Datadog guidelines, this requir…
-
**Is your feature request related to a problem? Please describe.**
I'm dealing with non-JSON log files that contain variable-width source file identifiers.
I would like to align log entries using `…
-
### Description
Using the json structured log with the intent to collect them from all containers without having to parse them, the message appears twice in full (bug) plus a third with the origina…
-
In https://github.com/elastic/elasticsearch/pull/96083, we've added a JSON parsing pipeline which is currently not enabled by default.
We didn't enable JSON parsing by default as it comes with a ri…
-
**Is your feature request related to a problem? Please describe.**
A lot of projects are running with a log-server in the background that wants structured data. Today the logging is a bit hard (Both …
-
### 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…
-
# Summary
Add JSON logs parsing into `pod-logs-viewer`
# Motivation
it would be very convenient
# Proposal
On click on log line try to parse it, if it is possible stringify it again but with …
-
**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…
-
## Bug description
I wanted to generate links into pre-filtered logs so I took the logs-with-filters URL and reverse-engineered where I need to parametrize it to show the correct logs.
I discove…
-
### Kyverno Version
1.8.3
### Description
For example:
```json
{
"level": "Level(-4)",
"ts": 1670261642.7125623,
"logger": "webhooks.resource.validate",
"caller": "resource/handlers.g…
jemag updated
1 month ago