Yes. The cards query the same log rows IP Geo Block writes per request, including IP, country code, matched rule, target endpoint, and timestamp. The chart layer reflects the live log without an export step.

Yes. Each card supports a filter on the protected endpoint, login, comment, admin-AJAX, REST, XML-RPC, and so on. A view scoped to the login endpoint shows the country mix driving credential attempts separately from other traffic.

Yes. The same data source feeds both, so a row inspected in the table stays in sync with the donut on the next chart render. The charts are a second presentation over the same log table.

The donut groups requests by the country code IP Geo Block itself wrote against each row. Whichever geolocation backend the plugin is configured to use, MaxMind, ipapi, or the bundled GeoIP database, the chart layer uses the resolved code without re-running the lookup.

Yes. The cache report and the validation log share the same row identifiers, so the chart layer can cross-reference cached lookups with logged blocks. The dashboard surfaces both layers without configuration.

Yes. Each WordPress role keeps its own saved dashboard layout. Security leads see the country donut by default; firewall maintainers see the top-IP bar; compliance owners see the daily KPI. Saved layouts ship per role without rebuilding the cards.

Charts query the live validation log on each render with paginated reads. The result is the same block state the plugin's own statistics tab would summarise, refreshed every time the dashboard loads.

Yes. Queries use the indexed timestamp and country-code columns on the validation log. Sites validating millions of requests per month render the dashboard in well under a second.