Optional logging metrics for rule applications

Tobias has suggestions around adding useful metrics for rule applications.

Context:

"It would be extremely helpful to have metrics about how often a rule was applied, how often it was violated, and how long evaluation took.
It could be controlled via opt-in so logging is off until you turn it on.
This way, we all could identify the rules violated most often, and initiate educational initiatives, plus find out more about rule quality and relevance.
The best way to consume this info would be through event logs. This would not replace my original suggestion of having a “-Diagnostic” switch. The –Diagnostics switch would apply to the current scenario only and return metrics immediately.
"

L’issue ne nomme ni fichiers, ni tests, ni points d’entrée. Commencez par localiser où les règles sont appliquées et évaluées, puis déterminez comment la journalisation des événements opt-in et le commutateur de diagnostic proposé devraient exposer les nombres d’applications, les violations et le temps d’évaluation.