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
When collecting sql SQLqueries to include in sentry reports, it would be need to include the results of ANALYZE on those queries.
This should be ok, performance wise, as usually the sentry report is generated at sent after the response has been sent to the user, but maybe there should be a limit on the number of ANALYZES, and we do them against slowest queries first.
We should only collect these in case of error, using raven's callback api, as while not expensive
The text was updated successfully, but these errors were encountered:
When collecting sql SQLqueries to include in sentry reports, it would be need to include the results of ANALYZE on those queries.
This should be ok, performance wise, as usually the sentry report is generated at sent after the response has been sent to the user, but maybe there should be a limit on the number of ANALYZES, and we do them against slowest queries first.
We should only collect these in case of error, using raven's callback api, as while not expensive
The text was updated successfully, but these errors were encountered: