Releases
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.
You can’t perform that action at this time.