Wp Decalog Versions Save

Capture and log events, metrics and traces on your site. Make WordPress observable - finally!

3.5.1

2 years ago

Changed

  • Upgraded Monolog library from version 2.5.0 to version 2.6.0.
  • Experimental: Elasticsearch V7-only support is now upgraded to V7/V8.

Fixed

  • A PHP error may be triggered when adding a new role to a user (thanks to Axel Ducoron).

3.5.0

2 years ago

Added

  • Compatibility with WordPress 6.0.
  • New events when adding or removing a user role.
  • A new filter allows now to exclude specific metrics for specific loggers (based on a suggestion from Jan Thiel).
  • New icons in loggers list to show activated privacy options.

Changed

  • Messages for database version downgrade/upgrade are much more precise.
  • Upgraded Monolog library from version 2.3.4 to version 2.5.0.
  • Site Health page now presents a much more realistic test about object caching.
  • Improved favicon handling for new Google API specifications.
  • Improved compatibility with Members plugin.
  • Improved errors handling when creating incomplete loggers.

Fixed

  • Events about roles changes are wrongly reported (thanks to Valérie Galassi).
  • The APCu test in option page may fail (thanks to Renaud Pacouil).
  • PHP 8.1 compatibility changes have introduced side effect on HTML entities encoding (thanks to Jan Thiel).
  • Callstack items are wrongly named (and ordered) in Loki logger.

3.4.1

2 years ago

Fixed

  • The Site Health page may launch deprecated tests.

3.4.0

2 years ago

Added

  • Compatibility with PHP 8.1.
  • New logger to send events to Spatie Ray app.
  • New listener for Redis Object Cache (thanks to Till Krüss for the help).
  • Logo for bbPress in events list and viewer.
  • Logo for MysQL DB in events list and viewer.
  • Logo for MariaDB DB in events list and viewer.
  • Logo for PostgreSQL DB in events list and viewer.
  • Logo for Percona DB in events list and viewer.

Changed

  • Html entities are now substituted for better readability in New Relic NR-Logs.
  • Refactored cache mechanisms to fully support Redis and Memcached.
  • Improved layout for WordPress traces viewer.
  • Better events messages for lost password form submission.
  • Improved APCu storage for loggers.
  • Reduction of the events' level for the wp_die ajax handler because it is not used consistently in the WordPress core (thanks to Jan Thiel for the suggestion).
  • Updated DecaLog SDK from version 2.0.0 to version 2.0.2.
  • Updated PerfOps One library from 2.2.1 to 2.2.2.
  • Improved bubbles display when width is less than 500px (thanks to Pat Ol).
  • Updated headers for drop-in and mu-plugin files.

Fixed

  • The console menu may display an empty screen (thanks to Renaud Pacouil).
  • There’s a PHP error when reaching the checkout page of woocommerce with WP Activity Log activated (thanks to freshuk).
  • Object caching method may be wrongly detected in Site Health status (thanks to freshuk).
  • The "WordPress metrics collation" span is attached to the wrong parent.
  • There may be name collisions with internal APCu cache.

3.3.0

2 years ago

Added

  • Compatibility with WordPress 5.9.
  • New listener for Cavalcade (thanks to Jan Thiel for the suggestion).
  • Internal viewers for events and traces display instance name in details screens.
  • New button in settings to install recommended plugins.
  • There's now decalog_events_list_actions_for_event, decalog_events_list_actions_for_source, decalog_events_list_actions_for_time, decalog_events_list_actions_for_site, decalog_events_list_actions_for_user and decalog_events_list_actions_for_ip filters to add custom actions to events list view (thanks to Julio Potier for the suggestion).
  • There's now decalog_event_view_actions_for_event, decalog_event_view_actions_for_content, decalog_event_view_actions_for_php, decalog_event_view_actions_for_device, decalog_event_view_actions_for_wp, decalog_event_view_actions_for_http, decalog_event_view_actions_for_wpbacktrace and decalog_event_view_actions_for_phpbacktrace filters to add custom actions to single event viewer (thanks to Julio Potier for the suggestion).
  • There's now decalog_traces_list_actions_for_trace, decalog_traces_list_actions_for_duration, decalog_traces_list_actions_for_time, decalog_traces_list_actions_for_site and decalog_traces_list_actions_for_user filters to add custom actions to traces list view (thanks to Julio Potier for the suggestion).
  • There's no decalog_trace_view_actions_for_trace and decalog_trace_view_actions_for_wp filters to add custom actions to single trace viewer (thanks to Julio Potier for the suggestion).
  • In all internal viewers, country flags have the name of the country as alternative text.
  • Adds OPcache compatibility for cluster/nodes environments - including Kubernetes.
  • Adds, for consistency check, PHP versions and modules compatibility for cluster/nodes environments - including Kubernetes.
  • Logo for WP-CLI in events list and viewer.

Changed

  • Improved update process on high-traffic sites to avoid concurrent resources accesses.
  • Better publishing frequency for metrics.
  • Instance name is now propagated for all events and traces loggers (in context), even if it is not required by the corresponding service.
  • Upgraded Monolog library from version 2.2.0 to version 2.3.4.
  • Improved default values for "InfluxDB 2" logger.
  • Improved way to detect instance name.
  • Updated labels and links in plugins page.

Fixed

  • The loggers list displays wrong types for "crash analytics" and "alerting".
  • OPcache events logging is wrong on clustered environments (thanks to Jan Thiel).
  • The warning message about "debugging" class logger is not always displayed when it should be.
  • The default index names for Elasticsearch and Elastic Cloud are inconsistent.
  • The HTTP 204 error code sometimes returned by a Loki instance is wrongly interpreted.
  • Name collisions or PHP errors can occur with plugins using outdated versions of Monolog library (like BackWPup).
  • Clearing events by hook reference may be not logged (thanks to Jan Thiel).
  • Unscheduling events may be not logged.
  • Logging an event with a message containing SQL select may be wrongly truncated in the where clause.
  • In some edge cases, logging plugins updates may not work correctly.
  • WordPress event viewer try to display request referrer even if it doesn't exist.
  • Country translation with i18n module may be wrong.
  • There's typos in CHANGELOG.md.

3.2.0

2 years ago

Added

  • New logger to send events to New Relic as NR-Logs.
  • New logger to send events in Tracy bar.
  • New logger to send metrics to New Relic.
  • New logger to send traces to New Relic.
  • New PerfOps One menu in the admin bar for quick actions.
  • All cron-related events are now logged (schedule, unschedule and clear).
  • There's now a warning box in all admin pages if a "debugging" logger is running.
  • Logos for Action Scheduler and WooCommerce in events list and viewer.
  • Logo for BuddyPress in events list and viewer.
  • Logo for W3 Total Cache in events list and viewer.
  • Logos for standard, Amelia and Forminator Stripe gateways in events list and viewer.
  • DecaLog now propagates site domain in events and traces (thanks to Jan Thiel).
  • It's now possible to hide the main PerfOps One menu via the poo_hide_main_menu filter or each submenu via the poo_hide_analytics_menu, poo_hide_consoles_menu, poo_hide_insights_menu, poo_hide_tools_menu, poo_hide_records_menu and poo_hide_settings_menu filters (thanks to Jan Thiel).

Changed

  • Design has been improved for the logger selector.
  • Better layout for the "bot details" box when bot name or manufacturer is not detected.

Fixed

  • There may be name collisions for some functions if version of WordPress is lower than 5.6.
  • The main PerfOps One menu is not hidden when it doesn't contain any items (thanks to Jan Thiel).
  • In some very special conditions, the plugin may be in the default site language rather than the user's language.
  • The PerfOps One menu builder is not compatible with Admin Menu Editor plugin (thanks to dvokoun).

3.1.0

2 years ago

Added

  • WordPress events list and viewer display component's logo if it is known.

Changed

  • New redesigned UI for PerfOps One plugins management and menus (thanks to Loïc Antignac, Paul Bonaldi, Axel Ducoron, Laurent Millet, Samy Rabih and Raphaël Riehl for their invaluable help).
  • There's now a decalog_no_log_post_activity filter to modify ability to log posts activities.
  • DecaLog SDK self calls are removed from backtraces.
  • The "Browser Console" logger has been improved (colors and concurrent accesses).

Fixed

  • In some conditions, the plugin may be in the default site language rather than the user's language.
  • Displaying events in WordPress viewer may produce a PHP notice.
  • There're some typos in the settings UI.
  • There's a PHP warning while creating a "PHP Error Log" logger (thanks to Axel Ducoron).
  • The "Browser Console" logger may not log all events in some rare cases.
  • With WordPress 5.8 it is impossible to move and close boxes (events and traces).

3.0.2

2 years ago

Fixed

  • DecaLog is unable to work properly with BackWPup (thanks to Emil1).

3.0.1

2 years ago

Fixed

  • wp.org distributes a Release Candidate, not the 3.0.0 version.

3.0.0

2 years ago

Added

  • DecaLog now supports metrics collecting, forwarding and publishing.
  • DecaLog now supports traces collecting and publishing.
  • New WordPress traces viewer allowing to view traces right in the admin dashboard.
  • New "metrics" tab in settings to list all currently collected metrics.
  • New "self-registration" tab in settings to list all currently self-registered components.
  • DecaLog now collects extended metrics for: PHP, WordPress core, database, WordPress multisite and plugins / themes using WordPress DecaLog SDK.
  • DecaLog now collects minimalist metrics for Wordfence.
  • DecaLog now collects extended traces for WordPress core and plugins / themes using WordPress DecaLog SDK.
  • New logger to send events to Datadog.
  • New logger to send metrics to a Prometheus instance (via Pushgateway).
  • New logger to publish metrics as endpoint for Prometheus polling.
  • New logger to send metrics to InfluxDB Cloud or on-premise InfluxDB 2 instance or cluster.
  • New logger to send metrics to Datadog via Datadog agent.
  • New logger to send traces to a Jaeger collector.
  • New logger to send traces to a Zipkin instance.
  • New logger to send traces to Grafana Cloud via Grafana agent.
  • New logger to send traces to Datadog via Datadog agent.
  • New logger to store traces in WordPress database or with APCu.
  • [WP-CLI] New command to list, dump or get metrics: see wp help log metrics for details.
  • [WP-CLI] New command to list self registered components: see wp help log selfreg for details.
  • [WP-CLI] New command to activate/deactivate endpoint authentication: see wp help settings for details.
  • [BC] The version of DecaLog API is now v3.
  • Deactivating or deleting DecaLog now removes MU-plugin and dropin function.

Changed

  • Redesigned loggers list.
  • The WordPress logger now accepts "APCu" as storage engine, in addition to "Database".
  • Upgraded Lock library from version 2.1 to version 2.2.
  • Improved internal IP detection: support for cloud load balancers.
  • [WP-CLI] All commands now support the --stdout flag.
  • [WP-CLI] The wp log logger list command now accepts a logger id or logger type as filter parameter.
  • [WP-CLI] The wp log listener list command now accepts a listener id as filter parameter.
  • [WP-CLI] The wp log type list command now accepts a logger type as filter parameter.
  • [WP-CLI] The wp log status command now returns SDK version too (if SDK in is in use).
  • [WP-CLI] Updated documentation.
  • Wordfence listener is much more precise while logging events.
  • The Stackdriver logger is now named "Google Cloud Logging" to follow Stackdriver rebranding.

Fixed

  • [WP-CLI] The wp log send command doesn't set an exit code in case of failure.
  • [WP-CLI] Typos in inline help.
  • Messages may be wrongly truncated in live console.
  • Detecting database version on WordPress prior to 5.5 generates an error (thanks to Sébastien Gastard).
  • Saving a page from the Divi builder may trigger an error when W3 Total Cache is activated.