BBQ Pro is a request firewall. It runs on every page load, checks the query string against its rules, and drops a row into the plugin's block log whenever a match fires. The settings screen and the log viewer give a flat list of recent blocks, which is fine for a single-row investigation but useless for spotting trends or comparing weeks. The data is rich, the rendering is the bottleneck.

SleekView Charts reads the BBQ log as a normal data source. The matched rule pattern, request URI, IP, user agent, and blocked_at timestamp become groupable fields the moment a source is mapped. A donut splits blocks by rule pattern, a Number card shows today's total, a horizontal bar surfaces the top abusive IPs, and an area chart traces daily volume so a scanner wave on a quiet weekend is obvious before it becomes a Monday incident.

Nothing is rewritten on BBQ's side. The plugin keeps filtering, the log keeps growing, and the dashboard renders the same rows in a shape humans can read at a glance, even on a site that ships tens of thousands of blocks a month.

A request firewall makes a thousand small decisions an hour. Each one is a row in a log, and each row matters at most once. What a security team needs is the shape of those decisions over a week, not the rows themselves.

The data exists in BBQ Pro's own block log, with all the columns it maintains on every block. Rendering it as Number, Pie, Bar, and Area cards costs nothing on the writing side and turns the same rows into a dashboard. The cadence of firewall review shifts from incident-only to a daily glance, while the underlying log stays untouched and ready for forensics whenever the next incident hits.