Smokedetector: Remove backoff messages

Created on 1 Dec 2016 · 2Comments · Source: Charcoal-SE/SmokeDetector

Is there any reason we can't remove these messages?

screen shot 2016-12-01 at 10 35 04 am

I can't think of any real action we take on them any more. Any actual violations of the backoff should be reported, but just receiving a backoff is a common thing.

Thoughts? Any reason we shouldn't stop posting these?

completed feedback wanted

Source

Undo1

👍4

Most helpful comment

I don't have any issues with removing these, but I think it would be good to still have them logged in a human-accessible place for debugging purposes.

E.g. we could log them in errorlogs.txt, or we could create a new log file + command entirely.

Alternatively, we could add a summary of backoffs that is printed when the API quota rolls over. E.g. 3 Backoffs received today at 3:42, 12:45 and 19:59. See !!/errorlogs for details

angussidney on 1 Dec 2016

👍4

All 2 comments

I don't have any issues with removing these, but I think it would be good to still have them logged in a human-accessible place for debugging purposes.

E.g. we could log them in errorlogs.txt, or we could create a new log file + command entirely.

Alternatively, we could add a summary of backoffs that is printed when the API quota rolls over. E.g. 3 Backoffs received today at 3:42, 12:45 and 19:59. See !!/errorlogs for details

angussidney on 1 Dec 2016

👍4

I'm removing them; planning to record them in metasmoke when we get a better analytics/events platform built.

Undo1 on 2 Dec 2016

Was this page helpful?

0 / 5 - 0 ratings