You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
shaun-nx opened this issue
Sep 19, 2024
Discussed in
#6436
· 1 comment
Labels
changePull requests that introduce a changegoPull requests that update Go codeproposalAn issue that proposes a feature requestrefinedIssues that are ready to be prioritized
As a user of NGINX Ingress Controller, I would like to have an easier time searching for specific log events so that we can better understand the health of our system and do so in a more performant way
High-level Requirements
Update logging library from golang/glog to log/slog
Add flag to toggle between string and json log parser
Provide a means to use glog as the logging handler for backwards compatibility
Update 3.7.0 release documentation to announce update to log/slog
Definition of Done
Development
Unit tests are written to cover functionality delivered in the story.
Make sure that the unit test passes before creating a pull request.
Make sure that the test coverage stays optimal.
Run make lint locally before creating a PR.
Remove CLI args used for configuring glog levels (eg: deployment.yaml)
Testing
NIC starts and runs
NIC starts and runs (with the service insight and healthcheck options enabled)
Automated tests are written as part of the story.
Run “make lint-python“ from root
Acceptance criteria are met.
Stories are demonstrated to the team.
Product Manager accepts the story as done.
If a feature requires changes/extensions of the Helm chart, those shall be done as part of the story.
Release Notes & Documentation
PR is labeled appropriately so they display in GitHub release notes.
Create/update documentation related to the user story.
Create/update the example in our codebase when applicable.
The content you are editing has changed. Please copy your edits and refresh the page.
The text was updated successfully, but these errors were encountered:
shaun-nx
added
change
Pull requests that introduce a change
proposal
An issue that proposes a feature request
go
Pull requests that update Go code
epic
Issues that need to be broken into smaller issues
ready for refinement
An issue that was triaged and it is ready to be refined
labels
Sep 19, 2024
changePull requests that introduce a changegoPull requests that update Go codeproposalAn issue that proposes a feature requestrefinedIssues that are ready to be prioritized
Overview
As a user of NGINX Ingress Controller, I would like to have an easier time searching for specific log events so that we can better understand the health of our system and do so in a more performant way
High-level Requirements
golang/glog
tolog/slog
string
andjson
log parserglog
as the logging handler for backwards compatibilitylog/slog
Definition of Done
Development
make lint
locally before creating a PR.glog
levels (eg:deployment.yaml
)Testing
service insight
andhealthcheck
options enabled)Automated tests are written as part of the story.Run “make lint-python“ from rootRelease Notes & Documentation
POC Tasks
Implementation Tasks
-v=
to-log-level=
#6620The text was updated successfully, but these errors were encountered: