Block Bad Queries Pro writes blocked requests into its own log table with request URI, query string, rule matched, IP address, user agent, and timestamp. The plugin's log viewer is a paginated list, useful for spot-checks but slow when the question is about volume or pattern.

SleekView reads the BBQ log table directly and exposes each row as a chartable record. Rule name, request method, and IP become groupBy columns, while the timestamp drives trend charts at any bucket width.

Charts then count, group, and trend the log: total blocks today, blocks by rule, top offending IPs, and a time series of blocks per hour. The same dataset feeds Table and Kanban views, so an analyst can pivot from a chart spike to the raw log row without leaving WP Admin.

Block Bad Queries does the blocking, but the log it produces is only useful when somebody actually reads it. A paginated viewer is fine for incident response, less so for the weekly question of whether the rule set is working. SleekView Charts reads the same log table and renders it as KPIs, distributions, and trends.

The plugin keeps owning the blocks, SleekView just surfaces them in a shape the security team can scan in seconds. Saved views travel with the site, and chart cards export as CSV for monthly reports. Rule tuning gets faster when the noisy patterns are visible in a Pie card instead of buried in pagination.