News

A couple minor bugfixes. Added possibility to trace time spent sending mails and extracting text from binary files for the search engine.

Release notes available at https://github.com/gggeek/ezperformancelogger/releases/tag/0.12.0

Some new features as well as minor bugfixes this time around.

Notable features:

  • It is now easier to properly trace the web pages which end up with redirects, without hacking the kernel
  • It is now possible to trace the eZ User id of the current user
  • It is now possible to trace all variables from the $_SERVER superglobal.
  • It is now possible to trace the resources used by publication events when using asynchronous publishing

Notable bugfixes:

  • the javascript loading in frontend design for xhprof-measurement is disabled by default, as it can break some sites

Check out the changelog for a complete list

IMPORTANT: since version 0.8, enabling this extension has a negative impact on viewcache management.

All users are urged to upgrade

Major new functionality: works with oracle (including cluster) for eZPublish 5.0

A bugfix release coming on the heels of version 0.9.

The biggest change: works much better with statsd/graphite

Get it at http://projects.ez.no/ezperformancelogger/downloads/ezperformancelogger_0_9_1_zip

A release which brings some nice new features, making this swiss-army-knife of performance measurement more useful than ever:

  • support for eZP 5 (when running the Legacy Stack)
  • can trace events from the event subsystem, such as cache clearing and image-alias generation
  • now has full support for tracing database operations and cluster operations - with debug mode off - for all eZ versions from 4.5 to 5.0
  • supports tracing time spent while generating images with imagemagick as well
  • adds (experimental) support for sending data directly to a Pinba server
  • last but not least, it fixes the only known bug ;-)

A release I am particularly proud of, it brings a whole new world to eZ monitoring: out-of-the box integration with Munin to display graphs!

Read on after the break for more details...

* New features
. performance metrics can be logged to syslog
. filters can be added to only log performance data when specific conditions apply.
  This allows to e.g. replicate the equivalent of the mysql slow query log
* Bugfixes
. make the record_value template operator actually do something

A big improvement in this version: besides tracing performance counters, we now support real profiling of webpage execution, via the XHProf.

Tthis means giving developers an easy to use profiling GUI, which you can see in action here

A huge amount of new features in this version:

  • can log any custom variable set by the developer besides the standard ones
  • can parse the Apache acces logs and extract the performance data to csv format
  • can log to a file formatted just like the Apache access log even when used from other webservers or in fastcgi mode
  • can log directly to a csv file

This version adds support for logging the number of database queries executed, besides total memory and execution time, but also allows logging performance data directly to piwik or google analytics instead of the apache log