A rather curious challenge with FlareWP is going to be what happens when a site is being DDoS’d? The system adds a relatively light load onto a site during runtime, but if events are being written like crazy because of an attack, what should happen? #WordPress I think that FlareWP is be in a unique position to not-only detect when an attack is happening, but also change its own behavior based on the attack, and send a flare to let someone know “hey, your site is drowning here!”

FlareWP has logged about 637,000 on a particularly busy site we maintain @DFS_Web – almost all of those are doing_it_wrong notices. Evidently the people who built this site before us didn’t build the site with WP_DEBUG enabled. Oof. The cool thing, however, is I was able to break it down into 9 distinct errors, and make GitHub issues for each one. Now we can target them one at a time, purge the log, and be good to go.

I’m running FlareWP on a few sites, and It’s moderately horrifying to see how many popular plugins throw uncaught errors that go un-noticed. Out of sight, out of mind I suppose.

But now it’s not out of sight, and it’s driving me insane.