Brute force attacks can make the log big – here’s why and how to stop it

In the support forum for Simple History some people have raised issues about the Simple History database tables are growing large. (For example this thread and this thread.

The reason for this is that Simple History is really good at logging things. So if your WordPress blog is getting a really big amount of brute force attacks, all those failed login attempts will be logged in Simple History. Nothing wrong with that, that’s the purpose of the plugin. But the number of rows can be huge – like over a million for some sites. And that can be an issue for some low cost hosts where you have a limited amount of storage/disk space.

Here’s what Simple History is doing to keep the database small – and a solution to keep the number of login attempts down to a minimum:

Now logs when users resets passwords + easier to see time of event

Version 2.4 of Simple History brings a wanted addition to the event log: when hovering the time of an event the tooltip now displays both the local time and the GMT time of the event. This change makes it easier for admins in different timezones that work together on a site to understand when each event happened.

Screenshot showing both local and GTM time on an event in the Simple History plugin

The update also brings two new logged things:

Actions performed in plugins “User Switching” and “Enable Media Replace” now visible in Simple History

Good news everyone!

Simple History now has basic support for logging events from some third party WordPress plugins. First out is the User Switching plugin and the Enable Media Replace plugin.