-
Notifications
You must be signed in to change notification settings - Fork 125
Add json log enricher user guide #3001
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
Add json log enricher user guide #3001
Conversation
|
Skipping CI for Draft Pull Request. |
|
/assign @saschagrunert |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3001 +/- ##
===========================================
- Coverage 45.50% 26.56% -18.95%
===========================================
Files 79 125 +46
Lines 7782 20921 +13139
===========================================
+ Hits 3541 5557 +2016
- Misses 4099 15080 +10981
- Partials 142 284 +142 🚀 New features to boost your workflow:
|
82ad5a2 to
58f215b
Compare
|
/retest |
|
/test all |
|
/test e2e-fedora |
|
@ngopalak-redhat: The specified target(s) for Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@saschagrunert Some weird failures. Unable to re-trigger them. After your review, I can rebase and push. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ngopalak-redhat, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Let's merge, that's just docs. Great work, thank you! |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
There are multiple steps to configure json log enricher. The users need to be guided to achieve it.
Which issue(s) this PR fixes:
Does this PR have test?
NA
Special notes for your reviewer:
Does this PR introduce a user-facing change?