You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2018. It is now read-only.
Hi,
I have problem with opbeat reaching the intake server when running opbeat with Django. With Flask I don't have that problem, both running on the same server/environment.
Proxy is set in environment variables. I added so when opbeat/transport/http.py is loaded, it writes the proxies.
This sounds like a bug. Thanks for reporting, we'll investigate! In the meantime (and if your proxy server supports it), could you check if it helps to set the HTTPS_PROXY environment variable to https://wwwproxy.work.se:808 (probably a different port)?
Organization, app and secret token are set, good job!
DEBUG mode is disabled! Looking good!
Opbeat APM middleware not set!
Add it to your MIDDLEWARE_CLASSES like this:
MIDDLEWARE_CLASSES = (
"opbeat.contrib.django.middleware.OpbeatAPMMiddleware",
# your other middleware classes
)
Looks like everything should be ready!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I have problem with opbeat reaching the intake server when running opbeat with Django. With Flask I don't have that problem, both running on the same server/environment.
Proxy is set in environment variables. I added so when opbeat/transport/http.py is loaded, it writes the proxies.
Is there anything I need to configure or missed to test?
The text was updated successfully, but these errors were encountered: