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

Log levels for pvsadm #34

Closed
mkumatag opened this issue Dec 4, 2020 · 2 comments · Fixed by #506
Closed

Log levels for pvsadm #34

mkumatag opened this issue Dec 4, 2020 · 2 comments · Fixed by #506
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@mkumatag
Copy link
Member

mkumatag commented Dec 4, 2020

This task is to set the different log level for the tool, #26 will give us the flexibility to use the different verbose log levels for the tool.

Here is the proposal for defining the log levels for the tool.

Level Purpose
1 Info
2 Debug
3 Trace level 1
4 Trace level 2
5 Function entry and exit

/kind feature

@ltccci ltccci added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 4, 2020
@mkumatag
Copy link
Member Author

mkumatag commented Dec 4, 2020

/cc @bpradipt @bkhadars please review and let me know your opinion.

@mkumatag
Copy link
Member Author

mkumatag commented Dec 4, 2020

/assign

@mkumatag mkumatag added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Dec 7, 2020
@mkumatag mkumatag assigned KeerthanaAP and unassigned mkumatag Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants