Yes. The view queries the same log table Hide My WP writes per probe, including IP, requested path, attack type, matched rule, and timestamp. The grid reflects the live log without an export step.

Yes. The attack-type column is filterable, so isolating brute-force, file-scan, SQL probe, or rewrite-probe traffic is one click. A brute-force-only view scoped to the last 24 hours is the standard credential-stuffing slice.

Yes. Hide My WP Ghost (the successor product from the same author) shares the intrusion log schema. SleekView reads either version without additional configuration.

Yes. The grid can sort by IP frequency to surface the addresses hitting most often. The longest streaks are usually the candidates for a permanent firewall block rather than a rotating soft block.

Yes. The same data source feeds both, so a row reviewed in the grid stays in sync with the donut on the next chart render. The grid is the row-level workspace; charts are the rollup over the same log.

Yes. The plugin supports multisite, and SleekView respects that scope. On multisite each subsite has its own intrusion grid, and a network-level view can roll probes up across blogs when one security team monitors the whole network.

No. Only the rows on the current page are queried, and the log table is indexed on timestamp and IP. Sites recording millions of probes a month query the same as smaller sites because pagination keeps the row count constant.

Yes. Any filtered view exports to CSV with active filters preserved. Security reviews get a defensible sheet of intrusion activity without manual log scanning.