newrelic_rpm 4.0.0.332 → 4.8.0.341

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 6f033acf8bf5efe89fd548f55aba3e3b7b9c58e2
-  data.tar.gz: 0e523aeaaca318f6bf863c4f7b9269d4b212f63a
+  metadata.gz: b51f94bfacea16c929d073a557db1c96c171da40
+  data.tar.gz: 6b593714cfad1a3751dd07b410ba300fe46e4751
 SHA512:
-  metadata.gz: 9b18921ad5e63244778c06a6d45fcf7fa556a19cac8eb61f58cdfce341033ea87c9e9c3eb1832c8c5c3dd4ce9ad30030340497772c5a1144bfd408b2be0dfd0e
-  data.tar.gz: 809cc815755c0d2be8555ac9e8bec2d057a849617e196e62644131588d7c8a697f19f1e91a1f73f0c4ace692efbd1d7ece2ce7996548a2f1828c7cd56b0649a9
+  metadata.gz: 88aa0416e6c2a3f8e32b6b5536e1b4f58b5b423ce06085ba583830fca6c014c04ea318bad3b48bcc17f5f93506d27f1ac7fed3ce56fb157cfd43830650c74652
+  data.tar.gz: afc0971db514b4b76e93725c6c7b299e26a281ba0a8cee2add9aba30a149f0c20a0dc74d7d08363f4977a54c5dc90f2e897edf64d2fa658cf286cc18358cc978

data/.travis.yml

@@ -2,6 +2,7 @@ services:
   - mysql
   - redis-server
   - memcached
+  - rabbitmq
 
 language: ruby
 
@@ -9,6 +10,7 @@ sudo: required
 
 before_install:
   - gem --version
+  - gem update --system
   - ./test/script/before_install/gemstash_mirror.sh
   - bundle --version
 
@@ -31,10 +33,11 @@ notifications:
 
 rvm:
   # Run slowest builds first to try and optimize overall cycle time.
-  - jruby-9.1.2.0
-  - 2.4.0
-  - 2.3.3
-  - 2.2.6
+  - jruby-9.1.13.0
+  - 2.5.0
+  - 2.4.2
+  - 2.3.5
+  - 2.2.8
   - 2.1.10
   - 2.0.0-p648
 
@@ -61,6 +64,7 @@ env:
     - TYPE=UNIT ENVIRONMENT=rails41
     - TYPE=UNIT ENVIRONMENT=rails42
     - TYPE=UNIT ENVIRONMENT=rails50
+    - TYPE=UNIT ENVIRONMENT=rails51
     - TYPE=UNIT ENVIRONMENT=norails
     - TYPE=FUNCTIONAL GROUP=agent
     - TYPE=FUNCTIONAL GROUP=api
@@ -78,40 +82,56 @@ matrix:
   fast_finish: true
   exclude:
     # Unsupported Rails/Ruby combinations
+    # 2.5
+    - rvm: 2.5.0
+      env: TYPE=UNIT ENVIRONMENT=rails21
+    - rvm: 2.5.0
+      env: TYPE=UNIT ENVIRONMENT=rails22
+    - rvm: 2.5.0
+      env: TYPE=UNIT ENVIRONMENT=rails23
+    - rvm: 2.5.0
+      env: TYPE=UNIT ENVIRONMENT=rails30
+    - rvm: 2.5.0
+      env: TYPE=UNIT ENVIRONMENT=rails31
+    - rvm: 2.5.0
+      env: TYPE=UNIT ENVIRONMENT=rails32
+    - rvm: 2.5.0
+      env: TYPE=UNIT ENVIRONMENT=rails40
+    - rvm: 2.5.0
+      env: TYPE=UNIT ENVIRONMENT=rails41
+
     # 2.4
-    - rvm: 2.4.0
+    - rvm: 2.4.2
       env: TYPE=UNIT ENVIRONMENT=rails21
-    - rvm: 2.4.0
+    - rvm: 2.4.2
       env: TYPE=UNIT ENVIRONMENT=rails22
-    - rvm: 2.4.0
+    - rvm: 2.4.2
       env: TYPE=UNIT ENVIRONMENT=rails23
-    - rvm: 2.4.0
+    - rvm: 2.4.2
       env: TYPE=UNIT ENVIRONMENT=rails30
-    - rvm: 2.4.0
+    - rvm: 2.4.2
       env: TYPE=UNIT ENVIRONMENT=rails31
-    - rvm: 2.4.0
+    - rvm: 2.4.2
       env: TYPE=UNIT ENVIRONMENT=rails32
-    - rvm: 2.4.0
+    - rvm: 2.4.2
       env: TYPE=UNIT ENVIRONMENT=rails40
-    - rvm: 2.4.0
+    - rvm: 2.4.2
       env: TYPE=UNIT ENVIRONMENT=rails41
-    - rvm: 2.4.0
-      env: TYPE=UNIT ENVIRONMENT=rails42
 
     # 2.3
-    - rvm: 2.3.3
+    - rvm: 2.3.5
       env: TYPE=UNIT ENVIRONMENT=rails21
-    - rvm: 2.3.3
+    - rvm: 2.3.5
       env: TYPE=UNIT ENVIRONMENT=rails22
-    - rvm: 2.3.3
+    - rvm: 2.3.5
       env: TYPE=UNIT ENVIRONMENT=rails23
 
     # 2.2
-    - rvm: 2.2.6
+    - rvm: 2.2.8
       env: TYPE=UNIT ENVIRONMENT=rails21
-    - rvm: 2.2.6
+    - rvm: 2.2.8
       env: TYPE=UNIT ENVIRONMENT=rails22
-    - rvm: 2.2.6
+    - rvm: 2.2.8
       env: TYPE=UNIT ENVIRONMENT=rails23
 
     # 2.1
@@ -123,6 +143,8 @@ matrix:
       env: TYPE=UNIT ENVIRONMENT=rails23
     - rvm: 2.1.10
       env: TYPE=UNIT ENVIRONMENT=rails50
+    - rvm: 2.1.10
+      env: TYPE=UNIT ENVIRONMENT=rails51
 
     # 2.0
     - rvm: 2.0.0-p648
@@ -133,17 +155,19 @@ matrix:
       env: TYPE=UNIT ENVIRONMENT=rails23
     - rvm: 2.0.0-p648
       env: TYPE=UNIT ENVIRONMENT=rails50
+    - rvm: 2.0.0-p648
+      env: TYPE=UNIT ENVIRONMENT=rails51
 
     # jruby 9.0
-    - rvm: jruby-9.1.2.0
+    - rvm: jruby-9.1.13.0
       env: TYPE=UNIT ENVIRONMENT=rails21
-    - rvm: jruby-9.1.2.0
+    - rvm: jruby-9.1.13.0
       env: TYPE=UNIT ENVIRONMENT=rails22
-    - rvm: jruby-9.1.2.0
+    - rvm: jruby-9.1.13.0
       env: TYPE=UNIT ENVIRONMENT=rails23
-    - rvm: jruby-9.1.2.0
+    - rvm: jruby-9.1.13.0
       env: TYPE=UNIT ENVIRONMENT=rails30
-    - rvm: jruby-9.1.2.0
+    - rvm: jruby-9.1.13.0
       env: TYPE=UNIT ENVIRONMENT=rails31
-    - rvm: jruby-9.1.2.0
+    - rvm: jruby-9.1.13.0
       env: TYPE=UNIT ENVIRONMENT=rails32

data/.yardopts

@@ -2,19 +2,21 @@
 --api public
 lib/new_relic/agent.rb
 lib/new_relic/agent/method_tracer.rb
+lib/new_relic/agent/external.rb
 lib/new_relic/agent/instrumentation/controller_instrumentation.rb
 lib/new_relic/agent/instrumentation/rack.rb
 lib/new_relic/agent/instrumentation/metric_frame.rb
 lib/new_relic/agent/stats_engine/metric_stats.rb
 lib/new_relic/agent/datastores.rb
+lib/new_relic/agent/messaging.rb
 lib/new_relic/agent/sql_sampler.rb
 lib/new_relic/agent/transaction.rb
 lib/new_relic/agent/transaction_sampler.rb
-lib/new_relic/rack/developer_mode.rb
 lib/new_relic/rack/agent_hooks.rb
 lib/new_relic/rack/browser_monitoring.rb
 lib/new_relic/rack/error_collector.rb
 lib/new_relic/rack.rb
+lib/new_relic/agent/transaction/external_request_segment.rb
 -
 LICENSE
 CHANGELOG

data/CHANGELOG.md

@@ -1,5 +1,270 @@
 # New Relic Ruby Agent Release Notes #
 
+  ## v4.8.0 ##
+
+  * Initialize New Relic Agent before config initializers
+
+  When running in a Rails environment, the agent registers an initializer that
+  starts the agent. This initializer is now defined to run before config/initializers.
+  Previously, the ordering was not specified for the initializer. This change
+  guarantees the agent will started by the time your initializers run, so you can
+  safely reference the Agent in your custom initializers. Thanks to Tony Ta for
+  the contribution.
+
+  * Ruby 2.5 Support
+
+  The Ruby Agent has been verified to run under Ruby 2.5.
+
+  * `request.uri` Collected as an Agent Attribute
+
+  Users can now control the collection of `request.uri` on errors and transaction
+  traces. Previously it was always collected without the ability to turn it off.
+  It is now an agent attribute that can be controlled via the attributes config.
+  For more information on agent attributes [see here](https://docs.newrelic.com/docs/agents/manage-apm-agents/agent-data/agent-attributes).
+
+  ## 4.7.1 ##
+
+  * Bugfix for Manual Browser Instrumentation
+
+  There was a previous bug that required setting both `rum.enabled: false` and
+  `browser.auto_instrument: false` to completely disable browser monitoring. An
+  attempt to fix this in 4.7.0 resulted in breaking manual browser
+  instrumentation. Those changes have been reverted. We will revisit this issue
+  in an upcoming release.
+
+  ## v4.7.0 ##
+
+  * Expected Error API
+
+  The agent now sends up `error.expected` as an intrinsic attribute on error
+  events and error traces. When you pass `expected: true` to the `notice_error`
+  method, both Insights and APM will indicate that the error is expected.
+
+  * Typhoeus Hydra Instrumentation
+
+  The agent now has request level visibility for HTTP requests made using
+  Typhoeus Hydra.
+
+  * Total Time Metrics are Recorded
+
+  The agent now records Total Time metrics. In an application where segments
+  execute concurrently, the total time can exceed the wall-clock time for a
+  transaction. Users of the new Typhoeus Hydra instrumentation will notice
+  this as changes on the overview page. Immediately after upgrading there
+  will be an alert in the APM dashboard that states: "There are both old and
+  new time metrics for this time window". This indicates that during that time
+  window, some transactions report the total time metrics, while others do not.
+  The message will go away after waiting for enough time to elapse and / or
+  updating the time window.
+
+  * Add `:message` category to `set_transaction_name` public API method
+
+  The agent now permits the `:message` category to be passed into the public
+  API method `set_transaction_name`, which will enable the transaction to be
+  displayed as a messaging transaction.
+
+  * Create `prepend_active_record_instrumentation` config option
+
+  Users may now set the `prepend_active_record_instrumentation` option in
+  their agent config to install Active Record 3 or 4 instrumentation using
+  `Module.prepend` rather than `alias_method`.
+
+  * Use Lazy load hooks for `ActionController::Base` and `ActionController::API`
+
+  The agent now uses lazy load hooks to hook on `ActionController::Base` and
+  `ActionController::API`. Thanks Edouard Chin for the contribution!
+
+  * Use Lazy load hooks for `ActiveRecord::Base` and `ActiveRecord::Relation`
+
+  The agent uses lazy load hooks when recording supportability metrics
+  for `ActiveRecord::Base` and `ActiveRecord::Relation`. Thanks Joseph Haig
+  for the contribution!
+
+  * Check that `Rails::VERSION` is defined instead of just `Rails`
+
+  The agent now checks that `Rails::VERSION` is defined since there are cases
+  where `Rails` is defined but `Rails::VERSION` is not. Thanks to Alex Riedler
+  and nilsding for the contribution!
+
+  * Support fast RPC/direct reply-to in RabbitMQ
+
+  The agent can now handle the pseudo-queue 'amq.rabbitmq.reply-to' in its
+  Bunny instrumentation. Previously, using fast RPC led to a `NoMethodError`
+  because the reply-to queue was expected to be a `Queue` object instead of
+  a string.
+
+## v4.6.0 ##
+
+  * Public API for External Requests
+
+  The agent now has public API for instrumenting external requests and linking
+  up transactions via cross application tracing. See the [API Guide](https://docs.newrelic.com/docs/agents/ruby-agent/customization/ruby-agent-api-guide#externals)
+  for more details this new functionality.
+
+## v4.5.0 ##
+
+  * Send synthetics headers even when CAT disabled
+
+  The agent now sends synthetics headers whenever they are received from an
+  external request, even if cross-application tracing is disabled.
+
+  * Bugfix for DelayedJob Daemonization
+
+  Customers using the delayed_job script that ships with the gem may encounter
+  an IOError with a message indicating the stream was closed. This was due to
+  the agent attempting to write a byte into a Pipe that was closed during the
+  deamonization of the delayed_job script. This issue has been fixed.
+
+  * Collect supportability metrics for public API
+
+  The agent now collects Supportability/API/{method} metrics to track usage of
+  all methods in the agent's public API.
+
+  * Collect supportability metrics on `Module#prepend`
+
+  The agent now collects Supportability/PrependedModules/{Module} metrics
+  for ActiveRecord 4 and 5, ActionController 4 and 5, ActionView 4 and 5,
+  ActiveJob 5, and ActionCable 5. These help track the adoption of the
+  `Module#prepend` method so we can maintain compatibility with newer versions
+  of Ruby and Rails.
+
+  * Collect explain plans when using PostGIS ActiveRecord adapter
+
+  The agent will now collect slow SQL explain plans, if configured to, on
+  connections using the PostGIS adapter. Thanks Ari Pollak for the contribution!
+
+  * Lazily intialize New Relic Config
+
+  The agent will lazily initialize the New Relic config. This allows the agent
+  to pickup configuration from environment variables set by dotenv and similar
+  tools.
+
+## v4.4.0 ##
+
+  * Include test helper for 3rd party use
+
+  In 4.2.0, all test files were excluded from being packaged in the gem. An
+  agent class method `NewRelic::Agent.require_test_helper` was used by 3rd
+  party gem authors to test extensions to the agent. The required file is now
+  included in the gem.
+
+  * Collect cloud metadata from Azure, GCP, PCF, and AWS cloud platform
+
+  The agent now collects additional metadata when running in AWS, GCP, Azure, and
+  PCF. This information is used to provide an enhanced experience when the agent
+  is deployed on those platforms.
+
+  * Install `at_exit` hook when running JRuby
+
+  The agent now installs an `at_exit` hook when running JRuby, which wasn't
+  done before because of constraints related to older JRuby versions that
+  are no longer supported.
+
+  * User/Utilization and System/Utilization metrics not recorded after Resque forks
+
+  The agent no longer records invalid User/Utilization and System/Utilization
+  metrics, which can lead to negative values, in forks of Resque processes.
+
+  * Add `identifier` field to agent connect settings
+
+  The agent now includes a unique identifier in its connect settings, ensuring
+  that when multiple agents connect to multiple different apps, data are reported
+  for each of the apps.
+
+  * Clear transaction state after forking now opt-in
+
+  The agent waits to connect until the first web request when it detects it's
+  running in a forking dispatcher. When clearing the transaction state in this
+  situation we lose the first frame of the transaction and the subsequent
+  trace becomes corrupted. We've made this feature opt-in and is turned off by
+  default. This behavior only affects the first transaction after a dispatcher
+  forks.
+
+## v4.3.0 ##
+
+  * Instrumentation for the Bunny AMQP Client
+
+  The Bunny AMQP Client is now automatically instrumented. The agent will
+  report data for messages sent and received by an application. Data on messages
+  is available in both APM and Insights. Applications connected through a
+  RabbitMQ exchange will now also be visible on Service Maps as part of Cross
+  Application Tracing. See the [message queues documentation page](https://docs.newrelic.com/docs/agents/ruby-agent/features/message-queues)
+  for more details.
+
+  * Safely normalize external hostnames
+
+  The agent has been updated to check for nil host values before downcasing the
+  hostname. Thanks Rafael Valério for the contribution!
+
+  * PageView events will not be generated for ignored transactions
+
+  The agent now checks if transaction is ignored before injecting the New Relic
+  Browser Agent. This will prevent PageView events from being generated for
+  ignored transactions.
+
+  * Datastores required explicitly in agent
+
+  The agent has been modified to explicity `require` the Datastores module
+  whereas previously there were situations where the module could be
+  implicitly defined. Thanks Kevin Griffin for the contribution!
+
+  * Clear transaction state after forking
+
+  Previously, if a transaction was started and the process forks, the transaction
+  state survived the fork and `#after_fork` call in thread local storage. Now,
+  this state is cleared by `#after_fork`.
+
+  * Postgis adapter reports as Postgres for datastores
+
+  The agent now maps the Postgis adapter to Postgres for datastore metrics.
+  Thanks Vojtěch Vondra for the contribution!
+
+  * Deprecate `:trace_only` option
+
+  The `NewRelic::Agent.notice_error` API has been updated to deprecate the
+  `:trace_only` option in favor of `:expected`.
+
+## v4.2.0 ##
+
+  * Sinatra 2.0 and Padrino 0.14.x Support
+
+  The agent has been verified against the latest versions of Sinatra and Padrino.
+
+  * Rails 5.1 Support
+
+  The Ruby agent has been validated against the latest release of Ruby on Rails!
+
+  * APP_ENV considered when determining environment
+
+  The agent will now consider the APP_ENV environment when starting up.
+
+  * Test files excluded from gem
+
+  The gemspec has been updated to exclude test files from being packaged into the
+  gem. Thanks dimko for the contribution!
+
+## v4.1.0 ##
+
+  * Developer Mode removed
+
+  The Ruby Agent's Developer Mode, which provided a very limited view of your
+  application performance data, has been removed. For more information, check
+  out our [community forum](https://discuss.newrelic.com/t/feedback-on-the-ruby-agent-s-developer-mode/46957).
+
+  * Support NEW_RELIC_ENV for Rails apps
+
+  Previously, users could set the agent environment with NEW_RELIC_ENV only
+  for non-Rails apps. For Rails app, the agent environment would use whatever
+  the Rails environment was set to. Now, NEW_RELIC_ENV can also be used for
+  Rails apps, so that it is possible to have an agent environment that is
+  different from the Rails environment. Thanks Andrea Campolonghi for the
+  contribution, as well as Steve Schwartz for also looking into this issue!
+
+  * Normalization of external hostnames
+
+  Hostnames from URIs used in external HTTP requests are now always downcased
+  to prevent duplicate metrics when only case is different.
+
 ## v4.0.0 ##
 
   * Require Ruby 2.0.0+

data/LICENSE

@@ -1,30 +1,4 @@
-This product includes jquery 1.4.2, written by John Resig
-and distributed under an MIT license.
-See https://github.com/jquery/jquery/blob/1.4.2/MIT-LICENSE.txt
-
-    Copyright (c) 2010 John Resig, http://jquery.com/
-
-    Permission is hereby granted, free of charge, to any person obtaining
-    a copy of this software and associated documentation files (the
-    "Software"), to deal in the Software without restriction, including
-    without limitation the rights to use, copy, modify, merge, publish,
-    distribute, sublicense, and/or sell copies of the Software, and to
-    permit persons to whom the Software is furnished to do so, subject to
-    the following conditions:
-
-    The above copyright notice and this permission notice shall be
-    included in all copies or substantial portions of the Software.
-
-    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-    EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-    MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-    NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-    LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-    OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-    WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-All other components of this product are
+All components of this product are
 Copyright (c) 2008-2017 New Relic, Inc.  All rights reserved.
 
 Certain inventions disclosed in this file may be claimed within

data/README.md

@@ -3,21 +3,10 @@
 New Relic is a performance management system, developed by
 New Relic, Inc (http://www.newrelic.com).  It provides you with deep
 information about the performance of your Rails or Ruby
-application as it runs in production. The New Relic Ruby Agent is
-dual-purposed as a either a Gem or a Rails plugin, hosted on
-[github](https://github.com/newrelic/rpm/tree/master).
-
-The New Relic Ruby Agent runs in one of two modes:
-
-**Production Mode**
-Low overhead instrumentation that captures detailed information on
-your application running in production and transmits them to
-newrelic.com where you can monitor them in real time.
-
-**Developer Mode**
-A Rack middleware that maps `/newrelic` to an application for showing
-detailed performance metrics on a page by page basis.  Installed
-automatically in Rails applications.
+application as it runs in production and transmits them to
+newrelic.com where you can monitor them in real time. The New Relic
+Ruby Agent is dual-purposed as a either a Gem or a Rails plugin,
+hosted on [github](https://github.com/newrelic/rpm/tree/master).
 
 ## Supported Environments
 
@@ -90,9 +79,6 @@ Then make sure you set `RACK_ENV` to the environment corresponding to the
 configuration definitions in the newrelic.yml file; e.g., development,
 staging, production, etc.
 
-To use Developer Mode in Sinatra, add `NewRelic::Rack::DeveloperMode` to
-the middleware stack.  See the `config.ru` sample below.
-
 #### Other Environments
 
 You can use the Ruby Agent to monitor any Ruby application. Add:
@@ -118,45 +104,6 @@ frameworks.  You can find a list of community created intrumentation plugins
 (e.g. [newrelic-redis](https://github.com/evanphx/newrelic-redis)) in the
 [extends_newrelic_rpm project](https://github.com/newrelic/extends_newrelic_rpm).
 
-## Developer Mode
-
-When running the Developer Mode, the Ruby Agent will track the
-performance of every HTTP request serviced by your application, and
-store in memory this information for the last 100 HTTP transactions.
-
-To view this performance information, including detailed SQL statement
-analysis, open `/newrelic` in your web application.  For instance if
-you are running mongrel or thin on port 3000, enter the following into
-your browser:
-
-    http://localhost:3000/newrelic
-
-Developer Mode is only initialized if the `developer_mode` setting in
-the newrelic.yml file is set to true.  By default, it is turned off in
-all environments but `development`.
-
-#### Developer Mode in Rails
-
-Developer Mode is available automatically in Rails Applications based
-on Rails 2.3 and later.  No additional configuration is required. When
-your application starts and `developer_mode` is enabled, the Ruby
-Agent injects a middleware into your Rails middleware stack.
-
-For earlier versions of Rails that support Rack, you can use
-a `config.ru` as below.
-
-#### Developer Mode in Rack Applications
-
-Developer Mode is available for any Rack based application such as
-Sinatra by installing the NewRelic::Rack::DeveloperMode
-middleware. This middleware passes all requests that do not start with
-/newrelic.
-
-Here's an example entry for Developer Mode in a `config.ru` file:
-
-    require 'new_relic/rack/developer_mode'
-    use NewRelic::Rack::DeveloperMode
-
 ## Production Mode
 
 When your application runs in the production environment, the New