newrelic_rpm 4.8.0.341 → 6.13.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (343) hide show
  1. checksums.yaml +5 -5
  2. data/.github/ISSUE_TEMPLATE/bug_report.md +31 -0
  3. data/.github/ISSUE_TEMPLATE/config.yml +5 -0
  4. data/.github/ISSUE_TEMPLATE/feature_request.md +24 -0
  5. data/.github/actions/annotate/README.md +79 -0
  6. data/.github/actions/annotate/action.yml +6 -0
  7. data/.github/actions/annotate/dist/index.js +433 -0
  8. data/.github/actions/annotate/index.js +25 -0
  9. data/.github/actions/annotate/package-lock.json +172 -0
  10. data/.github/actions/annotate/package.json +30 -0
  11. data/.github/actions/annotate/pre-commit +5 -0
  12. data/.github/actions/build-ruby/README.md +79 -0
  13. data/.github/actions/build-ruby/action.yml +15 -0
  14. data/.github/actions/build-ruby/dist/index.js +52683 -0
  15. data/.github/actions/build-ruby/index.js +514 -0
  16. data/.github/actions/build-ruby/package-lock.json +581 -0
  17. data/.github/actions/build-ruby/package.json +32 -0
  18. data/.github/actions/build-ruby/pre-commit +5 -0
  19. data/.github/pull_request_template.md +16 -0
  20. data/.github/workflows/ci.yml +212 -0
  21. data/.github/workflows/pr_review_checklist.yml +22 -0
  22. data/.github/workflows/release.yml +78 -0
  23. data/.github/workflows/scripts/rubygems-authenticate.py +13 -0
  24. data/.github/workflows/scripts/rubygems-publish.rb +32 -0
  25. data/.github/workflows/snyk.yml +27 -0
  26. data/.github/workflows/stale.yml +21 -0
  27. data/.gitignore +9 -0
  28. data/.yardopts +4 -1
  29. data/CHANGELOG.md +868 -3
  30. data/CONTRIBUTING.md +106 -19
  31. data/Gemfile +6 -2
  32. data/Guardfile +18 -1
  33. data/LICENSE +208 -38
  34. data/README.md +81 -88
  35. data/ROADMAP.md +24 -0
  36. data/Rakefile +2 -0
  37. data/THIRD_PARTY_NOTICES.md +213 -0
  38. data/bin/nrdebug +1 -1
  39. data/config.dot +3 -12
  40. data/init.rb +1 -1
  41. data/install.rb +1 -1
  42. data/lib/new_relic/agent.rb +145 -31
  43. data/lib/new_relic/agent/adaptive_sampler.rb +104 -0
  44. data/lib/new_relic/agent/agent.rb +192 -190
  45. data/lib/new_relic/agent/agent_logger.rb +5 -1
  46. data/lib/new_relic/agent/attribute_filter.rb +85 -25
  47. data/lib/new_relic/agent/attribute_processing.rb +1 -1
  48. data/lib/new_relic/agent/attributes.rb +152 -0
  49. data/lib/new_relic/agent/audit_logger.rb +1 -1
  50. data/lib/new_relic/agent/autostart.rb +20 -15
  51. data/lib/new_relic/agent/chained_call.rb +1 -1
  52. data/lib/new_relic/agent/commands/agent_command.rb +1 -1
  53. data/lib/new_relic/agent/commands/agent_command_router.rb +3 -22
  54. data/lib/new_relic/agent/commands/thread_profiler_session.rb +1 -1
  55. data/lib/new_relic/agent/configuration.rb +1 -1
  56. data/lib/new_relic/agent/configuration/default_source.rb +375 -67
  57. data/lib/new_relic/agent/configuration/dotted_hash.rb +1 -1
  58. data/lib/new_relic/agent/configuration/environment_source.rb +5 -3
  59. data/lib/new_relic/agent/configuration/event_harvest_config.rb +45 -0
  60. data/lib/new_relic/agent/configuration/high_security_source.rb +2 -3
  61. data/lib/new_relic/agent/configuration/manager.rb +54 -43
  62. data/lib/new_relic/agent/configuration/manual_source.rb +1 -1
  63. data/lib/new_relic/agent/configuration/mask_defaults.rb +1 -1
  64. data/lib/new_relic/agent/configuration/security_policy_source.rb +238 -0
  65. data/lib/new_relic/agent/configuration/server_source.rb +46 -5
  66. data/lib/new_relic/agent/configuration/yaml_source.rb +12 -7
  67. data/lib/new_relic/agent/connect/request_builder.rb +61 -0
  68. data/lib/new_relic/agent/connect/response_handler.rb +61 -0
  69. data/lib/new_relic/agent/custom_event_aggregator.rb +17 -6
  70. data/lib/new_relic/agent/database.rb +21 -3
  71. data/lib/new_relic/agent/database/explain_plan_helpers.rb +12 -1
  72. data/lib/new_relic/agent/database/obfuscation_helpers.rb +2 -2
  73. data/lib/new_relic/agent/database/obfuscator.rb +1 -1
  74. data/lib/new_relic/agent/database/postgres_explain_obfuscator.rb +1 -1
  75. data/lib/new_relic/agent/datastores.rb +12 -11
  76. data/lib/new_relic/agent/datastores/metric_helper.rb +2 -3
  77. data/lib/new_relic/agent/datastores/mongo.rb +2 -2
  78. data/lib/new_relic/agent/datastores/mongo/event_formatter.rb +3 -3
  79. data/lib/new_relic/agent/datastores/mongo/metric_translator.rb +1 -1
  80. data/lib/new_relic/agent/datastores/mongo/obfuscator.rb +9 -9
  81. data/lib/new_relic/agent/datastores/mongo/statement_formatter.rb +1 -1
  82. data/lib/new_relic/agent/datastores/redis.rb +1 -1
  83. data/lib/new_relic/agent/deprecator.rb +1 -1
  84. data/lib/new_relic/agent/distributed_tracing.rb +216 -0
  85. data/lib/new_relic/agent/distributed_tracing/cross_app_payload.rb +44 -0
  86. data/lib/new_relic/agent/distributed_tracing/cross_app_tracing.rb +248 -0
  87. data/lib/new_relic/agent/distributed_tracing/distributed_trace_attributes.rb +84 -0
  88. data/lib/new_relic/agent/distributed_tracing/distributed_trace_metrics.rb +75 -0
  89. data/lib/new_relic/agent/distributed_tracing/distributed_trace_payload.rb +165 -0
  90. data/lib/new_relic/agent/distributed_tracing/distributed_trace_transport_type.rb +39 -0
  91. data/lib/new_relic/agent/distributed_tracing/trace_context.rb +246 -0
  92. data/lib/new_relic/agent/distributed_tracing/trace_context_payload.rb +126 -0
  93. data/lib/new_relic/agent/encoding_normalizer.rb +1 -1
  94. data/lib/new_relic/agent/error_collector.rb +51 -20
  95. data/lib/new_relic/agent/error_event_aggregator.rb +14 -7
  96. data/lib/new_relic/agent/error_trace_aggregator.rb +2 -1
  97. data/lib/new_relic/agent/event_aggregator.rb +34 -15
  98. data/lib/new_relic/agent/event_buffer.rb +1 -1
  99. data/lib/new_relic/agent/event_listener.rb +1 -1
  100. data/lib/new_relic/agent/event_loop.rb +1 -1
  101. data/lib/new_relic/agent/external.rb +31 -29
  102. data/lib/new_relic/agent/guid_generator.rb +28 -0
  103. data/lib/new_relic/agent/harvester.rb +1 -1
  104. data/lib/new_relic/agent/heap.rb +140 -0
  105. data/lib/new_relic/agent/hostname.rb +16 -2
  106. data/lib/new_relic/agent/http_clients/abstract.rb +82 -0
  107. data/lib/new_relic/agent/http_clients/curb_wrappers.rb +25 -20
  108. data/lib/new_relic/agent/http_clients/excon_wrappers.rb +29 -14
  109. data/lib/new_relic/agent/http_clients/http_rb_wrappers.rb +18 -22
  110. data/lib/new_relic/agent/http_clients/httpclient_wrappers.rb +11 -12
  111. data/lib/new_relic/agent/http_clients/net_http_wrappers.rb +17 -5
  112. data/lib/new_relic/agent/http_clients/typhoeus_wrappers.rb +5 -7
  113. data/lib/new_relic/agent/http_clients/uri_util.rb +12 -11
  114. data/lib/new_relic/agent/instrumentation.rb +1 -1
  115. data/lib/new_relic/agent/instrumentation/action_cable_subscriber.rb +26 -43
  116. data/lib/new_relic/agent/instrumentation/action_controller_subscriber.rb +56 -74
  117. data/lib/new_relic/agent/instrumentation/action_view_subscriber.rb +82 -56
  118. data/lib/new_relic/agent/instrumentation/active_job.rb +19 -17
  119. data/lib/new_relic/agent/instrumentation/active_merchant.rb +1 -1
  120. data/lib/new_relic/agent/instrumentation/active_record.rb +85 -38
  121. data/lib/new_relic/agent/instrumentation/active_record_helper.rb +82 -24
  122. data/lib/new_relic/agent/instrumentation/active_record_notifications.rb +168 -0
  123. data/lib/new_relic/agent/instrumentation/active_record_prepend.rb +102 -31
  124. data/lib/new_relic/agent/instrumentation/active_record_subscriber.rb +47 -57
  125. data/lib/new_relic/agent/instrumentation/active_storage.rb +23 -0
  126. data/lib/new_relic/agent/instrumentation/active_storage_subscriber.rb +63 -0
  127. data/lib/new_relic/agent/instrumentation/acts_as_solr.rb +24 -8
  128. data/lib/new_relic/agent/instrumentation/authlogic.rb +1 -1
  129. data/lib/new_relic/agent/instrumentation/bunny.rb +115 -44
  130. data/lib/new_relic/agent/instrumentation/controller_instrumentation.rb +18 -12
  131. data/lib/new_relic/agent/instrumentation/curb.rb +121 -35
  132. data/lib/new_relic/agent/instrumentation/data_mapper.rb +6 -4
  133. data/lib/new_relic/agent/instrumentation/delayed_job_instrumentation.rb +61 -25
  134. data/lib/new_relic/agent/instrumentation/excon.rb +2 -2
  135. data/lib/new_relic/agent/instrumentation/excon/connection.rb +8 -5
  136. data/lib/new_relic/agent/instrumentation/excon/middleware.rb +4 -3
  137. data/lib/new_relic/agent/instrumentation/grape.rb +46 -35
  138. data/lib/new_relic/agent/instrumentation/http.rb +8 -5
  139. data/lib/new_relic/agent/instrumentation/httpclient.rb +7 -5
  140. data/lib/new_relic/agent/instrumentation/ignore_actions.rb +1 -1
  141. data/lib/new_relic/agent/instrumentation/memcache.rb +5 -3
  142. data/lib/new_relic/agent/instrumentation/memcache/dalli.rb +10 -6
  143. data/lib/new_relic/agent/instrumentation/merb/controller.rb +1 -1
  144. data/lib/new_relic/agent/instrumentation/merb/errors.rb +1 -1
  145. data/lib/new_relic/agent/instrumentation/middleware_proxy.rb +13 -5
  146. data/lib/new_relic/agent/instrumentation/middleware_tracing.rb +20 -11
  147. data/lib/new_relic/agent/instrumentation/mongo.rb +11 -5
  148. data/lib/new_relic/agent/instrumentation/mongodb_command_subscriber.rb +39 -7
  149. data/lib/new_relic/agent/instrumentation/net.rb +60 -23
  150. data/lib/new_relic/agent/instrumentation/notifications_subscriber.rb +100 -0
  151. data/lib/new_relic/agent/instrumentation/padrino.rb +40 -16
  152. data/lib/new_relic/agent/instrumentation/passenger_instrumentation.rb +1 -1
  153. data/lib/new_relic/agent/instrumentation/queue_time.rb +1 -1
  154. data/lib/new_relic/agent/instrumentation/rack.rb +36 -13
  155. data/lib/new_relic/agent/instrumentation/rails/action_controller.rb +1 -1
  156. data/lib/new_relic/agent/instrumentation/rails/action_web_service.rb +1 -1
  157. data/lib/new_relic/agent/instrumentation/rails3/action_controller.rb +1 -1
  158. data/lib/new_relic/agent/instrumentation/rails_middleware.rb +1 -1
  159. data/lib/new_relic/agent/instrumentation/{rails5 → rails_notifications}/action_cable.rb +8 -5
  160. data/lib/new_relic/agent/instrumentation/{rails5 → rails_notifications}/action_controller.rb +4 -4
  161. data/lib/new_relic/agent/instrumentation/{rails4 → rails_notifications}/action_view.rb +4 -4
  162. data/lib/new_relic/agent/instrumentation/rainbows_instrumentation.rb +1 -1
  163. data/lib/new_relic/agent/instrumentation/rake.rb +56 -22
  164. data/lib/new_relic/agent/instrumentation/redis.rb +141 -56
  165. data/lib/new_relic/agent/instrumentation/resque.rb +21 -37
  166. data/lib/new_relic/agent/instrumentation/sequel.rb +2 -3
  167. data/lib/new_relic/agent/instrumentation/sequel_helper.rb +1 -1
  168. data/lib/new_relic/agent/instrumentation/sidekiq.rb +48 -24
  169. data/lib/new_relic/agent/instrumentation/sinatra.rb +62 -23
  170. data/lib/new_relic/agent/instrumentation/sinatra/ignorer.rb +1 -1
  171. data/lib/new_relic/agent/instrumentation/sinatra/transaction_namer.rb +1 -1
  172. data/lib/new_relic/agent/instrumentation/sunspot.rb +1 -1
  173. data/lib/new_relic/agent/instrumentation/typhoeus.rb +27 -10
  174. data/lib/new_relic/agent/internal_agent_error.rb +1 -1
  175. data/lib/new_relic/agent/javascript_instrumentor.rb +19 -16
  176. data/lib/new_relic/agent/log_once.rb +1 -1
  177. data/lib/new_relic/agent/logging.rb +139 -0
  178. data/lib/new_relic/agent/memory_logger.rb +1 -1
  179. data/lib/new_relic/agent/messaging.rb +15 -59
  180. data/lib/new_relic/agent/method_tracer.rb +42 -25
  181. data/lib/new_relic/agent/method_tracer_helpers.rb +5 -5
  182. data/lib/new_relic/agent/monitors.rb +27 -0
  183. data/lib/new_relic/agent/monitors/cross_app_monitor.rb +110 -0
  184. data/lib/new_relic/agent/monitors/distributed_tracing_monitor.rb +27 -0
  185. data/lib/new_relic/agent/{inbound_request_monitor.rb → monitors/inbound_request_monitor.rb} +4 -4
  186. data/lib/new_relic/agent/{synthetics_monitor.rb → monitors/synthetics_monitor.rb} +4 -7
  187. data/lib/new_relic/agent/new_relic_service.rb +174 -63
  188. data/lib/new_relic/agent/new_relic_service/encoders.rb +1 -1
  189. data/lib/new_relic/agent/new_relic_service/json_marshaller.rb +1 -2
  190. data/lib/new_relic/agent/new_relic_service/marshaller.rb +6 -27
  191. data/lib/new_relic/agent/new_relic_service/security_policy_settings.rb +61 -0
  192. data/lib/new_relic/agent/noticible_error.rb +22 -0
  193. data/lib/new_relic/agent/null_logger.rb +1 -1
  194. data/lib/new_relic/agent/obfuscator.rb +1 -1
  195. data/lib/new_relic/agent/parameter_filtering.rb +19 -6
  196. data/lib/new_relic/agent/payload_metric_mapping.rb +1 -1
  197. data/lib/new_relic/agent/pipe_channel_manager.rb +1 -1
  198. data/lib/new_relic/agent/pipe_service.rb +5 -1
  199. data/lib/new_relic/agent/prepend_supportability.rb +1 -1
  200. data/lib/new_relic/agent/priority_sampled_buffer.rb +95 -0
  201. data/lib/new_relic/agent/range_extensions.rb +1 -1
  202. data/lib/new_relic/agent/rules_engine.rb +1 -1
  203. data/lib/new_relic/agent/rules_engine/replacement_rule.rb +1 -1
  204. data/lib/new_relic/agent/rules_engine/segment_terms_rule.rb +1 -1
  205. data/lib/new_relic/agent/sampler.rb +1 -1
  206. data/lib/new_relic/agent/sampler_collection.rb +1 -1
  207. data/lib/new_relic/agent/samplers/cpu_sampler.rb +1 -1
  208. data/lib/new_relic/agent/samplers/delayed_job_sampler.rb +1 -1
  209. data/lib/new_relic/agent/samplers/memory_sampler.rb +1 -1
  210. data/lib/new_relic/agent/samplers/object_sampler.rb +1 -1
  211. data/lib/new_relic/agent/samplers/vm_sampler.rb +1 -1
  212. data/lib/new_relic/agent/span_event_aggregator.rb +49 -0
  213. data/lib/new_relic/agent/span_event_primitive.rb +206 -0
  214. data/lib/new_relic/agent/sql_sampler.rb +23 -7
  215. data/lib/new_relic/agent/stats.rb +1 -1
  216. data/lib/new_relic/agent/stats_engine.rb +4 -4
  217. data/lib/new_relic/agent/stats_engine/gc_profiler.rb +1 -1
  218. data/lib/new_relic/agent/stats_engine/stats_hash.rb +1 -1
  219. data/lib/new_relic/agent/supported_versions.rb +3 -3
  220. data/lib/new_relic/agent/synthetics_event_aggregator.rb +6 -13
  221. data/lib/new_relic/agent/system_info.rb +18 -8
  222. data/lib/new_relic/agent/threading/agent_thread.rb +6 -4
  223. data/lib/new_relic/agent/threading/backtrace_node.rb +1 -1
  224. data/lib/new_relic/agent/threading/backtrace_service.rb +4 -4
  225. data/lib/new_relic/agent/threading/thread_profile.rb +10 -24
  226. data/lib/new_relic/agent/timestamp_sampled_buffer.rb +19 -0
  227. data/lib/new_relic/agent/tracer.rb +509 -0
  228. data/lib/new_relic/agent/transaction.rb +191 -278
  229. data/lib/new_relic/agent/transaction/abstract_segment.rb +38 -5
  230. data/lib/new_relic/agent/transaction/datastore_segment.rb +30 -5
  231. data/lib/new_relic/agent/transaction/distributed_tracer.rb +171 -0
  232. data/lib/new_relic/agent/transaction/distributed_tracing.rb +123 -71
  233. data/lib/new_relic/agent/transaction/external_request_segment.rb +41 -89
  234. data/lib/new_relic/agent/transaction/message_broker_segment.rb +7 -8
  235. data/lib/new_relic/agent/transaction/request_attributes.rb +1 -1
  236. data/lib/new_relic/agent/transaction/segment.rb +42 -2
  237. data/lib/new_relic/agent/transaction/slowest_sample_buffer.rb +1 -1
  238. data/lib/new_relic/agent/transaction/synthetics_sample_buffer.rb +1 -1
  239. data/lib/new_relic/agent/transaction/trace.rb +7 -23
  240. data/lib/new_relic/agent/transaction/trace_builder.rb +1 -2
  241. data/lib/new_relic/agent/transaction/trace_context.rb +168 -0
  242. data/lib/new_relic/agent/transaction/trace_node.rb +12 -8
  243. data/lib/new_relic/agent/transaction/tracing.rb +2 -100
  244. data/lib/new_relic/agent/transaction/transaction_sample_buffer.rb +1 -1
  245. data/lib/new_relic/agent/transaction_error_primitive.rb +13 -22
  246. data/lib/new_relic/agent/transaction_event_aggregator.rb +7 -16
  247. data/lib/new_relic/agent/transaction_event_primitive.rb +31 -42
  248. data/lib/new_relic/agent/transaction_event_recorder.rb +8 -16
  249. data/lib/new_relic/agent/transaction_metrics.rb +1 -1
  250. data/lib/new_relic/agent/transaction_sampler.rb +3 -14
  251. data/lib/new_relic/agent/transaction_time_aggregator.rb +155 -0
  252. data/lib/new_relic/agent/utilization/aws.rb +1 -1
  253. data/lib/new_relic/agent/utilization/azure.rb +1 -1
  254. data/lib/new_relic/agent/utilization/gcp.rb +1 -1
  255. data/lib/new_relic/agent/utilization/pcf.rb +1 -1
  256. data/lib/new_relic/agent/utilization/vendor.rb +1 -1
  257. data/lib/new_relic/agent/utilization_data.rb +37 -2
  258. data/lib/new_relic/agent/vm.rb +1 -1
  259. data/lib/new_relic/agent/vm/jruby_vm.rb +1 -1
  260. data/lib/new_relic/agent/vm/monotonic_gc_profiler.rb +1 -1
  261. data/lib/new_relic/agent/vm/mri_vm.rb +1 -1
  262. data/lib/new_relic/agent/vm/snapshot.rb +1 -1
  263. data/lib/new_relic/agent/worker_loop.rb +1 -1
  264. data/lib/new_relic/cli/command.rb +1 -1
  265. data/lib/new_relic/cli/commands/deployments.rb +2 -2
  266. data/lib/new_relic/cli/commands/install.rb +4 -3
  267. data/lib/new_relic/coerce.rb +32 -7
  268. data/lib/new_relic/collection_helper.rb +1 -1
  269. data/lib/new_relic/constants.rb +38 -0
  270. data/lib/new_relic/control.rb +1 -1
  271. data/lib/new_relic/control/class_methods.rb +8 -2
  272. data/lib/new_relic/control/frameworks.rb +1 -1
  273. data/lib/new_relic/control/frameworks/external.rb +1 -1
  274. data/lib/new_relic/control/frameworks/merb.rb +1 -1
  275. data/lib/new_relic/control/frameworks/rails.rb +1 -1
  276. data/lib/new_relic/control/frameworks/rails3.rb +1 -1
  277. data/lib/new_relic/control/frameworks/rails4.rb +1 -1
  278. data/lib/new_relic/control/frameworks/{rails5.rb → rails_notifications.rb} +2 -2
  279. data/lib/new_relic/control/frameworks/ruby.rb +1 -1
  280. data/lib/new_relic/control/frameworks/sinatra.rb +1 -1
  281. data/lib/new_relic/control/instance_methods.rb +30 -4
  282. data/lib/new_relic/control/instrumentation.rb +1 -1
  283. data/lib/new_relic/control/server_methods.rb +1 -1
  284. data/lib/new_relic/delayed_job_injection.rb +1 -1
  285. data/lib/new_relic/dependency_detection.rb +5 -5
  286. data/lib/new_relic/environment_report.rb +6 -2
  287. data/lib/new_relic/helper.rb +1 -1
  288. data/lib/new_relic/language_support.rb +1 -1
  289. data/lib/new_relic/latest_changes.rb +4 -4
  290. data/lib/new_relic/local_environment.rb +1 -1
  291. data/lib/new_relic/metric_data.rb +1 -1
  292. data/lib/new_relic/metric_spec.rb +1 -1
  293. data/lib/new_relic/noticed_error.rb +39 -18
  294. data/lib/new_relic/rack.rb +1 -1
  295. data/lib/new_relic/rack/agent_hooks.rb +1 -1
  296. data/lib/new_relic/rack/agent_middleware.rb +2 -2
  297. data/lib/new_relic/rack/browser_monitoring.rb +16 -9
  298. data/lib/new_relic/recipes.rb +1 -1
  299. data/lib/new_relic/recipes/capistrano3.rb +6 -3
  300. data/lib/new_relic/recipes/capistrano_legacy.rb +1 -1
  301. data/lib/new_relic/supportability_helper.rb +15 -1
  302. data/lib/new_relic/version.rb +4 -4
  303. data/lib/newrelic_rpm.rb +1 -1
  304. data/lib/sequel/extensions/newrelic_instrumentation.rb +3 -3
  305. data/lib/sequel/plugins/newrelic_instrumentation.rb +2 -2
  306. data/lib/tasks/all.rb +1 -1
  307. data/lib/tasks/config.rake +1 -2
  308. data/lib/tasks/multiverse.rb +35 -1
  309. data/lib/tasks/newrelic.rb +1 -1
  310. data/lib/tasks/tests.rake +6 -1
  311. data/newrelic_rpm.gemspec +23 -17
  312. data/recipes/newrelic.rb +1 -1
  313. data/test/agent_helper.rb +357 -78
  314. metadata +154 -60
  315. data/.travis.yml +0 -173
  316. data/lib/new_relic/agent/busy_calculator.rb +0 -117
  317. data/lib/new_relic/agent/commands/xray_session.rb +0 -55
  318. data/lib/new_relic/agent/commands/xray_session_collection.rb +0 -161
  319. data/lib/new_relic/agent/cross_app_monitor.rb +0 -140
  320. data/lib/new_relic/agent/cross_app_tracing.rb +0 -143
  321. data/lib/new_relic/agent/distributed_trace_monitor.rb +0 -29
  322. data/lib/new_relic/agent/distributed_trace_payload.rb +0 -223
  323. data/lib/new_relic/agent/distributed_trace_priority_sampled_buffer.rb +0 -72
  324. data/lib/new_relic/agent/http_clients/abstract_request.rb +0 -31
  325. data/lib/new_relic/agent/instrumentation/active_record_4.rb +0 -42
  326. data/lib/new_relic/agent/instrumentation/active_record_5.rb +0 -36
  327. data/lib/new_relic/agent/instrumentation/evented_subscriber.rb +0 -104
  328. data/lib/new_relic/agent/instrumentation/rails4/action_controller.rb +0 -32
  329. data/lib/new_relic/agent/instrumentation/rails5/action_view.rb +0 -27
  330. data/lib/new_relic/agent/sampled_buffer.rb +0 -68
  331. data/lib/new_relic/agent/sized_buffer.rb +0 -23
  332. data/lib/new_relic/agent/synthetics_event_buffer.rb +0 -40
  333. data/lib/new_relic/agent/throughput_monitor.rb +0 -59
  334. data/lib/new_relic/agent/transaction/attributes.rb +0 -153
  335. data/lib/new_relic/agent/transaction/xray_sample_buffer.rb +0 -64
  336. data/lib/new_relic/agent/transaction_state.rb +0 -145
  337. data/lib/new_relic/agent/transaction_timings.rb +0 -57
  338. data/lib/new_relic/metrics.rb +0 -13
  339. data/lib/tasks/versions.html.erb +0 -28
  340. data/lib/tasks/versions.postface.html +0 -8
  341. data/lib/tasks/versions.preface.html +0 -9
  342. data/lib/tasks/versions.rake +0 -65
  343. data/lib/tasks/versions.txt.erb +0 -14
@@ -0,0 +1,21 @@
1
+ name: "Close stale issues"
2
+ on:
3
+ schedule:
4
+ - cron: "0 0 * * *"
5
+
6
+ jobs:
7
+ stale:
8
+ runs-on: ubuntu-latest
9
+ steps:
10
+ - uses: actions/stale@v3
11
+ with:
12
+ repo-token: ${{ secrets.GITHUB_TOKEN }}
13
+ stale-issue-message: 'This has been marked stale after 30 days with no activity. It will be closed in 5 days if there is no activity.'
14
+ stale-pr-message: 'Stale pull request message'
15
+ days-before-stale: 30
16
+ days-before-close: 5
17
+ stale-issue-label: 'stale'
18
+ exempt-issue-labels: 'good first issue,help wanted,in progress,on hold,in review,roadmap'
19
+ stale-pr-label: 'stale'
20
+ exempt-pr-labels: 'on hold,in review'
21
+
data/.gitignore CHANGED
@@ -1,4 +1,5 @@
1
1
  Gemfile.lock
2
+ Guard*
2
3
  .DS\_Store
3
4
  .svn/
4
5
  *~
@@ -14,6 +15,7 @@ tags
14
15
  *.swp
15
16
  *.swo
16
17
 
18
+ /doc/
17
19
  /log/
18
20
  /lerg/
19
21
  gems/newrelic_rpm.gemspec
@@ -24,4 +26,11 @@ lib/new_relic/build.rb
24
26
  .bundle
25
27
  .yardoc
26
28
  artifacts/
29
+ test/performance/log/
27
30
  test/performance/script/log/
31
+ infinite_tracing/log/
32
+ infinite_tracing/test/new_relic/infinite_tracing/log
33
+ test/fixtures/cross_agent_tests/*/README.md
34
+ node_modules/
35
+ yarn.lock
36
+ errors.txt
data/.yardopts CHANGED
@@ -2,6 +2,8 @@
2
2
  --api public
3
3
  lib/new_relic/agent.rb
4
4
  lib/new_relic/agent/method_tracer.rb
5
+ lib/new_relic/agent/distributed_tracing.rb
6
+ lib/new_relic/agent/distributed_trace_payload.rb
5
7
  lib/new_relic/agent/external.rb
6
8
  lib/new_relic/agent/instrumentation/controller_instrumentation.rb
7
9
  lib/new_relic/agent/instrumentation/rack.rb
@@ -10,6 +12,7 @@ lib/new_relic/agent/stats_engine/metric_stats.rb
10
12
  lib/new_relic/agent/datastores.rb
11
13
  lib/new_relic/agent/messaging.rb
12
14
  lib/new_relic/agent/sql_sampler.rb
15
+ lib/new_relic/agent/tracer.rb
13
16
  lib/new_relic/agent/transaction.rb
14
17
  lib/new_relic/agent/transaction_sampler.rb
15
18
  lib/new_relic/rack/agent_hooks.rb
@@ -19,5 +22,5 @@ lib/new_relic/rack.rb
19
22
  lib/new_relic/agent/transaction/external_request_segment.rb
20
23
  -
21
24
  LICENSE
22
- CHANGELOG
25
+ CHANGELOG.md
23
26
  CONTRIBUTING.md
@@ -1,6 +1,871 @@
1
1
  # New Relic Ruby Agent Release Notes #
2
2
 
3
- ## v4.8.0 ##
3
+ ## v6.13.1
4
+
5
+ * **Bugfix: obfuscating URLs to external services no longer modifying original URI**
6
+
7
+ A recent change to the Ruby agent to obfuscate URIs sent to external services had the unintended side-effect of removing query parameters
8
+ from the original URI. This is fixed to obfuscate while also preserving the original URI.
9
+
10
+ Thanks to @VictorJimenezKwast for pinpointing and helpful unit test to demonstrate.
11
+
12
+ ## v6.13.0
13
+
14
+ * **Bugfix: never use redirect host when accessing preconnect endpoint**
15
+
16
+ When connecting to New Relic, the Ruby Agent uses the value in `Agent.config[:host]` to post a request to the New Relic preconnect endpoint. This endpoint returns a "redirect host" which is the URL to which agents send data from that point on.
17
+
18
+ Previously, if the agent needed to reconnect to the collector, it would incorrectly use this redirect host to call the preconnect
19
+ endpoint, when it should have used the original configured value in `Agent.config[:host]`. The agent now uses the correct host
20
+ for all calls to preconnect.
21
+
22
+ * **Bugfix: calling `add_custom_attributes` no longer modifies the params of the caller**
23
+
24
+ The previous agent's improvements to recording attributes at the span level had an unexpected
25
+ side-effect of modifying the params passed to the API call as duplicated attributes were deleted
26
+ in the process. This is now fixed and params passed in are no longer modified.
27
+
28
+ Thanks to Pete Johns (@johnsyweb) for the PR that resolves this bug.
29
+
30
+ * **Bugfix: `http.url` query parameters spans are now obfuscated**
31
+
32
+ Previously, the agent was recording the full URL of the external requests, including
33
+ the query and fragment parts of the URL as part of the attributes on the external request
34
+ span. This has been fixed so that the URL is obfuscated to filter out potentially sensitive data.
35
+
36
+ * **Use system SSL certificates by default**
37
+
38
+ The Ruby agent previously used a root SSL/TLS certificate bundle by default. Now the agent will attempt to use
39
+ the default system certificates, but will fall back to the bundled certs if there is an issue (and log that this occurred).
40
+
41
+ * **Bugfix: reduce allocations for segment attributes**
42
+
43
+ Previously, every segment received an `Attributes` object on initialization. The agent now lazily creates attributes
44
+ on segments, resulting in a significant reduction in object allocations for a typical transaction.
45
+
46
+ * **Bugfix: eliminate errors around Rake::VERSION with Rails**
47
+
48
+ When running a Rails application with rake tasks, customers could see the following error:
49
+
50
+ * **Prevent connecting agent thread from hanging on shutdown**
51
+
52
+ A bug in `Net::HTTP`'s Gzip decoder can cause the (un-catchable)
53
+ thread-kill exception to be replaced with a (catchable) `Zlib` exception,
54
+ which prevents a connecting agent thread from exiting during shutdown,
55
+ causing the Ruby process to hang indefinitely.
56
+ This workaround checks for an `aborting` thread in the `#connect` exception handler
57
+ and re-raises the exception, allowing a killed thread to continue exiting.
58
+
59
+ Thanks to Will Jordan (@wjordan) for chasing this one down and patching with tests.
60
+
61
+ * **Fix error messages about Rake instrumentation**
62
+
63
+ When running a Rails application with rake tasks, customers could see the following error in logs resulting from
64
+ a small part of rake functionality being loaded with the Rails test runner:
65
+
66
+ ```
67
+ ERROR : Error while detecting rake_instrumentation:
68
+ ERROR : NameError: uninitialized constant Rake::VERSION
69
+ ```
70
+
71
+ Such error messages should no longer appear in this context.
72
+
73
+ Thanks to @CamilleDrapier for pointing out this issue.
74
+
75
+ * **Remove NewRelic::Metrics**
76
+
77
+ The `NewRelic::Metrics` module has been removed from the agent since it is no longer used.
78
+
79
+ Thanks to @csaura for the contribution!
80
+
81
+ ## v6.12.0
82
+
83
+ * The New Relic Ruby Agent is now open source under the [Apache 2 license](LICENSE)
84
+ and you can now observe the project roadmap. See our [Contributing guide](https://github.com/newrelic/newrelic-ruby-agent/blob/main/CONTRIBUTING.md)
85
+ and [Code of Conduct](https://github.com/newrelic/.github/blob/master/CODE_OF_CONDUCT.md) for details on contributing!
86
+
87
+ * **Security: Updated all uses of Rake to >= 12.3.3**
88
+
89
+ All versions of Rake testing prior to 12.3.3 were removed to address
90
+ [CVE-2020-8130](https://nvd.nist.gov/vuln/detail/CVE-2020-8130).
91
+ No functionality in the agent was removed nor deprecated with this change, and older versions
92
+ of rake are expected to continue to work as they have in the past. However, versions of
93
+ rake < 12.3.3 are no longer tested nor supported.
94
+
95
+ * **Bugfix: fixes an error capturing content length in middleware on multi-part responses**
96
+
97
+ In the middleware tracing, the `Content-Length` header is sometimes returned as an array of
98
+ values when content is a multi-part response. Previously, the agent would fail with
99
+ "NoMethodError: undefined method `to_i` for Array" Error. This bug is now fixed and
100
+ multi-part content lengths are summed for a total when an `Array` is present.
101
+
102
+ * **Added support for auto-instrumenting Mongo gem versions 2.6 to 2.12**
103
+
104
+ * **Bugfix: MongoDB instrumentation did not handle CommandFailed events when noticing errors**
105
+
106
+ The mongo gem sometimes returns a CommandFailed object instead of a CommandSucceeded object with
107
+ error attributes populated. The instrumentation did not handle noticing errors on CommandFailed
108
+ objects and resulted in logging an error and backtrace to the log file.
109
+
110
+ Additionally, a bug in recording the metric for "findAndModify" as all lowercased "findandmodify"
111
+ for versions 2.1 through 2.5 was fixed.
112
+
113
+ * **Bugfix: Priority Sampler causes crash in high throughput environents in rare cases**
114
+
115
+ Previously, the priority sampling buffer would, in rare cases, generate an error in high-throughput
116
+ environments once capacity is reached and the sampling algorthym engages. This issue is fixed.
117
+
118
+ * **Additional Transaction Information applied to Span Events**
119
+
120
+ When Distributed Tracing and/or Infinite Tracing are enabled, the Agent will now incorporate additional information from the Transaction Event on to the root Span Event of the transaction.
121
+
122
+ The following items are affected:
123
+ * Custom attribute values applied to the Transaction via our [add_custom_attributes](http://www.rubydoc.info/github/newrelic/newrelic-ruby-agent/NewRelic/Agent#add_custom_attributes-instance_method) API method.
124
+ * Request parameters: `request.parameters.*`
125
+ * Request headers: `request.headers.*`
126
+ * Response headers: `response.headers.*`
127
+ * Resque job arguments: `job.resque.args.*`
128
+ * Sidekiq job arguments: `job.sidekiq.args.*`
129
+ * Messaging arguments: `message.*`
130
+ * `httpResponseCode` (deprecated in this version; see note below)/`http.statusCode`
131
+ * `response.status`
132
+ * `request.uri`
133
+ * `request.method`
134
+ * `host.displayName`
135
+
136
+ * **Security Recommendation**
137
+
138
+ Review your Transaction attributes [include](https://docs.newrelic.com/docs/agents/ruby-agent/attributes/enable-disable-attributes-ruby#transaction_events-attributes-include) and [exclude](https://docs.newrelic.com/docs/agents/ruby-agent/attributes/enable-disable-attributes-ruby#transaction_events-attributes-exclude) configurations. Any attribute include or exclude settings specific to Transaction Events should be applied
139
+ to your Span attributes [include](https://docs.newrelic.com/docs/agents/ruby-agent/attributes/enable-disable-attributes-ruby#span-events-attributes-include) and [exclude](https://docs.newrelic.com/docs/agents/ruby-agent/attributes/enable-disable-attributes-ruby#span-events-attributes-exclude) configuration or your global attributes [include](https://docs.newrelic.com/docs/agents/ruby-agent/attributes/enable-disable-attributes-ruby#attributes-include) and [exclude](https://docs.newrelic.com/docs/agents/ruby-agent/attributes/enable-disable-attributes-ruby#attributes-exclude) configuration.
140
+
141
+ * **Agent attribute deprecation: httpResponseCode**
142
+
143
+ Starting in this agent version, the [agent attribute](https://docs.newrelic.com/docs/agents/ruby-agent/attributes/ruby-agent-attributes#attributes) `httpResponseCode` (string value) has been deprecated. Customers can begin using `http.statusCode`
144
+ (integer value) immediately, and `httpResponseCode` will be removed in the agent's next major version update.
145
+
146
+ * **Bugfix: Eliminate warnings for distributed tracing when using sidekiq**
147
+
148
+ Previously, using sidekiq with distributed tracing disabled resulted in warning messages\
149
+ `WARN : Not configured to accept distributed trace headers`\
150
+ ` WARN : Not configured to insert distributed trace headers`\
151
+ These messages no longer appear.
152
+
153
+ ## v6.11.0
154
+
155
+ * **Infinite Tracing**
156
+
157
+ This release adds support for [Infinite Tracing](https://docs.newrelic.com/docs/understand-dependencies/distributed-tracing/enable-configure/enable-distributed-tracing). Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data. With Infinite Tracing, you get examples of errors and long-running traces so you can better diagnose and troubleshoot your systems.
158
+
159
+ Configure your agent to send traces to a trace observer in New Relic Edge. View distributed traces through New Relic’s UI. There is no need to install a collector on your network.
160
+
161
+ Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative.
162
+
163
+ * **Bugfix: Cross Application Tracing (CAT) adds a missing field to response**
164
+
165
+ Previously, the Ruby agent's Cross Application Tracing header was missing a reserved field that would lead to an error
166
+ in the Go agent's processing of incoming headers from the Ruby agent. This fix adds that missing field to the headers, eliminating
167
+ the issue with traces involving the Ruby agent and the Go agent.
168
+
169
+ * **Bugfix: Environment Report now supports Rails >= 6.1**
170
+
171
+ Previously, users of Rails 6.1 would see the following deprecation warning appear when the Ruby agent attempted to
172
+ collect enviroment data: `DEPRECATION WARNING: [] is deprecated and will be removed from Rails 6.2`. These deprecation methods
173
+ no longer appear.
174
+
175
+ Thanks to Sébastien Dubois (sedubois) for reporting this issue and for the contribution!
176
+
177
+ * **Added distributed tracing to Sidekiq jobs**
178
+
179
+ Previously, Sidekiq jobs were not included in portions of <a href="https://docs.newrelic.com/docs/understand-dependencies/distributed-tracing/get-started/introduction-distributed-tracing">distributed traces</a> captured by the Ruby agent. Now you can view distributed
180
+ traces that include Sidekiq jobs instrumented by the Ruby agent.
181
+
182
+ Thanks to andreaseger for the contribution!
183
+
184
+ * **Bugfix: Eliminate warnings appearing when using `add_method_tracer` with Ruby 2.7**
185
+
186
+ Previously, using `add_method_tracer` with Ruby 2.7 to trace a method that included keyword arguments resulted in warning messages:
187
+ `warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call`. These messages no
188
+ longer appear.
189
+
190
+ Thanks to Harm de Wit and Atsuo Fukaya for reporting the issue!
191
+
192
+ ## v6.10.0
193
+
194
+ * **Error attributes now added to each span that exits with an error or exception**
195
+
196
+ Error attributes `error.class` and `error.message` are now included on the span event in which an error
197
+ or exception was noticed, and, in the case of unhandled exceptions, on any ancestor spans that also exit with an error.
198
+ The public API method `notice_error` now attaches these error attributes to the currently executing span.
199
+
200
+ <a href="https://docs.newrelic.com/docs/apm/distributed-tracing/ui-data/understand-use-distributed-tracing-data#rules-limits">Spans with error details are now highlighted red in the Distributed Tracing UI</a>, and error details will expose the associated
201
+ `error.class` and `error.message`. It is also now possible to see when an exception leaves the boundary of the span,
202
+ and if it is caught in an ancestor span without reaching the entry span. NOTE: This “bubbling up” of exceptions will impact
203
+ the error count when compared to prior behavior for the same trace. It is possible to have a trace that now has span errors
204
+ without the trace level showing an error.
205
+
206
+ If multiple errors occur on the same span, only the most recent error information is added to the attributes. Prior errors on the same span are overwritten.
207
+
208
+ These span event attributes conform to <a href="https://docs.newrelic.com/docs/agents/manage-apm-agents/agent-data/manage-errors-apm-collect-ignore-or-mark-expected#ignore">ignored errors</a> and <a href="https://docs.newrelic.com/docs/agents/manage-apm-agents/agent-data/manage-errors-apm-collect-ignore-or-mark-expected#expected">expected errors</a>.
209
+
210
+ * **Added tests for latest Grape / Rack combination**
211
+
212
+ For a short period of time, the latest versions of Grape and Rack had compatibility issues.
213
+ Generally, Rack 2.1.0 should be avoided in all cases due to breaking changes in many gems
214
+ reliant on Rack. We recommend using either Rack <= 2.0.9, or using latest Rack when using Grape
215
+ (2.2.2 at the time of this writing).
216
+
217
+ * **Bugfix: Calculate Content-Length in bytes**
218
+
219
+ Previously, the Content-Length HTTP header would be incorrect after injecting the Browser Monitoring
220
+ JS when the response contained Unicode characters because the value was not calculated in bytes.
221
+ The Content-Length is now correctly updated.
222
+
223
+ Thanks to thaim for the contribution!
224
+
225
+ * **Bugfix: Fix Content-Length calculation when response is nil**
226
+
227
+ Previously, calculating the Content-Length HTTP header would result in a `NoMethodError` in the case of
228
+ a nil response. These errors will no longer occur in such a case.
229
+
230
+ Thanks to Johan Van Ryseghem for the contribution!
231
+
232
+ * **Bugfix: DecoratingFormatter now logs timestamps as millisecond Integers**
233
+
234
+ Previously the agent sent timestamps as a Float with milliseconds as part of the
235
+ fractional value. Logs in Context was changed to only accept Integer values and this
236
+ release changes DecoratingFormatter to match.
237
+
238
+ * **Added --force option to `newrelic install` cli command to allow overwriting newrelic.yml**
239
+
240
+ * **Bugfix: The fully qualified hostname now works correctly for BSD and Solaris**
241
+
242
+ Previously, when running on systems such as BSD and Solaris, the agent was unable to determine the fully
243
+ qualified domain name, which is used to help link Ruby agent data with data from New Relic Infrastructure.
244
+ This information is now successfully collected on various BSD distros and Solaris.
245
+
246
+
247
+ ## v6.9.0
248
+
249
+ * **Added support for W3C Trace Context, with easy upgrade from New Relic trace context**
250
+
251
+ * [Distributed Tracing now supports W3C Trace Context headers](https://docs.newrelic.com/docs/understand-dependencies/distributed-tracing/get-started/introduction-distributed-tracing#w3c-support) for HTTP protocols when distributed tracing is enabled. Our implementation can accept and emit both
252
+ the W3C trace header format and the New Relic trace header format. This simplifies
253
+ agent upgrades, allowing trace context to be propagated between services with older
254
+ and newer releases of New Relic agents. W3C trace header format will always be
255
+ accepted and emitted. New Relic trace header format will be accepted, and you can
256
+ optionally disable emission of the New Relic trace header format.
257
+
258
+ * When distributed tracing is enabled by setting `distributed_tracing.enabled` to `true`,
259
+ the Ruby agent will now accept W3C's `traceparent` and `tracestate` headers when
260
+ calling `DistributedTracing.accept_distributed_trace_headers` or automatically via
261
+ `http` instrumentation. When calling `DistributedTracing.insert_distributed_trace_headers`,
262
+ or automatically via `http` instrumentation, the Ruby agent will include the W3C
263
+ headers along with the New Relic distributed tracing header, unless the New Relic
264
+ trace header format is disabled by setting `exclude_newrelic_header` setting to `true`.
265
+
266
+ * Added `DistributedTracing.accept_distributed_trace_headers` API for accepting both
267
+ New Relic and W3C TraceContext distributed traces.
268
+
269
+ * Deprecated `DistributedTracing.accept_distributed_trace_payload` which will be removed
270
+ in a future major release.
271
+
272
+ * Added `DistributedTracing.insert_distributed_trace_headers` API for adding outbound
273
+ distributed trace headers. Both W3C TraceContext and New Relic formats will be
274
+ included unless `distributed_tracing.exclude_newrelic_header: true`.
275
+
276
+ * Deprecated `DistributedTracing.create_distributed_trace_payload` which will be removed
277
+ in a future major release.
278
+
279
+ Known Issues and Workarounds
280
+
281
+ * If a .NET agent is initiating traces as the root service, do not upgrade your
282
+ downstream Ruby New Relic agents to this agent release.
283
+
284
+ * **Official Ruby 2.7 support**
285
+
286
+ The Ruby agent has been verified to run with Ruby 2.7.0.
287
+
288
+ * **Reduced allocations when tracing transactions using API calls**
289
+
290
+ Default empty hashes for `options` parameter were not frozen, leading to
291
+ excessive and unnecessary allocations when calling APIs for tracing transactions.
292
+
293
+ Thanks to Joel Turkel (jturkel) for the contribution!
294
+
295
+ * **Bugfix for Resque worker thread race conditions**
296
+
297
+ Recent changes in Rack surfaced issues marshalling data for resque, surfaced a potential race-condition with closing out the worker-threads before flushing the data pipe. This
298
+ is now fixed.
299
+
300
+ Thanks to Bertrand Paquet (bpaquet) for the contribution!
301
+
302
+ * **Bugfix for Content-Length when injecting Browser Monitoring JS**
303
+
304
+ The Content-Length HTTP header would be incorrect after injecting the Browser Monitoring
305
+ JS into the HEAD tag of the HTML source with Content-Length and lead to the HTML BODY content
306
+ being truncated in some cases. The Content-Length is now correctly updated after injecting the
307
+ Browser Monitoring JS script.
308
+
309
+ Thanks to Slava Kardakov (ojab) for the contribution!
310
+
311
+ ## v6.8.0
312
+
313
+ * **Initial Ruby 2.7 support**
314
+
315
+ The Ruby agent has been verified to run with Ruby 2.7.0-preview1.
316
+
317
+ * **New API method to add custom attributes to Spans**
318
+
319
+ New API method for adding custom attributes to spans. Previously, custom
320
+ attributes were only available at the Transaction level. Now, with Span
321
+ level custom attributes, more granular tagging of events is possible for
322
+ easier isolation and review of trace events. For more information:
323
+
324
+ * [`Agent#add_custom_span_attributes`](https://www.rubydoc.info/github/newrelic/newrelic-ruby-agent/NewRelic/Agent#add_custom_span_attributes)
325
+
326
+ * **Enables ability to migrate to Configurable Security Policies (CSP) on a per agent
327
+ basis for accounts already using High Security Mode (HSM).**
328
+
329
+ When both [HSM](https://docs.newrelic.com/docs/agents/manage-apm-agents/configuration/high-security-mode) and [CSP](https://docs.newrelic.com/docs/agents/manage-apm-agents/configuration/enable-configurable-security-policies) are enabled for an account, an agent (this version or later)
330
+ can successfully connect with either `high_security: true` or the appropriate
331
+ `security_policies_token` configured. `high_security` has been added as part of
332
+ the preconnect payload.
333
+
334
+ * **Bugfix for Logs in Context combined with act-fluent-logger-rails**
335
+
336
+ Previously, when using the Ruby agent's Logs in Context logger
337
+ to link logging data with trace and entity metadata for an
338
+ improved experience in the UI, customers who were also using
339
+ the `act-fluent-logger-rails` gem would see a `NoMethodError`
340
+ for `clear_tags!` that would interfere with the use of this
341
+ feature. This error no longer appears, allowing customers to
342
+ combine the use of Logs in Context with the use of this gem.
343
+
344
+ Please note that the Logs in Context logger does not support
345
+ tagged logging; if you are initializing your logger with a
346
+ `log_tags` argument, your custom tags may not appear on the
347
+ final version of your logs.
348
+
349
+ * **Bugfix for parsing invalid newrelic.yml**
350
+
351
+ Previously, if the newrelic.yml configuration file was invalid, and the agent
352
+ could not start as a result, the agent would not log any indication of
353
+ the problem.
354
+
355
+ This version of the agent will emit a FATAL message to STDOUT when this scenario
356
+ occurs so that customers can address issues with newrelic.yml that prevent startup.
357
+
358
+ * **Configuration options containing the terms "whitelist" and "blacklist" deprecated**
359
+
360
+ The following local configuration settings have been deprecated:
361
+
362
+ * `autostart.blacklisted_constants`: use `autostart.denylisted_constants` instead.
363
+ * `autostart.blacklisted_executables`: use `autostart.denylisted_executables` instead.
364
+ * `autostart.blacklisted_rake_tasks`: use `autostart.denylisted_rake_tasks` instead.
365
+ * `strip_exception_messages.whitelist`: use `strip_exception_messages.allowed_classes` instead.
366
+
367
+ * **Bugfix for module loading and constant resolution in Rails**
368
+
369
+ Starting in version 6.3, the Ruby agent has caused module loading and constant
370
+ resolution to sometimes fail, which caused errors in some Rails applications.
371
+ These errors were generally `NoMethodError` exceptions or I18n errors
372
+ `translation missing` or `invalid locale`. These errors would not appear if the agent
373
+ was removed from the application's Gemfile.
374
+ This version of the agent fixes these issues with module loading and constant
375
+ resolution, so these errors no longer occur.
376
+
377
+ * **Bugfix: failed to get urandom**
378
+
379
+ Previous versions of the agent would fail unexpectedly when the Ruby process used
380
+ every available file descriptor. The failures would include this message:
381
+ ```
382
+ ERROR : RuntimeError: failed to get urandom
383
+ ```
384
+ This version of the agent uses a different strategy for generating random IDs, and
385
+ will not fail in the same way when no file descriptors are available.
386
+
387
+ ## v6.7.0
388
+
389
+ * **Trace and Entity Metadata API**
390
+
391
+ Several new API methods have been added to the agent:
392
+ * [`Agent#linking_metadata`](https://www.rubydoc.info/github/newrelic/newrelic-ruby-agent/NewRelic/Agent#linking_metadata-instance_method)
393
+ * [`Tracer#trace_id`](https://www.rubydoc.info/github/newrelic/newrelic-ruby-agent/NewRelic/Agent/Tracer#trace_id-class_method)
394
+ * [`Tracer#span_id`](https://www.rubydoc.info/github/newrelic/newrelic-ruby-agent/NewRelic/Agent/Tracer#span_id-class_method)
395
+ * [`Tracer#sampled?`](https://www.rubydoc.info/github/newrelic/newrelic-ruby-agent/NewRelic/Agent/Tracer#sampled?-class_method)
396
+
397
+ These API methods allow you to access information that can be used to link data of your choosing to a trace or entity.
398
+
399
+ * **Logs in Context**
400
+
401
+ This version of the agent includes a logger, which can be used in place of `::Logger`
402
+ from the standard library, or `ActiveSupport::Logger` from Rails. This logger
403
+ leverages the new trace and entity metadata API to decorate log statements with entity
404
+ and trace metadata, so they can be correlated together in the New Relic UI.
405
+
406
+ For more information on how to use logs in context, see https://docs.newrelic.com/docs/enable-logs-context-ruby
407
+
408
+ * **Project metadata in Gemspec**
409
+
410
+ Project metadata has been added to the gemspec file. This means our Rubygems page will allow users to more easily
411
+ access the agent's source code, raise issues, and read the changelog.
412
+
413
+ Thanks to Orien Madgwick for the contribution!
414
+
415
+ ## v6.6.0
416
+
417
+ * **Bugfix for ActionCable Instrumentation**
418
+
419
+ Previous versions of the agent sometimes caused application crashes with some versions
420
+ of ActionCable. The application would exit quickly after startup with the error:
421
+ `uninitialized constant ActionCable::Engine`.
422
+
423
+ Version 6.6.0 of the agent no longer crashes in this way.
424
+
425
+
426
+ * **Handling of disabling Error Collection**
427
+
428
+ When the agent first starts, it begins collecting Error Events and Traces before
429
+ fetching configuration from New Relic. In previous versions of the agent, those
430
+ events or traces would be sent to New Relic, even if _Error Collection_ is disabled in
431
+ the application's server-side configuration.
432
+
433
+ Version 6.6.0 of the agent drops all collected Error Events and Traces if the
434
+ configuration from the server disables _Error Collection_.
435
+
436
+ ## v6.5.0
437
+
438
+ * **Change to default setting for ActiveRecord connection resolution**
439
+
440
+ Due to incompatibilities between the faster ActiveRecord connection resolution
441
+ released in v6.3.0 of the agent and other gems which patch ActiveRecord,
442
+ `backport_fast_active_record_connection_lookup` will now be set to `false` by default.
443
+ Because it results in a significant performance improvement, we recommend customers
444
+ whose environments include ActiveRecord change this setting to `true`
445
+ _unless_ they are using other gems which measure ActiveRecord performance, which may
446
+ lose functionality when combined with this setting. If unsure whether to enable
447
+ `backport_fast_active_record_connection_lookup`, we recommend enabling it in a
448
+ development environment to make sure other gems which patch ActiveRecord are still
449
+ working as expected.
450
+
451
+ * **Bugfix for ActiveStorage instrumentation error**
452
+
453
+ Version 6.4.0 of the agent introduced a bug that interfered with ActiveStorage
454
+ callbacks, resulting in the agent being unable to instrument ActiveStorage operations.
455
+ ActiveStorage segments are now correctly recorded.
456
+
457
+ * **Bugfix for ActiveRecord 4.1 and 4.2 exception logging**
458
+
459
+ Version 6.3.0 of the agent introduced a bug that prevented ActiveRecord versions 4.1
460
+ and 4.2 from logging exceptions that occurred within a database transaction. This
461
+ version of the agent restores the exception logging functionality from previous agent
462
+ versions.
463
+ Thanks to Oleksiy Kovyrin for the contribution!
464
+
465
+ ## v6.4.0
466
+
467
+ * **Custom Metadata Collection**
468
+
469
+ The agent now collects environment variables prefixed by `NEW_RELIC_METADATA_`. These
470
+ may be added to transaction events to provide context between your Kubernetes cluster
471
+ and your services. For details on the behavior, see
472
+ [this blog post](https://blog.newrelic.com/engineering/monitoring-application-performance-in-kubernetes/).
473
+
474
+ * **Bugfix for faster ActiveRecord connection resolution**
475
+
476
+ Version 6.3.0 of the agent backported the faster ActiveRecord connection resolution
477
+ from Rails 6.0 to previous versions, but the implementation caused certain other gems
478
+ which measured ActiveRecord performance to stop working. This version of the agent
479
+ changes the implementation of this performance improvement so no such conflicts occur.
480
+
481
+ * **Bugfix for Grape instrumentation error**
482
+
483
+ Previous versions of the agent would fail to install Grape instrumentation in Grape
484
+ versions 1.2.0 and up if the API being instrumented subclassed `Grape::API::Instance`
485
+ rather than `Grape::API`. A warning would also print to the newrelic_agent log:
486
+ ```
487
+ WARN : Error in Grape instrumentation
488
+ WARN : NoMethodError: undefined method `name' for nil:NilClass
489
+ ```
490
+
491
+ This version of the agent successfully installs instrumentation for subclasses
492
+ of `Grape::API::Instance`, and these log messages should no longer appear.
493
+
494
+ * **Bugfix for streaming responses**
495
+
496
+ Previous versions of the agent would attempt to insert JavaScript instrumentation into
497
+ any streaming response that did not make use of `ActionController::Live`. This resulted
498
+ in an empty, non-streamed response being sent to the client.
499
+
500
+ This version of the agent will not attempt to insert JavaScript instrumentation into
501
+ a response which includes the header `Transfer-Encoding=chunked`, which indicates a
502
+ streaming response.
503
+
504
+ This should exclude JavaScript instrumentation for all streamed responses. To include
505
+ this instrumentation manually, see
506
+ [Manually instrument via agent API](https://docs.newrelic.com/docs/agents/ruby-agent/features/new-relic-browser-ruby-agent#manual_instrumentation)
507
+ in our documentation.
508
+
509
+ ## v6.3.0
510
+
511
+ * **Official Rails 6.0 support**
512
+
513
+ This version of the agent has been verified against the Rails 6.0.0 release.
514
+
515
+ As ActiveRecord 4, 5, and 6 use the same New Relic instrumentation, the
516
+ `disable_active_record_4` and `disable_active_record_5` settings in NewRelic.yml are being
517
+ deprecated in favor of the new `disable_active_record_notifications`. This new
518
+ setting will affect the instrumentation of ActiveRecord 4, 5, and 6. The deprecated settings
519
+ will be removed in a future release.
520
+
521
+ * **Bugfix for `newrelic deployments` script**
522
+
523
+ For applications housed in the EU, the `newrelic deployments` script included with previous
524
+ versions of the agent would fail with the following message: `Deployment not recorded:
525
+ Application does not exist.` This is because the script would attempt to send the deployment
526
+ notification to the US region. The deployment script now sends deployments to the correct region.
527
+
528
+ * **Faster ActiveRecord connection resolution**
529
+
530
+ This version of the agent uses the faster ActiveRecord connection resolution that Rails 6.0 uses, even on previous versions of Rails.
531
+ Thanks to Callum Jones for the contribution!
532
+
533
+ * **Support non-ascii characters in hostnames**
534
+
535
+ Previous versions of the agent would frequently log warnings like: `log writing failed. "\xE2" from ASCII-8BIT to UTF-8` if the hostname contained a non-ascii character. This version of the agent will no longer log these warnings.
536
+ Thanks to Rafael Petry for the contribution!
537
+
538
+ ## v6.2.0
539
+
540
+ * Bugfix for superfluous `Empty JSON response` error messages
541
+
542
+ Version 6.1.0 of the agent frequently logged error messages about an empty
543
+ JSON response, when no error had occurred. These logs no longer appear.
544
+
545
+ * Bugfix for `Unable to calculate elapsed transaction time` warning messages
546
+
547
+ Ruby Agent versions 5.4 through 6.1, when running in jruby without
548
+ ObjectSpace enabled, would occasionally log a warning indicating that the
549
+ agent was unable to calculate the elapsed transaction time. When this log
550
+ statement appeared, the affected transactions would not be included in the
551
+ data displayed on the capacity analysis page. These transactions are now
552
+ correctly recorded.
553
+
554
+ ## v6.1.0
555
+
556
+ * Performance monitoring on Kubernetes
557
+
558
+ This release adds Transaction event attributes that provide
559
+ context between your Kubernetes cluster and services. For details
560
+ on the benefits, see this [blog
561
+ post](https://blog.newrelic.com/engineering/monitoring-application-performance-in-kubernetes/).
562
+
563
+ * Bugfix for Bunny instrumentation when popping empty queues
564
+
565
+ When a customer calls `Bunny::Queue#pop` on an empty queue, Bunny
566
+ returns a `nil` value. Previous Ruby Agent versions raised a
567
+ `NoMethodError` when trying to process this result. Now, the
568
+ agent correctly skips processing for `nil` values. Thanks to
569
+ Matt Campbell for the contribution.
570
+
571
+ ## v6.0.0
572
+
573
+ * Tracer API for flexible custom instrumentation
574
+
575
+ With agent version 6.0, we are introducing the `Tracer` class, an
576
+ officially supported public API for more flexible custom
577
+ instrumentation. By calling its `in_transaction` method, you can
578
+ instrument an arbitrary section of Ruby code without needing to
579
+ juggle any explicit state. Behind the scenes, the agent will
580
+ make sure that the measured code results in an APM segment inside
581
+ a transaction.
582
+
583
+ The same API contains additional methods for creating
584
+ transactions and segments, and for interacting with the current
585
+ transaction. For more details, see the [custom instrumentation
586
+ documentation](https://docs.newrelic.com/docs/agents/ruby-agent/api-guides/ruby-custom-instrumentation).
587
+
588
+ If you were previously using any of the agent's private,
589
+ undocumented APIs, such as `Transaction.wrap` or
590
+ `Transaction.start/stop`, you will need to update your code to
591
+ use the Tracer API.
592
+
593
+ The full list of APIs that were removed or deprecated are:
594
+ * `External.start_segment`
595
+ * `Transaction.create_segment`
596
+ * `Transaction.start`
597
+ * `Transaction.stop`
598
+ * `Transaction.start_datastore_segment`
599
+ * `Transaction.start_segment`
600
+ * `Transaction.wrap`
601
+ * `TransactionState.current_transaction`
602
+
603
+ If are you using any of these APIs, please see the [upgrade guide](https://docs.newrelic.com/docs/agents/ruby-agent/troubleshooting/update-private-api-calls-public-tracer-api) for a list of replacements.
604
+
605
+ * Agent detects Rails 6.0
606
+
607
+ The agent properly detects Rails 6.0 and no longer logs an error when
608
+ started in a Rails 6.0 environment. This does not include full Rails 6.0
609
+ support, which will be coming in a future release. Thanks to Jacob Bednarz
610
+ for the contribution.
611
+
612
+ ## v5.7.0
613
+
614
+ * Ruby 2.6 support
615
+
616
+ We have tested the agent with the official release of Ruby 2.6.0
617
+ made on December 25, 2018, and it looks great! Feel free to use
618
+ agent v5.7 to measure the performance of your Ruby 2.6
619
+ applications.
620
+
621
+ * Support for loading Sequel core standalone
622
+
623
+ Earlier versions of the agent required users of the Sequel data
624
+ mapping library to load the _entire_ library. The agent will now
625
+ enable Sequel instrumentation when an application loads Sequel's
626
+ core standalone; i.e., without the `Sequel::Model` class. Thanks
627
+ to Vasily Kolesnikov for the contribution!
628
+
629
+ * Grape 1.2 support
630
+
631
+ With agent versions 5.6 and earlier, Grape 1.2 apps reported
632
+ their transactions under the name `Proc#call` instead of the name
633
+ of the API endpoint. Starting with agent version 5.7, all
634
+ existing versions of Grape will report the correct transaction
635
+ name. Thanks to Masato Ohba for the contribution!
636
+
637
+ ## v5.6.0
638
+
639
+ * Bugfix for transactions with `ActionController::Live`
640
+
641
+ Previously, transactions containing `ActionController::Live` resulted in
642
+ incorrect calculations of capacity analysis as well as error backtraces
643
+ appearing in agent logs in agent versions 5.4 and later. The agent now
644
+ correctly calculates capacity for transactions with `ActionController::Live`.
645
+
646
+ * Add ability to exclude attributes from span events and transaction
647
+ segments
648
+
649
+ Agent versions 5.5 and lower could selectively exclude attributes
650
+ from page views, error traces, transaction traces, and
651
+ transaction events. With agent version 5.6 and higher, you can
652
+ also exclude attributes from span events (via the
653
+ `span_events.include/exclude` options) and from transaction
654
+ segments (via the `transaction_segments.include/exclude` options).
655
+
656
+ As with other attribute destinations, these new options will
657
+ inherit values from the top-level `attributes.include/exclude`
658
+ settings. See the
659
+ [documentation](https://docs.newrelic.com/docs/agents/ruby-agent/attributes/enabling-disabling-attributes-ruby)
660
+ for more information.
661
+
662
+ * Increasing backoff sequence on failing to connect to New Relic
663
+
664
+ If the agent cannot reach New Relic, it will now wait for an
665
+ increasing amount of time after each failed attempt. We are also
666
+ starting with a shorter delay initially, which will help customer
667
+ apps bounce back more quickly from transient network errors.
668
+
669
+ * Truncation of long stack traces
670
+
671
+ Previous versions of the agent would truncate long stack traces to
672
+ 50 frames. To give customers more flexibility, we have added the
673
+ `error_collector.max_backtrace_frames` configuration option.
674
+ Thanks to Patrick Tulskie for the contribution!
675
+
676
+ * Update link in documentation
677
+
678
+ The community forum link in `README.md` now goes to the updated
679
+ location. Thanks to Sam Killgallon for the contribution!
680
+
681
+ * Active Storage instrumentation
682
+
683
+ The agent now provides instrumentation for Active Storage, introduced in
684
+ Rails 5.2. Customers will see Active Storage operations represented as
685
+ segments within transaction traces.
686
+
687
+ ## v5.5.0
688
+
689
+ * Bugfix for `perform` instrumentation with curb gem
690
+
691
+ Use of curb's `perform` method now no longer results in nil headers
692
+ getting returned.
693
+
694
+ * Bugfix for parsing Docker container IDs
695
+
696
+ The agent now parses Docker container IDs correctly regardless of the
697
+ cgroup parent.
698
+
699
+ * Use lazy load hooks for ActiveJob instrumentation
700
+
701
+ In some instances the ActiveJob instrumentation could trigger ActiveJob
702
+ to load before it was initialized by Rails. This could result in
703
+ configuration changes not being properly applied. The agent now uses lazy
704
+ load hooks which fixes this issue.
705
+
706
+ * Documentation improvement
707
+
708
+ The `config.dot` diagram of the agent's configuration settings no
709
+ longer includes the deleted `developer_mode` option. Thanks to
710
+ Yuichiro Kaneko for the contribution!
711
+
712
+ ## v5.4.0
713
+
714
+ * Capacity analysis for multi-threaded dispatchers
715
+
716
+ Metrics around capacity analysis did not previously account for multi-threaded
717
+ dispatchers, and consequently could result in capacities of over 100% being
718
+ recorded. This version now properly accounts for multi-threaded dispatchers.
719
+
720
+ * `NewRelic::Agent.disable_transaction_tracing` deprecated
721
+
722
+ `NewRelic::Agent.disable_transaction_tracing` has been deprecated. Users
723
+ are encouraged to use `NewRelic::Agent.disable_all_tracing` or
724
+ `NewRelic::Agent.ignore_transaction` instead.
725
+
726
+ * Bugfix for SQL over-obfuscation
727
+
728
+ A bug, introduced in v5.3.0, where SQL could be over-obfuscated for some
729
+ database adapters has been fixed.
730
+
731
+ * Bugfix for span event data in Resque processes
732
+
733
+ A bug where span events would not be sent from Resque processes due to a
734
+ missing endpoint has been fixed.
735
+
736
+ ## v5.3.0 ##
737
+
738
+ * Distributed Tracing
739
+
740
+ Distributed tracing lets you see the path that a request takes as
741
+ it travels through your distributed system. By showing the
742
+ distributed activity through a unified view, you can troubleshoot
743
+ and understand a complex system better than ever before.
744
+
745
+ Distributed tracing is available with an APM Pro or equivalent
746
+ subscription. To see a complete distributed trace, you need to
747
+ enable the feature on a set of neighboring services. Enabling
748
+ distributed tracing changes the behavior of some New Relic
749
+ features, so carefully consult the
750
+ [transition guide](https://docs.newrelic.com/docs/transition-guide-distributed-tracing)
751
+ before you enable this feature.
752
+
753
+ To enable distributed tracing, set the
754
+ `distributed_tracing.enabled` configuration option to `true`.
755
+
756
+ ## v5.2.0 ##
757
+
758
+ * Use priority sampling for errors and custom events
759
+
760
+ Priority sampling replaces the older reservoir event sampling method.
761
+ With this change, the agent will maintain randomness across a given
762
+ time period while improving coordination among transactions, errors,
763
+ and custom events.
764
+
765
+ * Bugfix for wrapping datastore operations
766
+
767
+ The agent will now complete the process of wrapping datastore
768
+ operations even if an error occurs during execution of a callback.
769
+
770
+ * Span Events
771
+
772
+ Finished segments whose `sampled` property is `true` will now post
773
+ Span events to Insights.
774
+
775
+ ## v5.1.0 ##
776
+
777
+ * Rails 5.2 support
778
+
779
+ The Ruby agent has been validated against the latest release of
780
+ Ruby on Rails!
781
+
782
+ * Support for newer libraries and frameworks
783
+
784
+ We have updated the multiverse suite to test the agent against
785
+ current versions of several frameworks.
786
+
787
+ * Add `custom_attributes.enabled` configuration option
788
+
789
+ This option is enabled by default. When it's disabled, custom
790
+ attributes will not be transmitted on transaction events or error
791
+ events.
792
+
793
+ * Fix Grape load order dependency
794
+
795
+ The agent will now choose the correct name for Grape transactions
796
+ even if the customer's app loads the agent before Grape. Thanks
797
+ to Daniel Doubrovkine for the contribution!
798
+
799
+ * Add `webpacker:compile` to blacklisted tasks
800
+
801
+ `webpacker:compile` is commonly used for compiling assets. It has
802
+ been added to `AUTOSTART_BLACKLISTED_RAKE_TASKS` in the default
803
+ configuration. Thanks to Claudio B. for the contribution!
804
+
805
+ * Make browser instrumentation W3C-compliant
806
+
807
+ `type="text/javascript"` is optional for the `<script>` tag under
808
+ W3C. The `type` attribute has now been removed from browser
809
+ instrumentation. Thanks to Spharian for the contribution!
810
+
811
+ * Deferred `add_method_tracer` calls
812
+
813
+ If a third-party library calls `add_method_tracer` before the
814
+ agent has finished starting, we now queue these calls and run them
815
+ when it's safe to do so (rather than skipping them and logging a
816
+ warning).
817
+
818
+ * Bugfix for Resque `around` / `before` hooks
819
+
820
+ In rare cases, the agent was not instrumenting Resque `around` and
821
+ `before` hooks. This version fixes the error.
822
+
823
+ * Truncation of long stack traces
824
+
825
+ Occasionally, long stack traces would cause complications sending
826
+ data to New Relic. This version truncates long traces to 50 frames
827
+ (split evenly between the top and bottom of the trace).
828
+
829
+ ## v5.0.0 ##
830
+
831
+ * SSL connections to New Relic are now mandatory
832
+
833
+ Prior to this version, using an SSL connection to New Relic was
834
+ the default behavior, but could be overridden. SSL connections are
835
+ now enforced (not overrideable).
836
+
837
+ * Additional security checking before trying to explain
838
+ multi-statement SQL queries
839
+
840
+ Customer applications might submit SQL queries containing multiple
841
+ statements (e.g., SELECT * FROM table; SELECT * FROM table). For
842
+ security reasons, we should not generate explain plans in this
843
+ situation.
844
+
845
+ Although the agent correctly skipped explain plans for these
846
+ queries during testing, we have added extra checks for this
847
+ scenario.
848
+
849
+ * Bugfix for RabbitMQ exchange names that are symbols
850
+
851
+ The agent no longer raises a TypeError when a RabbitMQ exchange
852
+ name is a Ruby symbol instead of a string.
853
+
854
+ * Bugfix for audit logging to stdout
855
+
856
+ Previous agents configured to log to stdout would correctly send
857
+ regular agent logs to stdout, but would incorrectly send audit
858
+ logs to a text file named "stdout". This release corrects the
859
+ error.
860
+
861
+ * Bugfix for Capistrano deployment notifications on v3.7 and beyond
862
+
863
+ Starting with version 3.7, Capistrano uses a different technique
864
+ to determine a project's version control system. The agent now
865
+ works correctly with this new behavior. Thanks to Jimmy Zhang for
866
+ the contribution.
867
+
868
+ ## v4.8.0 ##
4
869
 
5
870
  * Initialize New Relic Agent before config initializers
6
871
 
@@ -22,7 +887,7 @@
22
887
  It is now an agent attribute that can be controlled via the attributes config.
23
888
  For more information on agent attributes [see here](https://docs.newrelic.com/docs/agents/manage-apm-agents/agent-data/agent-attributes).
24
889
 
25
- ## 4.7.1 ##
890
+ ## 4.7.1 ##
26
891
 
27
892
  * Bugfix for Manual Browser Instrumentation
28
893
 
@@ -32,7 +897,7 @@
32
897
  instrumentation. Those changes have been reverted. We will revisit this issue
33
898
  in an upcoming release.
34
899
 
35
- ## v4.7.0 ##
900
+ ## v4.7.0 ##
36
901
 
37
902
  * Expected Error API
38
903