Version 4.3.0

Added

• Compatibility with WordPress 6.6 & 6.7.
• It's now possible to change buffering behavior (for loggers supporting deferred forwarding). By default, the new behavior is: events batch at 1000 and no buffering for WP CLI. To modify it, you have to activate "advanced settings" in admin (see hooks for details).

Changed

• To avoid name collision with some third-party configurations, the version tag in Datadog, Loki and Grafana loggers is now named wp_version (it was previously version).
• Ability to self-update from Github.
• The plugin user agent is now more consistent and "standard".

Fixed

• There's a WordPress core "feature" which causes some PII to leak (to wp.org) during plugin and theme updates. This is no more the case for this plugin.
• In some cases, a WordPress notice can be triggered concerning the loading sequence of translations.

Removed

• Test site launching from wordpress.org plugin page.
• All Databeam hooks and libraries, as the Databeam project is abandoned.
• Dependency on wp.org for updates.

Version 4.2.0

Added

• It's now possible to send Datadog events, metrics and traces to custom endpoints. These custom endpoints must be defined in wp-config.php as DECALOG_DATADOG_EVENTS_CUSTOM_ENDPOINT, DECALOG_DATADOG_METRICS_CUSTOM_ENDPOINT and DECALOG_DATADOG_TRACES_CUSTOM_ENDPOINT constants.

Changed

• To avoid name collision with some third-party configurations, the environment tag in Datadog, Loki and Grafana loggers is now named wp_env (it was previously env).

version 4.1.0

Added

• New listener for WP Migrate Lite & Pro.

Fixed

• [WP-CLI] PHP error in some cases when Elastic Cloud is a running logger.
• Some failing loggers may not be able to report their health state.

Version 4.0.0

Important note about this version:

• DecaLog 4 is a transition version to prepare DecaLog 5.
• No migration path wil be available to migrate from DecaLog 3.x to 5.x, so don't ignore this version 4: install it!
• DecaLog 5 will be available in early 2025.

Added

• Events sent to DataDog, Elastic Cloud, Elasticsearch, Grafana Cloud, Loki and Sematext can now be extended with custom fields (this feature supports variable substitution).
• It's now possible to substitute PHP-defined constants for some loggers settings.
• There's now a filter to map PHP error levels to PSR3 levels - see hooks reference (thanks to Clément Hallet).
• Full compatibility with Elasticsearch 8.

Changed

• [BC] If a third-party plugin or theme uses PSR-3 1.x only, DecaLog early-loading option become unavailable.
• [BC] DecaLog now uses PSR-3 1.x & 3.x => if you use the DecaLog SDK, you should update it to version 4.
• Events contexts are now fully mapped with standard fields while using Elastic Cloud logger.
• The responsiveness of DecaLog settings pages has been greatly boosted.
• The rendering of web console has been improved.
• Upgraded Monolog library from version 2.9.1 to version 2.9.3.
• Upgraded InfluxDB library from version 1.12.0 to version 3.5.0.
• Upgraded GuzzleHttp library from version 7.2.0 to version 7.8.1.
• Upgraded Elasticsearch library from version 7.6.1 to version 8.13.0.
• Upgraded Tracy from version 2.10.5 to version 2.10.7.

Fixed

• Constant storage may produce PHP warning while initializing.
• There's some deprecation warnings with PHP 8.4.

Version 3.10.0

Added

• Compatibility with WordPress 6.5.
• Spatie Ray logger now supports host and port settings to allow Docker, Kubernetes and other "local" usage (thanks to Axel Ducoron).

Changed

• Minimal required WordPress version is now 6.1.
• Minimal required PHP version is now 8.1.

Version 3.9.1

Changed

• Upgraded Tracy library from version 2.8.7 to version 2.10.5.

Fixed

• [SEC004] SQL Injection vulnerability (thanks to isacaya from Patchstack).
• [WP-CLI] In some cases --no-color and --color global parameters may be overridden.

Removed

• Warning message when Spatie Ray is activated as it doesn't log in browser.

Version 3.9.0

Added

• It's now possible to substitute environment variables for some loggers settings.
• Compatibility with WordPress 6.4.

Changed

• Settings options have been reorganized to be more consistent.

Version 3.8.0

Added

• Compatibility with WordPress 6.3.
• Datadog events logging now supports all events levels (thanks to Jan Thiel).

Changed

• The color for shmop test in Site Health is now gray to not worry to much about it (was previously orange).

Fixed

• The url for console error remediation is wrong.

Removed

• Support for WP Activity Log plugin because it doesn't adhere to observability basic standards.

Version 3.7.1

Fixed

• [SEC003] CSRF vulnerability / CVE-2023-27444 (thanks to Mika from Patchstack).

Version 3.7.0

The developments of PerfOps One suite, of which this plugin is a part, is now sponsored by Hosterra.

Hosterra is a web hosting company I founded in late 2022 whose purpose is to propose web services operating in a European data center that is water and energy efficient and ensures a first step towards GDPR compliance.

This sponsoring is a way to keep PerfOps One plugins suite free, open source and independent.

Added

• Compatibility with WordPress 6.2.
• It's now possible to define failsafe loggers right in the wp-config.php file (thanks to Jan Thiel).
• Jaeger and Zipkin traces loggers now support SpanKind feature (thanks to YR Chen).
• It's now possible to add a custom service name for tracers using Jaeger thrift over HTTP format.
• New option to not report non-existent metrics.

Changed

• Upgraded Monolog library from version 2.8.0 to version 2.9.1.
• Improved browser logger for events.
• Fixed tags are now passed as global tags when tracing with Jaeger logger (thanks to YR Chen).
• Great resources improvement for WordPress installs where there's no monitoring needed (thanks to Jan Thiel).
• Improved loading by removing unneeded jQuery references in public rendering (thanks to Kishorchand).

Fixed

• Some weird processes can try to delete null attachments, and it produces PHP warning (thanks to Axel Ducoron).
• In some edge-cases, detecting IP may produce PHP deprecation warnings (thanks to YR Chen).
• Some strings should not be translatable (thanks to Laurent Millet).