Bug 1788228 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
This Sentry event is for "timeout" in pymemcache presumably on `/__lbheartbeat__`:

https://sentry.io/organizations/mozilla/issues/3546766253/

However, there are several instances in that issue where the meta information for the issue is related to SuperSearch.

Seems like when the timeout happens, Sentry client is picking up information from a different thread or something like that.

Is the Sentry client set up correctly? Are we hitting a Sentry client bug?
Revision 1 by
on 
This Sentry event is for "timeout" in pymemcache presumably on `/__lbheartbeat__`:

https://sentry.io/organizations/mozilla/issues/3546766253/

However, there are several instances in that issue where the transaction information (url, http headers, query string, transaction, etc) for the issue is for a SuperSearch request which has a different stack.

Seems like when the timeout happens, Sentry client is picking up information from a different thread or something like that.

Is the Sentry client set up correctly? Are we hitting a Sentry client bug?

Back to Bug 1788228 Comment 0