Version 3.1.0

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).

Version 3.0.2

Fixed

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

Version 3.0.1

Fixed

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

Version 3.0.0

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.

Version 2.4.2

Removed

• Some currently unused logger types (will be in next release).

Version 2.4.1

Changed

• [WP-CLI] Changing the color scheme for the tail command is now done via the --theme=<theme> parameter.

Fixed

• [WP-CLI] There's an error in the tail command synopsis (thanks to aspsa).
• Site Health may produce PHP notice while listing loggers details.

Version 2.4.0

Added

• New logger to send crash reports to Bugsnag.
• New logger to send crash reports to Raygun.
• New logger to send exceptions to Google (Universal) Analytics.
• New logger to send logs to an Elasticsearch instance.
• New logger to send logs to a Loki instance.
• New logger to send logs to Grafana Cloud service.
• New listener for bbPress.
• New listener for BuddyPress.
• New listener for Action Scheduler library.
• New listeners for Stripe gateways (standard, Amelia and Forminator) libraries.
• New 'environment' context metadata for all external loggers.
• Compatibility with WordPress 5.7.
• New setting to override live console and local access privileges when in development or staging environments (thanks to sebastienserre for the suggestion).
• New automatic bootstrap listener allowing to catch PHP events occurring before DecaLog is loaded.
• It's now possible to filter by session ID in WordPress events viewer.
• The current session user blinks in WordPress events viewer.
• Core listener now reports stuck/unstuck posts.
• New "early-loading auto diagnostic" in Site Health.
• The WordPress events viewer allows to manage sessions for a user if Sessions plugin is installed.

Changed

• When OPcache API is restricted by restrict_api configuration directive, OPcache configuration is no more monitored.
• Detection of PHP version upgrade/downgrade now takes care of web vs. command-line difference.
• Detection of OPcache configuration changes now takes care of web vs. command-line difference.
• DecaLog now propagates traceID and sessionID for all loggers supporting it.
• Upgraded Monolog library from version 2.0.2 to version 2.2.0.
• Consistent reset for settings.
• Improved translation loading.
• Now detects and emits warning when a call is sandboxed (theme/plugin editor, for instance).
• Improved display in WordPress event viewer when backtraces are not available.
• [WP_CLI] log command have now a definition and all synopsis are up to date.
• The display of verb labels in events viewer has been improved.
• Better PHP introspection and backtrace cleaning, parsing and rendering.
• Check on "mandatory" processors are now done for loggers which need it.
• Improved hash handling and reporting for users and IPs.
• Improved self monitoring to handle loggers internal errors.
• Code refactoring led to a huge execution speed gain: DecaLog is now 30% faster.
• Improved message for deleted posts/pages in core listener.
• Elastic Cloud logger is renamed for better consistency.
• Now fully detects versions for MariaDB, Percona, MySQL and PostgreSQL (and so, fully detects migrations and upgrades).

Fixed

• [SEC002] The password for Elastic Cloud logger is in plain text in "Site Health Info" page.
• DecaLog doesn't correctly honour previous error handler calls (thanks to ajoah).
• DecaLog jams the plugin/theme editor while editing PHP files (thanks to ajoah).
• In Site Health section, Opcache status may be wrong (or generates PHP warnings) if OPcache API usage is restricted.
• PHP notice when trying to display details for "System auto-logger".
• DecaLog may log multiple times a change about environment type.
• When disabling "early loading", the mu-plugin is not always removed.

Removed

• DecaLog internal watchdog as it is no longer necessary.

Version 2.3.0

Added

• Supports for new application passwords events (WordPress 5.6 and higher).
• Compatibility with WordPress 5.6.

Changed

• Improvement in the way roles are detected.
• Console now starts automatically in the admin dashboard if clicked.
• Anonymous proxies, satellite providers and private networks are now fully detected when IP Locator is installed.
• Better web console layout.

Fixed

• [SEC001] User may be wrongly detected in XML-RPC or Rest API calls.
• Deleting a comment may trigger an error (thanks to jimmy19742).
• When site is in english and a user choose another language for herself/himself, menu may be stuck in english.
• When shared memory is not available, it is wrongly reported as an emergency.

Version 2.2.2

Fixed

• The DecaLog menus may be hidden when they should be visible (thanks to Emil1).

Version 2.2.1

Changed

• Hardening (once again) IPs detection.
• Prepares PerfOps menus to future 5.6 version of WordPress.

Fixed

• The remote IP can be wrongly detected when in AWS or GCP environments.