Warn about SMS failures when it's cost effective

Previously we warned when as little as 100 SMS messages failed, which
equates to £1.60 in cost. This increases the absolute threshold so that
we avoid taking action when the cost in developer time is greater than
the money wasted. If it takes us an hour to solve the ticket, then that
equates to roughly £100 in people costs.

In future, we should also consider simplifying this check to be about
permanent failures in general.
This commit is contained in:
Ben Thorner
2021-04-26 13:51:34 +01:00
parent 5f26d16915
commit 89cea9a2e7
3 changed files with 6 additions and 6 deletions

View File

@@ -564,9 +564,9 @@ MockServicesWithHighFailureRate = namedtuple(
],
[
[],
[MockServicesSendingToTVNumbers("123", 300)],
"1 service(s) have sent over 500 sms messages to tv numbers in last 24 hours:\n"
"service: {}/services/{} count of sms to tv numbers: 300,\n".format(
[MockServicesSendingToTVNumbers("123", 63_000)],
"1 service(s) have sent high volumes of sms messages to tv numbers in last 24 hours:\n"
"service: {}/services/{} count of sms to tv numbers: 63000,\n".format(
Config.ADMIN_BASE_URL, "123"
)
]