No. The FluentSMTP UI remains the right place for connection configuration and per-row inspection. SleekView Charts adds the dashboard view that the default UI does not assemble, complementing rather than replacing.

Yes. Group failed rows by connection and aggregate counts to render a per-connection Bar card. Providers with rising failure rates become visible immediately without per-row filtering.

Yes. Average retry count grouped by connection or status produces a retry-loop diagnostic chart. Rising averages signal SES throttles or Postmark recipient rejections worth investigating.

Yes. Dashboard-level filters apply to every chart card. A recipient-domain filter scopes the whole dashboard to that domain, which is the audit pattern compliance reviews need.

Yes. Aggregations use the indexed columns FluentSMTP maintains on the log table. Sites with millions of log rows render the dashboard in seconds because the queries ride on existing indexes rather than scanning meta.

Yes. Each chart card exposes its underlying row set for CSV export with active filters applied. The export produces a defensible artifact for compliance retention or post-incident reports.

Yes. When the primary fails and the fallback succeeds, both attempts appear in the log with their respective statuses. Group by connection to spot which primary is unreliable and how often the fallback rescues sends.

Timestamps stay in the WordPress timezone for consistency with the rest of the admin. Column-level formatting can render charts in UTC or another timezone for teams operating across regions without changing the underlying values.