Skip to Content
  2. Mailing Lists
  3. Contributors
  4. suggestion for monitoring error 500

Archives

Contributors

Download Sale Orders from Magento 2.3 to Odoo14

OCA/bank_statement_import - Odoo 16, Switzerland

suggestion for monitoring error 500

Hi,

We have a case where odoo is used as an e-commerce + portal system (with quite a lot of customisation).
Times to times, the end user (e-commerce customer) will receive an error 500.

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 ?
Or could we "monitor" the log file ? <-- any suggestion on possible tool ?

Thanks,
Dominique
by dominique.k - 07:21 - 1 May 2023

Follow-Ups

  • Re: suggestion for monitoring error 500
    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

    by Tom Blauwendraat - 05:56 - 1 May 2023
  • RE: suggestion for monitoring error 500

    Hi Dominique,

    I normally use the try … except like below:

     


    try:

     

    except Exception as e:

        mail_smtp_server = self.env["ir.mail_server"].sudo().search([], limit=1)

        email_vals = {"state": "outgoing" ,

            "subject": str(self.env.cr.dbname) + " Error in demo 1 controller  " ,

            "body_html": """Error in demo 1 controller  :  """ + str(e.message) + " " + str(e.args) ,

            "auto_delete": True,

            "email_from": mail_smtp_server.smtp_user ,

            "email_to": madeb@regious.co.zw ,

            }

        self.env["mail.mail"].create(email_vals)

     

     

    Regards,

     

    Bill Made

    +263 733 419 060

     

     

     

    From: Dominique k <notifications@odoo-community.org>
    Sent: Monday, May 1, 2023 7:29 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: suggestion for monitoring error 500

     

    Hi,

     

    We have a case where odoo is used as an e-commerce + portal system (with quite a lot of customisation).

    Times to times, the end user (e-commerce customer) will receive an error 500.

     

    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 ?

    Or could we "monitor" the log file ? <-- any suggestion on possible tool ?

     

    Thanks,

    Dominique

    by Bill Made - 08:51 - 1 May 2023
  • Re: suggestion for monitoring error 500 
    > 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
    by Holger Brunn - 07:56 - 1 May 2023

    1 attachments 1 attachments

    signature.asc