Investigate how we can optimize the performance of DB queries when alerting gets triggered by the quota feature. My customer is seeing that when their customers hit the quota limit, it starts causing 502 errors for them. They were able to stop the errors by increasing the limits which then stopped the alerting. This suggests that the quota feature itself isn't too much for their DB and perhaps alerting can be optimized.

They are at the maximum resource size in their OSP environment for their DB server. They cannot get more resources for their DB unless they re-architect their deployment.