-
-
Notifications
You must be signed in to change notification settings - Fork 219
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
Implement new directive for performance profiling #192
Comments
@fzipi was motivated with this last year, I think we should think about a profiling engine for Coraza capable of creating a detailed report of the performance of the rule. There might be a way to attach ourselves to the profiling API and hook some "tags" https://pkg.go.dev/runtime/pprof, splitting the data by rule. That way we not only get the milliseconds performance per rule, but we will get the memory allocation, processing units, and more. |
Sounds awesome! Maybe makes sense also to have a |
It sounds consistent with other directives like SecAuditEngine and SecRuleEngine. |
This issue is stale because it has been open for 30 days with no activity. |
This is still happening. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Summary
I think we need to add some hooks for the rule.
Basic example
Not yet.
Motivation
If we have some hooks of the rule, we can add some custom behaviors before and after rule execution. For example, collect the execution time of each rule(because our system performance requirements are high, it is necessary to do some observable work).
The text was updated successfully, but these errors were encountered: