8000 support reset log level or stack trace level separately for admin log by my-git9 · Pull Request #56642 · istio/istio · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

support reset log level or stack trace level separately for admin log #56642

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

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

my-git9
Copy link
Member
@my-git9 my-git9 commented Jun 14, 2025

Please provide a description of this PR:

Currently there is only one --reset flag to reset the log level for both log and stack trace. It would be better to be able to reset two convenient log levels separately (like --level and --stack-trace-level for each).

To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

  • Ambient
  • Configuration Infrastructure
  • Docs
  • Dual Stack
  • Installation
  • Networking
  • Performance and Scalability
  • Extensions and Telemetry
  • Security
  • Test and Release
  • User Experience
  • Developer Infrastructure
  • Upgrade
  • Multi Cluster
  • Virtual Machine
  • Control Plane Revisions

Please check any characteristics that apply to this pull request.

  • Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@my-git9 my-git9 requested review from a team as code owners June 14, 2025 05:58
@istio-testing istio-testing added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 14, 2025
Signed-off-by: xin.li <xin.li@daocloud.io>
@my-git9
Copy link
Member Author
my-git9 commented Jun 14, 2025

/test integ-ds

@my-git9
Copy link
Member Author
my-git9 commented Jun 14, 2025

/test integ-security-multicluster

@my-git9
Copy link
Member Author
my-git9 commented Jun 15, 2025

/test integ-ds

return &istiodConfigLog{state: &resetState{ctrzClient}}
} else if outputLogLevel != "" {
case logRest:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, does this mean that if both --log-reset and -stracktrace-reset are passed, only the log level will be reset?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a problem. I just added a check to remind users that they cannot specify --log-reset and --stack-trace-reset at the same time.

my-git9 added 2 commits June 24, 2025 11:02
Signed-off-by: xin.li <xin.li@daocloud.io>
Signed-off-by: xin.li <xin.li@daocloud.io>
@my-git9 my-git9 requested a review from Stevenjin8 June 24, 2025 03:08
Copy link
Contributor
@Stevenjin8 Stevenjin8 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay, but is there a reason why we can't pass both flags? Would also be good to have a test for it.

@my-git9
Copy link
Member Author
my-git9 commented Jun 27, 2025

Sorry for the delay, but is there a reason why we can't pass both flags? Would also be good to have a test for it.

No, just an option, I re-evaluated it and specifying both seems better. I have updated and added the test. Please review again, thanks

Signed-off-by: xin.li <xin.li@daocloud.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/user experience size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0