-
Notifications
You must be signed in to change notification settings - Fork 230
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
Enhancement Proposal: Addressing Operations Tab UI Issue with Logger Creation and Level Buttons #1809
Comments
That seems not to be wanted, indeed. |
@aitiqad why did you close the issue? |
I thought, since you have taken this issue into account, I would go ahead and close it. |
Since it is not fixed and I also do not plan on working on a fix, we will keep this issue open. Also a good issue to fix for a small contribution. |
@aitiqad @thjaeckle I would like to work on this issue. Could you please assign it to me? |
Hello @sejal-bansal, once again, sorry |
@thfries Thanks for the update. |
@thjaeckle I also would like clarification on the basic use of the Operations tab. Could you provide me with some information or documentation on it? |
@aitiqad the UI is a "helper" to send DevOps commands, also sometimes referred to as piggyback commands. The Operations tab also allows easily adjusting the log levels dynamically. I am afraid there is no documentation on the UI itself. |
Thank you for the Info @thjaeckle |
There is an issue with the Operations tab UI. I am uncertain whether you have intentionally retained this feature. In the text field for adding a new logger, I suggest disabling the level buttons. I observed that, even when the text box is empty, it is possible to send a PUT request using the buttons, thereby creating an empty logger with associated levels.
The text was updated successfully, but these errors were encountered: