Multiple applications about newrelic

[ProxiBlue]

Interesting.
This has not been seen before.

I gather you have two servers serving your magento site?

Is there a possibility I can gain access to your newrelic account, so I can have a look at this, and see if I can find some reason behind this.

You cam email me directly using sales at proxiblue.com.au with those particulars

Can you also send me the newrelic configuration files for each server.

[Tall-Paul]

Hi, I actually have 5 servers.

I'll email you with the newrelic info now

[Tall-Paul]

I've added you as a user on our newrelic account, you should get a welcome email from them.

[ProxiBlue]

Great, that will help. Can you also attach an image of the module configuration. This will allow me to have the exact same settings to try and replicate this

with 5 servers, are these 5 frontends?

As I see it we have some possible reasons for this:

1. Something has changed in the newrelic api, which means all users will soon be having this issue.
2. Something odd / different in your configuration, which the module cannot account for...
3. Nothing wrong with the module, and an issue in your config setup.

I'l work my way through this....

[ProxiBlue]

For continuity of the ticket information:

Via direct email from Tall-Paul:

Something else that just occurred to me, we have another magento instance running on the app1 server, our staging site (staging.prettylittlething.com) which doesn’t have your magento module installed but does run on the same nginx / php-fpm server as app1…. could that be causing this issue?

and a response from ProxiBlue:

Yes, I think this is potentially the issue.
Looking at your newrelic output I can see that one instance do not have the module names attached to the transactions.
This is added by my module.
Thus in the live sites, my module is causing newrelic to see the reporting as a separate instance, even though the instance names are the same. This could be caused by the named transactions, or by the add module names to transactions.

You could try and set those to 'no', and see if the instances merge. (you will see the old one, but it would state that it is not collecting data)

Another solution would be to install the module into your staging as well, see if that merges the instances.

I will be experimenting with a setup like that, see if I can see why this is happening, however I am a bit strapped for time to debug this for a few weeks.

[ProxiBlue]

Also, have you configured your staging and live sites as multiple applications.

ref: https://docs.newrelic.com/docs/agents/php-agent/configuration/php-directory-ini-settings

[barbazul]

I have the exact same issue.

I have only one server running the application. Inmediately after I finished configurating the module in production I got a second application which started reporting all the trafic while the original one went mute.

[ProxiBlue]

Hi,

Very strange. Generally if every user complains about this, there would be a major issue with the module. None others have (except of course yourself and the other person on this ticket)
I never heard back from them and assumed the issue was solved, and caused by the dev/testing site that also used the same newrelic configuration.

Can you add me to your newrelic account, so I can have a look at your data?
Please use the email lucas @ vanstaden.com.au

[barbazul]

There. I just addedd you.

Something I noticed today is that trace reports for custom modules are reporting most of the time consumed in a single line that reads "Application code..." so there is really no way to track what's going on with those traces.

[ProxiBlue]

Thanks for adding me, but you set me as a restricted user.
Since I don't exactly know what it is that I am looking for, restricted user may hide that key bit of information to debug this.

Can you also email me your newrelic agent configuration files, as the reason my be contained in those.

Possible you can increase the access level to admin?

As for the trace reports, can you point me to one (a link will do) - would hate wasting time hunting stuff down, and looking at the wrong information.

[ProxiBlue]

The multiple application names explained:

The problem is two fold.

The first part is that, in your setup, you did not name your PHP Appliation in the NewRelic configuration.
This would have been done in the PHP ini settings

https://docs.newrelic.com/docs/agents/php-agent/configuration/php-agent-configuration#inivar-appname

The application is reporting as 'PHP Application' which is the default value in the ini config.
I can see this as per the configuration of that application:

In your setup, you had simply renamed the application name using the NewRelic admin, so it is visually what you want.

The second part (and the end reason why a new application came in)

The NewRelic module sets the application name during processing.

public function setAppName(){ if (extension_loaded('newrelic')) { $application_name = Mage::getStoreConfig('newrelic/api/application_name'); $license_key = Mage::getStoreConfig('newrelic/api/license_key'); return newrelic_set_appname($application_name,$license_key,true); } }

The issue is that I am setting the appname,a s per the App Name passed back by NewRelic when making a query to their API for the list of application names available.

This is the list that gets populated in the admin, where you select the app name.
It would seem they pass back the visual name change for that api call.

I can see this in the new application configuration:

This then effectively created a new application in NewRelic, as the name is now different.

#explained ;)

[dbashyal]

Thanks Lucas. That fixed the multiple application issue for me too :)