When using SUDS in a Django app, alongside Sentry error logging, I hit a problem where SUDS raises an error and Sentry tries to handle it, fails horribly and causes a server 500:
I\'m looking into setting up Sentry for my Django project, but I was wondering whether to install the Sentry server along with my main webapp, or in a separate web instance.
I have installed Sentry for messages logging. I am new to sentry so i don\'t how it works. Does it logs only those messages which put in my files with logger (\"error something\") or whatever error o
I am adding a sentry handler to the R logging package.currently django-sentry validates the client (the application sending log records) based on a shared key which travels in clear text in a secured
I just installed django-sentry, and it catches exceptions just fine. However calls to logger.warning and logger.error are not being saved to Sentry for some reason.
I\'m running django-sentr开发者_高级运维y successfully in our staging and production environments, but on my development instance sentry doesn\'t appear to be logging.
I have a custom 500 hander to use with sentry. In my urls.py file i have: def handler500(request): \"\"\"
I have created in magento 2 shops with 1 common shopping cart. If I am a visitor an开发者_开发知识库d add to cart 1 product from 1st store and then go to 2nd store the cart reset.I saw on gap.com that
I suddenly started to get an error on my sentry logs for two particular errors... it appeared all of the them are fr开发者_如何学运维om chrome 87 on Android: