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
The current alarms systems is getting triggered according to a percentage of status codes responded in a period of time. As the period of time is pretty short and the alarm gets triggered by 4XXs, any user could trigger an alarm by performing unauthorized requests or trying to access some resource that doesn't exist.
To complete this task: increase the timeframe on which the metrics are computed to a higher interval of time to avoid false positives. We can also remove some 4XXs from the list that we could think of being not useful.
🐛 This is a bug report.
📈 This is a feature request.
The text was updated successfully, but these errors were encountered:
🎉 Description
The current alarms systems is getting triggered according to a percentage of status codes responded in a period of time. As the period of time is pretty short and the alarm gets triggered by 4XXs, any user could trigger an alarm by performing unauthorized requests or trying to access some resource that doesn't exist.
To complete this task: increase the timeframe on which the metrics are computed to a higher interval of time to avoid false positives. We can also remove some 4XXs from the list that we could think of being not useful.
The text was updated successfully, but these errors were encountered: