1. Mailing Lists
  2. Contributors
  3. Re: suggestion for monitoring error 500

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

RE: suggestion for monitoring error 500

Avatar

Re: suggestion for monitoring error 500

by
Therp, Tom Blauwendraat
- 01/05/2023 17:53:52
Hi Dominique

If you have Odoo running behind NGINX, you can parse the access log file to get some statistics about the timestamps around which this occurs, and on which urls. I have a way of doing that with command line tools such as "awk", "sort" and "uniq" (for hourly statistics), but regular "grep" can also yield you the info.

Armed with that knowledge you can then check the Odoo log file around those times, sometimes it will also display "Internal error" or even a useful traceback, and you can then use "grep" again to extract relevant patterns over the course of a day or so.

If not enough information is given, then you could resort to modifying the Odoo source code to add some more exception-catching.

1 mei 2023 06:57:22 Holger Brunn <notifications@odoo-community.org>:

> It is a bit of a catchall... Would anybody have any suggestion, to monitor

> such error, and possibly get an email, or a warning as a system

> administrator? Is there a way to catch at odoo level, if there is such

> error and send an email ?

all requests go through
https://github.com/OCA/OCB/blob/16.0/odoo/addons/base/models/ir_http.py#L153
so that seems the best place to catch your exception


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Reference