[18.0][IMP] server logs and profiling #589
Draft
+74
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This allows to use the same syntax than the existing one from rest.log.active to define other config parameters.
Werkzeug logs are only generated when Odoo answers HTTP requests, whereas this will allow to know whenever a request is dispatched through rest services.
Leverage ir.profile machinery to track what happens when a user calls some rest services. Since profiling can be done only for a single user at a time the system parameter rest.log.profiling.uid has to be defined with the ID from res.users whose calls need to be profiled. Moreover, system parameter rest.log.profiling.conf can be defined using the syntax from rest.log.active to fine tune which requests will trigger the profiling for the user defined by the previous parameter. To note, once a request is identified to start the profiling, all incoming requests from the user will be profiled until the timeout duration defined by rest.log.profiling.duration is reached.
Contributor
|
Hi @simahawk, |
simahawk
reviewed
Feb 11, 2026
Contributor
simahawk
left a comment
simahawk
left a comment
There was a problem hiding this comment.
early review, to be tested.
| _log_calls_in_db = False | ||
|
|
||
| def dispatch(self, method_name, *args, params=None): | ||
| if self._server_debug_logging_active(method_name): |
Contributor
There was a problem hiding this comment.
I wonder if we really need an IF here. All in all we can control this with debug levels.
| profiling_duration = 10 | ||
| try: | ||
| profiling_duration = int( | ||
| self.env["ir.config_parameter"] |
Contributor
There was a problem hiding this comment.
Do we really need to take care of such params?
We can simply set base.profiling_enabled_until when we set the other params.
We'll reduce complexity here. In fact, we could simply check if profiling is enable by calling ir.profile._enabled_until()
simahawk
reviewed
Feb 11, 2026
| _logger.warning( | ||
| "System parameter rest.log.profiling.duration is not defined. Profiling will be active for the next 10 minutes" | ||
| ) | ||
| profiling_enabled_until = fields.Datetime.now() + relativedelta( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[REF] rest_log: Add hooks to read configuration from system params
This allows to use the same syntax than the existing one from
rest.log.active to define other config parameters.
[IMP] rest_log: Allow printing server logs on incoming requests
Werkzeug logs are only generated when Odoo answers HTTP requests,
whereas this will allow to know whenever a request is dispatched
through rest services.
[IMP] rest_log: Allow to profile requests through rest services
Leverage ir.profile machinery to track what happens when a user
calls some rest services.
Since profiling can be done only for a single user at a time the
system parameter rest.log.profiling.uid has to be defined with
the ID from res.users whose calls need to be profiled.
Moreover, system parameter rest.log.profiling.conf can be defined
using the syntax from rest.log.active to fine tune which requests
will trigger the profiling for the user defined by the previous
parameter.
To note, once a request is identified to start the profiling, all
incoming requests from the user will be profiled until the timeout
duration defined by rest.log.profiling.duration is reached.