Improve log management
We need filters, more searching and exporting possibilities, manuals, examples, etc.
Thanks for the idea. We haven’t assigned this idea to a release yet, but we welcome further comments and votes if this is important to you.
Better humanized logging for IPS
When the IPS is logged during debugging, one only sees 'Rule ID: 128:6' or something like this and does not know what this rule is.
For better 'humanization' of this rule, would be to add the names of these rules too to the log.
Yes, this needs to be done. How often we have so long to investigate why something is blocked and then need basically hours of trying to find why it is blocked....
Even more so what needs a huge improvement would be that one can see the id next to each rule. Alternately or both option available that one shows in the logs the name of the rule additionally!!!
As well include instead of just the 'rule id' as well the name of the rule for the logs, there is a huge problem with finding the rule id in general.
Frank Raasveld commented
Investigating logs is slow, and very time consuming, what I do now is setup an ssh session (which is not advised) but then I am able to quickly search and and filter using grep in Busy Box.
I think why not mplement this within the admin interface?
Jan van Melle commented
+3 A main reason was to use Kerio was for logs, but at the moment logs are totally useless and it takes too much time to find some simple things. Please improve this.
Especially Filtering and exporting options.
I vote, but guess that will be enough to add some kind of csv structure into a logs. This little improvement + Excel or Calc will make me happy.
In kerio very bad management logs
+3 to this, especially on http filter. or atlas the ability to only download last hour instead of whole file!
Mario Levesque commented
Log filtering with keywords or features would be a necessary feature, especially in the connection logs (filter by IP, connection type, ports etc..)