-
Notifications
You must be signed in to change notification settings - Fork 266
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
logLineMaxSize and logLineMaxSize in the log admin REST API #3707
Comments
Hi @fgalan Sir, I would like to work on this issue, Please assign this issue to me. Thank you. |
Assigned. Thank you very much! |
Hi @fgalan sir, I have done investigation on this issue. As per my understanding we need to add PUT and GET method for logLineMaxSize and logInfoPayloadMaxSize in log admin API. To GET logLineMaxSize and logInfoPayloadMaxSize we need to modify serviceRoutinesV2/logLevelTreat.cpp and add "lmLogLinesGet" method for getting logLineMaxSize but I have not found something for PUT method. Currently I am leaving this issue, and working on another issue. |
Hi @fgalan Sir, I am not working on this issue as mention in comment #3707 (comment) |
Hi @fgalan Sir, I would like to work on this issue, Please assign this issue to me. I have started the investigation. |
@ArqamFarooqui110719 you have been assigned Thanks for your willingness to work on this issue! |
Hi @fgalan Sir,
in I think these function names were given only for the "Log Level" functionality. As now we are modifying the functions and adding new details so these function names should also be change. For e.g.
Please let me know your opinion? |
I'd suggest the following names:
|
It looks better. Thanks:) |
Fix LogConfig in log admin REST API Issue #3707
Fixed by PR #4289 |
In the re-work done in issue #3694 the following parameters were introduced in the CLI:
-logLineMaxSize
-logInfoPayloadMaxSize
It could be a good idea to include them in the log admin API, so they can be dyncamically changed, allowing things like this:
Each setting is associated to a global variable, so connect them with the existing management API shouldn't be difficult.
The text was updated successfully, but these errors were encountered: