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

logLineMaxSize and logLineMaxSize in the log admin REST API #3707

Closed
fgalan opened this issue Oct 26, 2020 · 10 comments
Closed

logLineMaxSize and logLineMaxSize in the log admin REST API #3707

fgalan opened this issue Oct 26, 2020 · 10 comments

Comments

@fgalan
Copy link
Member

fgalan commented Oct 26, 2020

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:

PUT /admin/log?infoPayloadMaxSize=10240
GET /admin/log

{
   "level": "INFO"
   "infoPayloadMaxSize": 10240,
   "lineMaxSize": 32768
}

Each setting is associated to a global variable, so connect them with the existing management API shouldn't be difficult.

@Anjali-NEC
Copy link
Contributor

Hi @fgalan Sir,

I would like to work on this issue, Please assign this issue to me. Thank you.

@fgalan
Copy link
Member Author

fgalan commented Nov 5, 2020

Assigned. Thank you very much!

@Anjali-NEC
Copy link
Contributor

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.

@Anjali-NEC Anjali-NEC removed their assignment May 4, 2021
@Anjali-NEC
Copy link
Contributor

Hi @fgalan Sir,

I am not working on this issue as mention in comment #3707 (comment)

@ArqamFarooqui110719
Copy link
Contributor

Hi @fgalan Sir, I would like to work on this issue, Please assign this issue to me.

I have started the investigation.
Thank you:)

@fgalan
Copy link
Member Author

fgalan commented Feb 24, 2023

@ArqamFarooqui110719 you have been assigned

Thanks for your willingness to work on this issue!

@ArqamFarooqui110719
Copy link
Contributor

Hi @fgalan Sir,
As per my investigation, mainly below 2 functions need to be modified for this issue i.e.

changeLogLevel() and getLogLevel()

in src/lib/serviceRoutinesV2/logLevelTreat.cpp file.

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.

changeLogDetails() and getLogDetails() respectively.

Please let me know your opinion?

@fgalan
Copy link
Member Author

fgalan commented Feb 24, 2023

I'd suggest the following names:

  • changeLogConfig()
  • getLogConfig()

@ArqamFarooqui110719
Copy link
Contributor

I'd suggest the following names:

  • changeLogConfig()
  • getLogConfig()

It looks better. Thanks:)

ArqamFarooqui110719 added a commit to ArqamFarooqui110719/fiware-orion that referenced this issue Feb 28, 2023
fgalan added a commit that referenced this issue Mar 8, 2023
Fix LogConfig in log admin REST API Issue #3707
@fgalan fgalan added this to the 3.9.0 milestone Mar 8, 2023
@fgalan
Copy link
Member Author

fgalan commented Mar 8, 2023

Fixed by PR #4289

@fgalan fgalan closed this as completed Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants