✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Stream: activity records & connectors as tables

Stream writes records into wp_stream and pivots context into wp_stream_meta. SleekView joins them into a grid where you can run cross-connector investigations, save reusable views, and annotate records in place.

♾️ Lifetime License available

SleekView table view for Stream

Stream activity, finally pivotable

Stream models its data tightly: wp_stream stores one row per event with the actor, connector, context, action, and timestamp, while wp_stream_meta holds the variable details as key/value pairs. The default UI does a clean job for browsing, but anything beyond the canonical filters means SQL or a custom query — every connector ships with its own context keys that the list view never surfaces.

SleekView reads both tables and joins them onto a single record. Connector-specific keys promote to columns, so a row from the Posts connector can show its post type and edited field while a row from the Plugins connector can show the plugin slug and version. Saved views capture filters, columns, and sort order, which means the questions a security or ops team asks repeatedly stop being one-off SQL.

The practical payoff is the cross-connector view: everything one user did this morning, every delete across themes and plugins this week, every role change across the network. Stream already records the data faithfully; the limit has always been getting the right slice in front of the right person, and a real grid removes that friction.

Workflow

From Stream records to a real investigation grid

1

Connect to wp_stream

Create a SleekView against wp_stream. Native columns — connector, context, action, user, IP, created — are detected and offered as the starting field set for the grid.
2

Promote meta keys

Add the join to wp_stream_meta and surface connector-specific keys as columns. Post type, plugin slug, theme name, and any custom context become filterable fields rather than buried metadata.
3

Save incident views

Pin filters that matter for triage: Plugin changes this week, Deletes by user, Role escalations, or All actions by deploy_bot. Reopen them with a click rather than rebuilding the filter.
4

Annotate and export

Tag a record, leave an internal note, or archive a false positive from the row. Export the active view as CSV or JSON for downstream tools, ticket systems, or audit handoffs.

Sample columns

A typical Stream activity view

One row per record with user, connector, context, action, and the affected object.
Source: wp_stream, wp_stream_meta
When User Connector Context Action Object
Today 08:12 editor_jen Posts post Updated Spring Sale post
Today 08:45 admin Plugins plugins Activated WP Rocket
Today 09:02 intern_amy Users profiles Updated User #42
Today 09:30 deploy_bot Themes themes Deleted old-theme

Comparison

Default Stream admin vs SleekView

Default Stream admin

  • Stream's records list is clean but only filters by a fixed set of columns.
  • Metadata pivoted into wp_stream_meta is hard to filter without writing SQL.
  • Cross-connector views, like everything one user did this morning, are not part of the UI.
  • Bulk actions on records are not supported in the default plugin.
  • Exports are basic CSV with no column control.

SleekView

  • Joins records with pivoted metadata so every Stream field is filterable as a column.
  • Inline tag, comment, or archive records without opening a sidebar.
  • Filter by connector, context, action, IP, or user role and save reusable views.
  • Group records by connector or user for fast incident triage.
  • Export the visible columns as CSV or JSON for downstream tools.

Features

What SleekView gives you for Stream

Records and meta

Combines wp_stream rows with wp_stream_meta keys so every connector's specific fields — post type, plugin slug, theme name — sit on the same row as the action and the actor.

Saved incident views

Pin filters like Plugin changes, Role changes, or Deletes by user for instant triage. Each view captures the active filter, the column set, and the sort, ready to reopen during the next incident.

Inline annotations

Add a tag, an internal note, or an archive flag from the row. Investigation context stays attached to the record itself rather than scattered across tickets and chat threads.

Audience

Who uses SleekView for Stream

Security ops

Run cross-connector investigations against deletes, role changes, and plugin activations. Pivot on user, IP, or time window without writing SQL or exporting raw tables.

Multisite admins

Audit changes across the network by joining users, connectors, and contexts into a single super-admin grid. Per-site filters keep the noise down on busy installs.

Developer teams

Trace deployments and config changes by filtering Stream records by user or IP. Pair with build IDs in metadata to map every Stream event to a specific release.

The bigger picture

Why cross-connector investigation matters

Stream's value is breadth — it logs events across posts, options, plugins, themes, users, taxonomies, comments, widgets, and any connector you add. That breadth is also the reason its default UI cannot answer real questions cleanly: a triage moment usually crosses connectors. When a deploy goes wrong you do not just want to see plugin activations; you want everything one user did in a fifteen-minute window across every connector.

When a content audit fires you want post deletions, option edits, and theme changes side by side. The metadata pivot makes that possible in theory, since each connector adds its own keys to wp_stream_meta, but only if the UI lets you promote those keys to columns and filter on them. Multisite makes the gap larger because the same investigation has to span sites, not just connectors.

Treating Stream data as a real grid turns it from a passive log into a working incident-response tool: ask a question, save the view, hand it to the next person on rotation.

Questions

Common questions about SleekView for Stream

No. SleekView reads from wp_stream and wp_stream_meta; it does not intercept the connector pipeline. Stream continues to capture events the same way, with the same retention rules. Annotations applied through SleekView live in a separate store, leaving the Stream audit chain untouched.

 

Yes. Any key in wp_stream_meta can be promoted to a column. That includes connector-specific fields — post type, plugin slug, theme name, taxonomy term — as well as custom keys added by add-ons or your own connectors. Once promoted, keys behave like any other column for filtering and sorting.

 

Yes. SleekView respects the multisite context where Stream stores it. A super-admin view can filter records by site, user, or connector across the whole network, while site-level admins see only the events relevant to their site.

 

Yes. Exports include only the columns currently visible and respect the active filter and sort. Choose CSV for spreadsheets and ticket systems or JSON when piping records into a SIEM or downstream automation.

 

SleekView paginates server-side and uses Stream's existing indexes on connector, user_id, and created. Even installs with years of records stay responsive because the grid never tries to load the entire dataset — each request returns one page filtered against the index.

 

Yes. Capability checks follow the role configuration Stream uses, so only users with the right capability can view records or make annotations. You can also gate specific saved views to a smaller group when the underlying data is sensitive.

 

If the other plugin writes to a known table, you can build a separate SleekView for it and put the two grids side by side. The plain answer for true correlation is filtering by user and a tight time window in each view; SleekView does not perform automatic cross-source joins beyond Stream's own tables.

 

Stream prunes older rows from wp_stream based on its retention setting. SleekView reads what is in the table, so if a row has been pruned it cannot appear in the grid. For long-term audit trails, set Stream's retention to match your compliance window or schedule periodic exports of saved views.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView