Interesting pointhttps://twitter.com/bgrant0607/status/1124168404904976384 …
Especially in distributed, resilient, fault-tolerant systems. If something occurs 1M times a day and the system has no observable degradation in correctness, SLOs, efficiency, or anything, is it an error?
-
-
This is why Kubernetes events just distinguish Normal, for desired/expected behavior, and Warning, for undesirable behaviors. Severity of the latter really depends on the situation, not on the event type.
-
That only makes sense. Complexity in logging always means one will have to sanitize it later, when possible
End of conversation
New conversation -
-
-
When that happens, sadly the most common thing I’ve seen is to operators or devs to ignore the messages. From that point on, it becomes the application expected behavior
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.