newrelic_rpm 3.6.3.103.beta → 3.6.3.104

data/CHANGELOG

@@ -1,6 +1,6 @@
 # New Relic Ruby Agent Release Notes #
 
-## 3.6.3 ##
+## v3.6.3 ##
 
   * Better Sinatra Support
 
@@ -9,13 +9,13 @@
 
   Sinatra instrumentation has been updated to more accurately reflect the final
   route that was actually executed, taking pass and conditions into account.
-  
+
   New Relic middlewares for error collection, real user monitoring, and cross
   application tracing are automatically inserted into the middleware stack.
-  
+
   Ignoring routes, similar to functionality available to Rails controllers, is
   now available in Sinatra as well.
-  
+
   Routes in 1.4 are properly formatting in transaction names. Thanks Zachary
   Anker for the contribution!
 
@@ -25,9 +25,9 @@
   supporting Padrino, a framework that builds on Sinatra. Web transactions
   should show up in New Relic now for Padrino apps automatically. The agent has
   been tested against the latest Padrino in versions 0.11.x and 0.10.x.
-  
+
   * Main overview graph only shows web transactions
-  
+
   In the past database times from background jobs mixed with other web transaction
   metrics in the main overview graph. This often skewed graphs. A common workaround
   was to send background jobs to a separate application, but that should no longer

data/lib/new_relic/build.rb

@@ -1,2 +1,2 @@
-# GITSHA: 0b3609118317f2a210341a12bcf8759e9978fd28
-module NewRelic; module VERSION; BUILD='103.beta'; end; end
+# GITSHA: 4fcb3cca4b114aade7a89991cba3363c50612865
+module NewRelic; module VERSION; BUILD='104'; end; end

metadata

@@ -1,8 +1,8 @@
 --- !ruby/object:Gem::Specification
 name: newrelic_rpm
 version: !ruby/object:Gem::Version
-  version: 3.6.3.103.beta
-  prerelease: 10
+  version: 3.6.3.104
+  prerelease: 
 platform: ruby
 authors:
 - Jason Clark
@@ -526,37 +526,26 @@ files:
 - lib/new_relic/build.rb
 homepage: http://www.github.com/newrelic/rpm
 licenses: []
-post_install_message: ! "# New Relic Ruby Agent Release Notes #\n\n## 3.6.3 ##\n\n*
+post_install_message: ! "# New Relic Ruby Agent Release Notes #\n\n## v3.6.3 ##\n\n*
   Better Sinatra Support\n\n  A number of improvements have been made to our Sinatra
   instrumentation.\n  More details: https://newrelic.com/docs/ruby/sinatra-support-in-the-ruby-agent\n\n
   \ Sinatra instrumentation has been updated to more accurately reflect the final\n
-  \ route that was actually executed, taking pass and conditions into account.\n  \n
+  \ route that was actually executed, taking pass and conditions into account.\n\n
   \ New Relic middlewares for error collection, real user monitoring, and cross\n
-  \ application tracing are automatically inserted into the middleware stack.\n  \n
+  \ application tracing are automatically inserted into the middleware stack.\n\n
   \ Ignoring routes, similar to functionality available to Rails controllers, is\n
-  \ now available in Sinatra as well.\n  \n  Routes in 1.4 are properly formatting
-  in transaction names. Thanks Zachary\n  Anker for the contribution!\n\n* Padrino
-  Support\n\n  Along with improving our support of Sinatra, we've also extended that
-  to\n  supporting Padrino, a framework that builds on Sinatra. Web transactions\n
-  \ should show up in New Relic now for Padrino apps automatically. The agent has\n
-  \ been tested against the latest Padrino in versions 0.11.x and 0.10.x.\n  \n* Main
-  overview graph only shows web transactions\n  \n  In the past database times from
-  background jobs mixed with other web transaction\n  metrics in the main overview
-  graph. This often skewed graphs. A common workaround\n  was to send background jobs
-  to a separate application, but that should no longer\n  be necessary as the overview
-  graphs now only represent web transactions.\n\n## v3.6.2 ##\n\n* Sequel support\n\n
-  \ The Ruby agent now supports Sequel, a database toolkit for Ruby. This\n  includes
-  capturing SQL calls and model operations in transaction traces, and\n  recording
-  slow SQL calls. See https://newrelic.com/docs/ruby/sequel-instrumentation\n  for
-  full details.\n\n* Thread profiling fix\n\n  The prior release of the agent (version
-  3.6.1) broke thread profiling. A\n  profile would appear to run, but return no data.
-  This has been fixed.\n\n* Fix for over-counted Net::HTTP calls\n\n  Under some circumstances,
-  calls into Net::HTTP were being counted twice in\n  metrics and transaction traces.
-  This has been fixed.\n\n* Missing traced errors for Resque applications\n\n  Traced
-  errors weren't displaying for some Resque workers, although the errors\n  were factored
-  into the overall count graphs. This has been fixed, and traced\n  errors should
-  be available again after upgrading the agent.\n\nSee https://github.com/newrelic/rpm/blob/master/CHANGELOG
-  for a full list of\nchanges.\n"
+  \ now available in Sinatra as well.\n\n  Routes in 1.4 are properly formatting in
+  transaction names. Thanks Zachary\n  Anker for the contribution!\n\n* Padrino Support\n\n
+  \ Along with improving our support of Sinatra, we've also extended that to\n  supporting
+  Padrino, a framework that builds on Sinatra. Web transactions\n  should show up
+  in New Relic now for Padrino apps automatically. The agent has\n  been tested against
+  the latest Padrino in versions 0.11.x and 0.10.x.\n\n* Main overview graph only
+  shows web transactions\n\n  In the past database times from background jobs mixed
+  with other web transaction\n  metrics in the main overview graph. This often skewed
+  graphs. A common workaround\n  was to send background jobs to a separate application,
+  but that should no longer\n  be necessary as the overview graphs now only represent
+  web transactions.\n\nSee https://github.com/newrelic/rpm/blob/master/CHANGELOG for
+  a full list of\nchanges.\n"
 rdoc_options:
 - --line-numbers
 - --inline-source