Premium 1.14.0 logs changes to Premium’s own settings, adds the user behind each event to Datadog and Splunk payloads, and finally ships the plugin’s translations — 22 languages that were missing from the download until now.
Datadog and Splunk now see who did it
The biggest fix/change in this release is more fields to Datadog and Splunk.
If you forward events to Datadog or Splunk, you could see that something happened but not who was behind it. The payload said the initiator was wp_user and stopped there, which is not much help when you’re looking at an alert at 2am.
Forwarded events now carry user_id, user_login, user_email and server_remote_addr. On Datadog they’re also mapped onto the reserved attributes usr.id, usr.name, usr.email and network.client.ip, so events populate Datadog’s built-in user panel and GeoIP enrichment rather than landing as generic custom facets.
If you want your own fields in a forwarded payload — a post title, a changed setting value, whatever your logger has — there are two new filters for that: simple_history/channel/datadog/payload and simple_history/channel/splunk/payload.
Full changelog
Added
- Changes to Premium’s own settings — retention, IP storage, stealth mode, failed login attempts, Message Control, alerts, the Google Maps key and the post activity panel — are now logged, shown as “Modified settings”.
- Datadog and Splunk payloads now include the user behind the event:
user_id,user_login,user_emailandserver_remote_addr. Previously the initiator was only everwp_user. - Datadog payloads also map the user and IP onto Datadog’s reserved attributes (
usr.id,usr.name,usr.email,network.client.ip), so events populate the built-in user panel and GeoIP enrichment. - New
simple_history/channel/datadog/payloadandsimple_history/channel/splunk/payloadfilters for adding your own fields to a forwarded payload. - The Alerts item in the core 5.30.0 header status bar shows the number of active alert rules, and links to them.
Changed
- Changes to structured settings (alerts, Message Control) are recorded as “changed” rather than dumping their full value into the log.
Fixed
- Stealth Mode no longer creates its options during normal page views. This caused a stray “Modified settings” event on fresh installs once settings logging arrived.
- Fatal error when setting up the External Database channel. Creating the log table succeeded and then immediately crashed the request, so the channel looked broken even though the table was there.
- Premium now ships with its translations, in 22 languages.
Update from your WordPress dashboard. Premium 1.14.0 needs Simple History core 5.26.0 or later, and the settings-change details look their best on core 5.30.0, which renders them itself. If something looks off after updating, let us know.