Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optional logging metrics for rule applications #313

Open
raghushantha opened this issue Oct 8, 2015 · 1 comment
Open

Optional logging metrics for rule applications #313

raghushantha opened this issue Oct 8, 2015 · 1 comment

Comments

@raghushantha
Copy link
Member

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.
"

@joeyaiello
Copy link
Contributor

Two possible metrics:

  • Speed of individual rule invocation
  • Frequency of rule failing (i.e. rule is "caught")

And per Tobias' suggestion, rules should be instrumented regardless of whether they fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants