#89 logging notes and configs for fluentd and vector #994
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #994 +/- ##
=======================================
Coverage 30.97% 30.97%
=======================================
Files 174 174
Lines 38171 38171
Branches 5341 5341
=======================================
Hits 11823 11823
Misses 25194 25194
Partials 1154 1154
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
jiridanek
force-pushed
the
jd_2023_03_12_openshift_logging
branch
from
b8dca44 to
3345850
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here's configs for fluentd and vector to parse skupper-router logs. In either case it consists of a single regexp for the log line plus some fiddling with the timestamp format.
I haven't figured how to use this in OpenShift yet. As far as I found out, OpenShift uses fluentd, elasticsearch, and kibana for its logging. So, hopefully one of these configs can be applied. Or maybe I need to do this in elasticsearch?
Is this good for anything? What are your expectations about the ticket (I guess there are some since it was kept open after the last ticket scrub)?