![]() ![]() Change via API: An option if you have access to modify your application code, are okay with instrumenting it directly, and find the trace continuity implications of this call acceptable.(This option does not break data continuity in APM.) Change alias via UI: This changes only the alias in the UI, not the underlying app name being reported.(Procedures for Apache, PHP-FPM, and NGINX in PHP-FPM are documented.) Set per-directory INI settings: Useful for when you have one web server serving multiple applications and want to have different settings or names for them.Although the package name references PHP 5, this package works for all supported PHP versions. Configure newrelic.ini file using newrelic.appname: The recommended and most commonly used option. The package name for New Relics PHP agent is newrelic-php5.Here are the ways to change your PHP application's name in New Relic: To change an application's name without breaking data continuity, use the UI alias-change option. When you change the name an application reports as, New Relic creates a new application entity and breaks data continuity between the new and old entity. ![]() I even spun up a brand new box and deployed it, adding the same configurations as the others, and it too started to zombie shortly after starting. Im able to replicate this problem across all of my web servers. New Relic differentiates applications by their name. Restarting PHP-FPM removes the zombie and the service works again for a few minutes, but goes back into a zombie state soon after. This document gives you an overview of those naming options.įor a general overview of APM app naming (not PHP-specific), see Name your application. ![]() New Relic for PHP gives you several ways to change the application name that is reported to, and displayed in, New Relic. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |