From the deprecated_log custom post type the plugin creates and the matching postmeta rows. Each call to a deprecated function, hook, or argument lands as a post, and the chart cards run live queries against the same rows the plugin's admin screen reads.

Yes. Log Deprecated Notices records the calling file in each entry, and SleekView parses the path to extract the plugin or theme directory. A pie card grouped by source surfaces the responsible vendor without manual investigation.

Yes. The plugin hooks _deprecated_function, _deprecated_argument, and doing_it_wrong, which fire from core, plugins, and themes equally. The chart cards split sources by directory so core, plugin, and theme deprecations are easy to separate.

Yes. SleekView queries only the columns the active cards need and pushes grouping to the database, so a deprecated_log table with tens of thousands of rows still renders a horizontal bar chart quickly. View-level caching keeps repeated loads instant.

Yes. An Area card grouped by post_date with a date filter spanning a release window shows the immediate impact of a plugin update. A falling curve after a vendor update is the clearest possible proof the fix landed.

Yes. View-level filters for date range, source pattern, or deprecation type 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 in sync.

Yes. SleekView only reads from the database, never modifies the deprecation log, and never enables additional capture. If Log Deprecated Notices itself is acceptable on production, the chart dashboard adds no extra load beyond the queries the cards need.

No. The Tools entry the plugin adds keeps working with its paginated list of entries. SleekView Charts adds a reporting surface on top, so the log itself stays intact and the dashboard owns the summarisation.