Hide My WordPress works by renaming the public endpoints attackers automate against. Once wp-login is moved, the original path returns a generic page or a hard block, and the plugin records the attempt with the requested path, IP, user agent, and timestamp. The admin screen lists those attempts, which is exactly enough to confirm the obfuscation is doing its job, but it cannot tell you how many bots still scan the old paths every day or which IPs persist after their first failure.

SleekView Charts reads the block log as a normal data source. The requested_path, ip, user_agent, and blocked_at fields become groupable the moment the source is mapped. A donut splits attempts across wp-login.php, wp-admin, xmlrpc.php, and wp-content paths, a Number card shows today's total, a horizontal bar surfaces the top probing IPs, and an area chart traces daily volume so a scanner campaign is obvious before it spreads.

Nothing is rewritten on the plugin's side. Hide My WordPress keeps obfuscating, the log keeps growing, and the dashboard renders the same rows in a shape that supports a daily security review of the bot traffic the rename already absorbs.

Renaming wp-login does not make the bots stop; it makes them irrelevant for a while. They keep hitting the old paths, and the plugin keeps writing rows. Each row is uninteresting on its own, but the stream carries a useful signal about how persistent the bot traffic is, which paths still receive scans, and which IPs return after their first failure.

The data exists in the plugin's own log table with all the columns it maintains. Rendering it as Number, Pie, Bar, and Area cards costs nothing on the writing side and turns the same rows into a dashboard, which makes obfuscation observable rather than invisible.