I am stopping to use this plugin at the version 1.3.1 because it is outright dangerous from the point of view of security. We often say that "an absence of logs is better than false logs" and this is exactly what is wrong with this plugin.
You think that everything is fine with your website but if you look in closer, you will find that the plugin simply was not logging any security relevant information for some time now. This is unacceptable in a security critical component of the website. It creates a false sense of security.
Previously, this plugin loaded the logs with megabytes of information, slowing down the website and providing tons of nonsensical details in between which I would hardly distinguish the important things. That was fixed now but created an even more dangerous aberration.
I hope the author(s) will fix their act some time.
My hoster deactivted my account because of this plugin, it produces much too much sql load...
Follow up -- as of 02.18.2015 -- we tried it again and for random reasons it started tanking servers again. Nothing special about the servers or the installs:
show processlist from mysql shows that it's running a SELECT * FROM one of its tables (only 5000 rows in it) and it won't finish, then it keeps stacking statements.
The service it provides is great.
But the burden to the database and how it scales with traffic is horrible.
We've now had SEVERAL websites go down because of this plugin.
It just bloats MySQL and we see 1000% CPU usage, 400% memory usage.
The plugin should be using access logs or syslog or something, not assaulting the database.
You must log in to submit a review. You can also log in or register using the form near the top of this page.