anjalirana/newrelic-bundle

Integrate New Relic into Symfony2 with ignore transactions update

Tuesday, March 10, 2015
by anjalirana
Repository
4 Watchers
0 Stars
5 Installations

PHP
0 Dependents
0 Suggesters
56 Forks
0 Open issues
7 Versions
0 % Grown

The README.md

Ekino NewRelic Bundle

, _(*1)

This bundle integrates the NewRelic PHP API into Symfony2. For more information about NewRelic, please visit http://newrelic.com., _(*2)

The bundle can use either the route name or the controller name as the transaction name. For CLI commands the transaction name is the command name., _(*3)

Result

Ekino NewRelicBundle , _(*4)

Installation

Step 0 : Install NewRelic

review http://newrelic.com ..., _(*5)

Step 1: Using Composer (recommended)

Use composer.phar:, _(*6)

$ php composer.phar require ekino/newrelic-bundle

You just have to specify the version you want : master-dev. It will add the package in your composer.json file and install it., _(*7)

Or you can do it by yourself, first, add the following to your composer.json file:, _(*8)

// composer.json
{
    // ...
    require: {
        // ...
        "ekino/newrelic-bundle": "master-dev"
    }
}

Then, you can install the new dependencies by running Composer's update command from the directory where your composer.json file is located:, _(*9)

$ php composer.phar update ekino/newrelic-bundle

Step 1 (alternative) : Using `deps` file (Symfony 2.0.x)

First, checkout a copy of the code. Just add the following to the deps file of your Symfony Standard Distribution:, _(*10)

[EkinoNewRelicBundle]
    git=http://github.com/ekino/EkinoNewRelicBundle.git
    target=/bundles/Ekino/Bundle/NewRelicBundle

Then, run, _(*11)

$ bin/vendors install

Make sure that you also register the namespace with the autoloader:, _(*12)

<?php

// app/autoload.php
$loader->registerNamespaces(array(
    // ...
    'Ekino'              => __DIR__.'/../vendor/bundles',
    // ...
));

Step 2 : Register the bundle

Then register the bundle with your kernel:, _(*13)

<?php

// in AppKernel::registerBundles()
$bundles = array(
    // ...
    new Ekino\Bundle\NewRelicBundle\EkinoNewRelicBundle(),
    // ...
);

Step 3 : Configure the bundle

``` yaml, _(*14)

app/config/config.yml

ekino_new_relic: enabled: true # Defaults to true application_name: Awesome Application # default value in newrelic is "PHP Application", or whatever is set # as php ini-value api_key: # New Relic API license_key: # New Relic license key xmit: false # if you want to record the metric data up to the point newrelic_set_appname is called, set this to true logging: false # If true, logs all New Relic interactions to the Symfony log instrument: false # If true, uses enhanced New Relic RUM instrumentation (see below) log_exceptions: false # If true, sends exceptions to New Relic log_commands: true # If true, logs CLI commands to New Relic as Background jobs (>2.3 only) using_symfony_cache: false # Symfony HTTP cache (see below) transaction_naming: route # route, controller or service (see below) transaction_naming_service: ~ # Transaction naming service (see below) ignored_routes: [] # No transaction recorded for this routes ignored_paths: [] # No transaction recorded for this paths ignored_commands: [] # No transaction recorded for this commands (background tasks), _(*15)

## Enhanced RUM instrumentation

The bundle comes with an option for enhanced real user monitoring. Ordinarily the New Relic extension (unless disabled by configuration) automatically adds a tracking code for RUM instrumentation to all HTML responses. Using enhanced RUM instrumentation, the bundle allows you to selectively disable instrumentation on certain requests.

This can be useful if, e.g. you're returning HTML verbatim for an HTML editor.

If enhanced RUM instrumentation is enabled, you can *disable* instrumentation for a given request by passing along a ```_instrument``` request parameter, and setting it to ```false```. This can be done e.g. through the routing configuration.

## Transaction naming strategies

The bundle comes with two built-in transaction naming strategies. ```route``` and ```controller```, naming the New Relic transaction after the route or controller respectively. However, the bundle supports custom transaction naming strategies through the ```service``` configuration option. If you have selected the ```service``` configuration option, you must pass the name of your own transaction naming service as the ```transaction_naming_service``` configuration option.

The transaction naming service class must implement the ```Ekino\Bundle\NewRelicBundle\TransactionNamingStrategy\TransactionNamingStrategyInterface``` interface. For more information on creating your own services, see the Symfony documentation on [Creating/Configuring Services in the Container](http://symfony.com/doc/current/book/service_container.html#creating-configuring-services-in-the-container).

## Symfony HTTP Cache

When you are using Symfony's HTTP cache your `app/AppCache.php` will build up a response with your Edge Side Includes (ESI). This will look like one transaction in New Relic. When you set `using_symfony_cache: true` will these ESI request be separate transaction which improves the statistics. If you are using some other reverse proxy cache or no cache at all, leave this to false.

If true is required to set the `application_name`.

## Deployment notification

You can use the `newrelic:notify-deployment` command to send deployment notifications to New Relic. This requires the `api_key` configuration to be set.

The command has a bunch of options, as displayed in the help data.

$ app/console newrelic:notify-deployment --help Usage: newrelic:notify-deployment [--user[="..."]] [--revision[="..."]] [--changelog[="..."]] [--description[="..."]], _(*16)

Options: --user The name of the user/process that triggered this deployment --revision A revision number (e.g., git commit SHA) --changelog A list of changes for this deployment --description Text annotation for the deployment — notes for you, _(*17)


The bundle provide a [Capifony](http://capifony.org) recipe to automate the deployment notifications (see `Resources/recipes/newrelic.rb`).

## Integration with SonataBlockBundle

### Step 0: Install SonataBlockBundle

Review [SonataBlockBundle](http://sonata-project.org/bundles/block/master/doc/reference/installation.html)

### Step 1: Enable your block:

``` yaml
# app/config/config.yml

sonata_block:
    blocks:
        ekino.newrelic.block.simple:
        ekino.newrelic.block.tabs:

Integration with SonataAdminBundle

Step 0: Install SonataBlockBundle

Review preview section, _(*18)

Step 1: Install SonataAdminBundle

Review SonataAdminBundle installation, _(*19)

Step 1: Enable your block:

``` yaml, _(*20)

app/config/config.yml

sonata_block: blocks: ekino.newrelic.block: ... sonata_admin: ... dashboard: blocks: - { position: left, type: ekino.newrelic.block.simple, settings: { reference: 3Y5rCib3JmH # Url charts (https://... or 3Y5rCib3JmH) } }, _(*21)


More details for [configuration](http://sonata-project.org/bundles/admin/master/doc/reference/configuration.html) SonataAdminBundle

## Integration with Twig

``` twig
{{ sonata_block_render({ 'type': 'ekino.newrelic.block.simple' }, {
    'reference': '3Y5rCib3JmH'
}) }}

More details for Twig extension, _(*22)