This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 29
JSONResponseError: 400 Bad Request #703
Comments
Updated sentry link: https://sentry.prod.mozaws.net/operations/autopush-prod/issues/358260/ |
I see sentry entries for db calls: all_channels, fetch_messages, fetch_notifications, register_user These come from websocket. endpoint/web.base already traps the parent BotoServerError track_provisioned should increase a metric and reraise, then websocket can handle as it likes |
pjenvey
added a commit
that referenced
this issue
Oct 20, 2016
have websocket log them instead of passing along to sentry and give them a metric closes #703
pjenvey
added a commit
that referenced
this issue
Oct 20, 2016
have websocket log them instead of passing along to sentry and give them a metric closes #703
pjenvey
added a commit
that referenced
this issue
Oct 20, 2016
have websocket log them instead of passing along to sentry and give them a metric closes #703
actually any db call can trigger this https://sentry.prod.mozaws.net/operations/autopush-prod/issues/360478/ |
pjenvey
added a commit
that referenced
this issue
Oct 20, 2016
have websocket log them instead of passing along to sentry and give them a metric closes #703
pjenvey
added a commit
that referenced
this issue
Oct 20, 2016
have websocket log them instead of passing along to sentry and give them a metric closes #703
bbangert
pushed a commit
that referenced
this issue
Oct 20, 2016
have websocket log them instead of passing along to sentry and give them a metric closes #703
jrconlin
pushed a commit
that referenced
this issue
Oct 21, 2016
have websocket log them instead of passing along to sentry and give them a metric closes #703
jrconlin
added a commit
that referenced
this issue
Oct 21, 2016
have websocket log them instead of passing along to sentry and give them a metric closes #703
jrconlin
added a commit
that referenced
this issue
Oct 21, 2016
have websocket log them instead of passing along to sentry and give them a metric closes #703
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Occasionally requests have a token error, these should be caught since they're not addressable bugs.
Most likely in track_provisioned so they can be logged out appropriately for ops to look at if desired.
See: https://sentry.prod.mozaws.net/operations/autopush-prod/issues/358013/
The text was updated successfully, but these errors were encountered: