Directly from the Debug This option rows in wp_options for recent mode activations, the per-user mode preferences in wp_usermeta, and the bar query log if enabled. No shadow copy or export pipeline. Cards run live queries against the same data the plugin writes.

Yes. The plugin's option and meta keys have stayed stable across recent versions, so the activation log and per-user mode preferences are reliable sources. If a fork changes the key names, edit the SleekView source filter to match and the chart cards pick up the new keys.

Yes. Join the recorded user_id to wp_usermeta and read the wp_capabilities meta value to derive the role at query time. A stacked Bar grouped by mode and split by role then shows whether admins, editors, or developers dominate each inspection mode.

Yes. SleekView only queries the columns and rows the active cards need, so a long Debug This activity log produces a lean grouped count rather than a full scan. Heavy aggregations are pushed to the database engine and cached at the view level for repeat loads.

Cards reflect whatever is currently stored, so a trimmed log produces a shorter time series rather than missing data. To preserve longer history, snapshot the relevant rows to a separate table on a schedule and point a second SleekView source at that copy for long-range trend analysis.

Yes. View-level filters for mode slug, user role, or date range apply to every chart card on the dashboard. One saved configuration drives both the editing table and the reporting view, so investigation and summary stay aligned across the diagnostic workflow.

Charts are read-only summaries by design. To act on an insight, switch to the SleekView table filtered to the same slice (for example, recent query-mode activations) and jump back to the affected page in Debug This from there. Inspection itself stays inside the existing plugin workflow.

No. The admin bar menu, the mode renderers, and the capability gating stay exactly where the plugin puts them. SleekView Charts adds a reporting surface on top of the activity data the plugin already writes, so each inspection remains a one-click action and the dashboard owns the summarisation.