Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Service Arch
Description
Back in 3.6, we used to have wassert, and it was counted in a separate counter just like masserts, uasserts, and tasserts currently are. Since 4.0, however, the "warnings" AssertionCount is just zero and has no code that can increment it. This assertion-warnings count is still collected out of server status and displayed on the Assertions metrics chart in Cloud along with the rest of the assertions, but it never shows anything other than 0.
To restore usefulness to this counter, we should count the number of logged server messages at "W" (warning) severity. In a sense, these are our new "assertion warnings".
In addition, I propose that we start counting the number of "E" error log messages, in a separate counter. We could then start collecting this data and add a line to the Assertions chart for errors.