proxiblue / newrelic

Magento New Relic Integration

NewRelic

NOTE: NewRelic depricated teh Data Access key (and most likely the API with it) This module is most likely no longer functional, and I have no time to update it ongoing.

It is now simply here for historical purposes

Magento New Relic Integration http://www.proxiblue.com.au/newrelic-magento-integration.html

This module will allow in depth connection between the amazing New Relic Performance Monitoring System and your Magento website. Uses the awesome New Relic API to submit and collect data. Notice immediately what your Magento site is up to, and how it affects your site performance.

Compatible with Magento CE 1.6+ and EE 1.11+ Requirements: New Relic Pro or higher for full functionality New Relic PHP agent installed PHP5.3+

Can be made compatible to older magento versions (php5.2), with a bit of chnages.

Refer to #22 (if you do this, and find more changes, please feed back changes for other users)

Multiple Application Names After install

A few users have noted that after the module was installed, a new application name appeared in NewRelic. Please see the answer on issue #17 which explains why this is happening (see the last answer by ProxiBlue)

The sweet and short: Make sure your application name in the newrelic agent ini is correct.

Features

Mark Cache clear events on New Relic graphs
Mark Index events on New Relic graphs
Send log entries to New Relic Stack trace for log entries in New Relic
Send Magento exceptions to New Relic - Notice when your site has problems
Limit certain log and exception entries from logging to New Relic. Keep the 'noise' out, so you can focus on the real errors and events
Embed New Relic Graphs in your Dashboard. Make it easy to monitor your site performance directly from Magento admin
Retain in depth analytics in New Relic
Easy to install,
Easy to use Block admin access to be send metrics. Stop admin from scewing your apdex score!
Block specific modules to send metrics.
Ability to set named transactions
Ability to add module name to named transactions

This is not an official New Relic product, and is not endorsed by New Relic. This module is currently given FREE

Compatibility with Firegento Logger

ref: https://github.com/firegento/firegento-logger

Edit the config.xml file of the ProxiBlue module. Find the entry for the log writer.

    <log>
        <core>
            <writer_model>ProxiBlue_NewRelic_Model_Log_Writer_Stream</writer_model>
        </core>
    </log>

and change it to

    <log>
        <core>
            <!-- <writer_model>ProxiBlue_NewRelic_Model_Log_Writer_Stream</writer_model> -->
            <writer_models>
                <newrelic>
                    <label>ProxiBlue NewRelic Logger</label>
                    <class>ProxiBlue_NewRelic_Model_Log_Writer_Stream</class>
                </newrelic>
            </writer_models>
        </core>
    </log>

After this change you will find an entry for the ProxiBlue NewRelic Logger in the Firegento Logger list of available loggers, and you can then control logging to newRelic via the Firegento Logger system

Our Premium extensions:

Magento Free Gift Promotions The ultimate magento gift promotions module - clean code, and it just works!

Magento Dynamic Category Products Automate Category Product associations - assign any product to a category, using various rules.

newrelic's Issues

newrelic_base_url is not defined

Getting this js error when I fill in my api key and press:

Similarly, if I manually fill in the details and press Fetch Application Names
Same js error

Default application name used instead of configuration

I just installed and deployed your extension.

I did all the configuration, events are reported to the correct application. However regular NewRelic PHP agent data goes to PHP Application app which is defined in newrelic.ini.

I don't think that it is a server issue, as I had Yireo's extension and when setting the app name there it was considered.

Looks like some admin transactions still screw the apdex score.

Hi Lucas,
Thanks a lot for the plugin. It's very helpful.

I have v0.1.12 and found the following issue:

The config is set to ignore admin requests: http://screencast.com/t/XGA26NIZ
But it looks like some of the transactions still make it to New Relic: http://screencast.com/t/ZfoTqixl.

Thanks,
Lex

Nothing visible

I just installed the extension via modman. Enabled symlinks and removed the var/cache directory. Unfortunately, I can't find a trace of the extension the Magento admin. Also under system -> Advanced the extension is not visible...

What did I miss?

New Error format in New Relic

About a week ago my errors in New Relic changed to be a lot longer so that they included "Noticed Exception...". Example below.

Any idea what caused this and how I can get them to shorten back to their original length?

Mage_Core_Exception: Noticed exception 'Mage_Core_Exception' with message 'Please specify the product's option(s).' in /home/freeflyapparel/public_html/app/Mage.php:595

Help URLs don't work correctly.

The documentation urls like How to find your graph urls and How to find your API Key are dead...

Renaming a few methods (layout related)

I'd like to contribute a piece that alters Mage_Core_Layout::createBlock('suppressed/blockargument') into Visible_Blockargument::createLayout() for transaction traces and was looking into New Relic API support. I think it can be done with a custom tracer, but was wondering if you guys had looked into this and if so can you share your insights?
If I use a custom tracer, it seems like I need to implement a lot more then just name change which could introduce errors, so I'm torn between requesting a feature with New Relic to support alternative names for method calls or go ahead and code a custom tracer. Maybe there is a third option I'm not seeing.

Magento CE 1.8 does not work?

Its seems this plugin does not work with Magento CE 1.8? I am unable to retrieve my Account ID settings although I am sure the API key is correct, active and Magento configuration is saved.

Dashboard graph script error (fixed with 0.1.7)

When l load up the dashboard graph in Magento, I get the following script error:

HierarchyRequestError: DOM Exception 3: A Node was inserted somewhere it doesn't belong.

New Relic Insights

Insights is currently in Beta but I've been playing around with it and it's very powerful in terms of the general information that New Relic collects. It's also ridiculously fast and real-time, which is kind of fun to watch while page view and transaction numbers update every few seconds.

Anyway, what would be a very cool addition to this module would be the ability to define custom attributes to add in to various places in Magento that would then send off that data to New Relic. For example, the ability to insert the required attribute code into the checkout confirmation page to send off info to New Relic such as product name or product category or even things like payment method or shipment method.

You can see some info on custom attributes at https://docs.newrelic.com/docs/insights/custom-attributes and if you're interested or think it would be a useful or reasonable thing to add into this module, you can let me know and you can also take a look at our New Relic Insights beta account, if you want to check it out.

Version tags

This is a great module. We'd like to use it on our magento sites, in which we use composer to pull in components.

We would like to be able to specify a version rather than pulling from dev-master, but that would need tags adding for > 0.1.2

Could these please be added?

If you have ideas for improving this module, please add them to the issues, as we are interested in helping maintain and improve this.

Named Transactions on Magento 1.5.1.0 show /index.php

Hi,

Great extension. Thank you!

We used to run the Yireo extension, with the "named transactions" enabled. These showed in NewRelic as the request URI.

After switching to your plugin, all of our named transactions show as /index.php (with the request URI in grey below it). This means makes it impossible to track key transactions.

Is this a bug? Or an incompatibility with 1.5.1.0?

Many thanks,

Geoff

Registry key already exists

Hello there,
I was having an issue with the <class>proxiblue_newrelic/predispatch_observer</class> call in the config.xml file (line: 95). It was throwing a duplicate key error for some reason:

a:5:{i:0;s:75:"Mage registry key "_singleton/newrelic/predispatch_observer" already exists";i:1;s:1334:"#0 /vagrant/httpdocs/app/Mage.php(223): Mage::throwException('Mage registry k...')
#1 /vagrant/httpdocs/app/Mage.php(477): Mage::register('_singleton/newr...', false)
#2 /vagrant/httpdocs/app/code/core/Mage/Core/Model/App.php(1316): Mage::getSingleton('newrelic/predis...')

I made a fix by providing the full class to it <class>ProxiBlue_NewRelic_Model_Predispatch_Observer</class>, I hear that will be the standard in mage 2.0 anyways. Double checked with xDebug, observer method was firing in v1.9.1.
Cheers,
Konstantin

Template for dashboard needs renaming

In changing the namespace, Block/Adminhtml/Dashboard/Tab/Newrelic.php has had the path to the dashboard tab template changed to proxiblue_newrelic.phtml.phtml. However, the template has not been renamed. This causes a warning, which when developing with strict warnings turned on means that the admin panel does not work at all. Easy fix, though :)

Mage/Newrelic/Model/Log/Exception.php. No such file or directory

Warning: include(Mage/Newrelic/Model/Log/Exception.php) [function.include]: failed to open stream: No such file or directory in /var/www/html/lib/Varien/Autoload.php on line 92

Warning: include() [function.include]: Failed opening 'Mage/Newrelic/Model/Log/Exception.php' for inclusion (include_path='/var/www/html/app/code/local:/var/www/html/app/code/community:/var/www/html/app/code/core:/var/www/html/lib:.:/usr/share/pear:/usr/share/php') in /var/www/html/lib/Varien/Autoload.php on line 92

Multiple applications

Hi,

I set up newrelic on my servers this morning and all seemed to be going well. Then I installed your extension.

I now have 2 applications showing, both named exactly the same.

The original application is now showing page load times massively below what it was showing before installing the extension, while the new application seems to be showing the difference.

original application:

new application:

...what's the deal?

Wishilist activation in installer

Why is there an installer for enabling the wishlist.

I immediatelly disabled the wishlist back after installing, but it looks like that code should not be there

PHP Compatibility

This is probably minor for most installs but I just run into this issue.

The module is listed as being compatible with Magento CE 1.4 which in turn is compatible with PHP 5.2

However there is a rewrite of Mage_Core_Exception that uses PHP 5.3 constructor by passing the $previous parameter.

I think the correct fix here would be to make a notice in the README notifying compatibility with PHP 5.3+ as I don't think its worth the trouble to compatibilize with PHP 5.2 as it is absolutely deprecated.

Infinite loop in app/code/local/Mage/Core/Exception.php?

There are hundreds of entries like the following in the error logs:

[08-Apr-2014 00:12:26 UTC] PHP Fatal error: Aborting! The New Relic imposed maximum PHP function nesting level of '5000' has been reached. This limit is to prevent the PHP execution from catastrophically running out of C-stack frames. If you think this limit is too small, adjust the value of the setting newrelic.special.max_nesting_level in the newrelic.ini file, and restart php. Please file a ticket at https://support.newrelic.com if you need further assistance. in app/Mage.php on line 1472

and

[08-Apr-2014 00:17:01 UTC] PHP Fatal error: Maximum execution time of 180 seconds exceeded in app/code/local/Mage/Core/Exception.php on line 83