Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ecamp3-logging: strip prefix "{datetime} std(out|err) F " in fluentd #5378

Merged
merged 2 commits into from
Jul 28, 2024

Conversation

BacLuc
Copy link
Contributor

@BacLuc BacLuc commented Jun 16, 2024


ecamp3-logging: strip prefix "{datetime} stdout F " in fluentd

Before this was done by fluent-bit automatically with the tail clusterinput, when the container engine was set to containerd. Since fluent-operator helm chart 2.8.0, this does not work anymore. -> Thus we do it with fluentd.

After stripping this prefix, we can do the json parsing.


ecamp3-logging: also strip stderr of log messages

This allows us to also parse the messages
of Caddy as json.

Before this was done by fluent-bit automatically with
the tail clusterinput, when the container engine was set to containerd.
Since fluent-operator helm chart 2.8.0, this does not work anymore.
-> Thus we do it with fluentd.

After stripping this prefix, we can do the json parsing.
@BacLuc BacLuc requested a review from a team July 18, 2024 21:13
This allows us to also parse the messages
of Caddy as json.
@BacLuc BacLuc changed the title ecamp3-logging: strip prefix "{datetime} stdout F " in fluentd ecamp3-logging: strip prefix "{datetime} std(out|err) F " in fluentd Jul 28, 2024
@BacLuc BacLuc added this pull request to the merge queue Jul 28, 2024
Merged via the queue into ecamp:devel with commit 6b3a7f4 Jul 28, 2024
34 checks passed
@BacLuc BacLuc deleted the parse-container-log-files-with-fluentd branch July 28, 2024 21:00
This was referenced Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants