akaunting/laravel-firewall

Ability to see why a rule was triggered?

MCKLtech opened this issue · 0 comments

This may exist, but I can't see it if it does. In the logs, the lowest level of detail is the middleware, e.g. 'Agent,' but it would be helpful to know what about that middleware triggered the alert.

Is this possible under the current architecture?