Archival repost — originally published on my old blog on October 5, 2013. Already in English, lightly cleaned up for dev.to. New Relic's PHP agent and API have evolved a lot since, but the underlying idea — naming transactions manually instead of dumping everything into one bucket — is still exactly how you'd solve this today. The ezpublish-newrelic extension is still up on GitHub and Packagist if you want to see the actual code.
When using the New Relic PHP agent with an eZ Publish stack, every profiled transaction shows up under /index.php. Not exactly helpful when you're trying to figure out what's actually making your app struggle.
New Relic provides a self-explanatory PHP API. It lets you send additional metrics and data alongside whatever the agent already gathers — including a custom transaction name.
The eZ Publish extension I wrote, ezpublish-newrelic, hooks into that API to track modules and their views under separate, meaningful transaction names instead of one big /index.php bucket.
The source is on GitHub and installable via Composer from Packagist — feel free to contribute.
Top comments (0)