Bump newrelic_rpm from 4.7.1.340 to 9.14.0

[dependabot]

Bumps newrelic_rpm from 4.7.1.340 to 9.14.0.

Release notes

Sourced from newrelic_rpm's releases.

9.14.0

No release notes provided.

9.14.0-pre

No release notes provided.

9.13.0

No release notes provided.

9.13.0-pre

No release notes provided.

9.12.0

No release notes provided.

9.12.0-pre

No release notes provided.

9.11.0

No release notes provided.

9.11.0-pre

No release notes provided.

9.10.2

No release notes provided.

9.10.2-pre

No release notes provided.

9.10.1

No release notes provided.

9.10.1-pre

No release notes provided.

9.10.0

No release notes provided.

9.10.0-pre

No release notes provided.

9.9.0

No release notes provided.

9.9.0-pre

No release notes provided.

9.8.0

No release notes provided.

... (truncated)

Changelog

Sourced from newrelic_rpm's changelog.

v9.14.0

Version 9.14.0 adds Apache Kafka instrumentation for the rdkafka and ruby-kafka gems, introduces a configuration-based, automatic way to add custom instrumentation method tracers, correctly captures MIME type for AcionDispatch 7.0+ requests, properly handles Boolean coercion for newrelic.yml configuration, fixes a JRuby bug in the configuration manager, fixes a bug related to Bundler.rubygems.installed_specs, and fixes a bug to make the agent compatible with ViewComponent v3.15.0+.

• Feature: Add Apache Kafka instrumentation for the rdkafka and ruby-kafka gems

  The agent now has instrumentation for both the rdkafka and ruby-kafka gems. The agent will record transactions and message broker segments for produce and consume calls made using these gems. PR#2824 PR#2842

• Feature: Add a configuration option to permit custom method tracers to be defined automatically

  A new :automatic_custom_instrumentation_method_list configuration parameter has been added to permit the user to define a list of fully qualified (namespaced) Ruby methods for the agent to automatically add custom instrumentation for without requiring any code modifications to be made to the classes that define the methods.

  The list should be an array of CLASS#METHOD (for instance methods) and/or CLASS.METHOD (for class methods) strings.

  Use fully qualified class names (using the :: delimiter) that include any module or class namespacing.

  Here is some Ruby source code that defines a render_png instance method for an Image class and a notify class method for a User class, both within a MyCompany module namespace:

  module MyCompany
    class Image
      def render_png
        # code to render a PNG
      end
    end
  class User
  
  def self.notify
  
  # code to notify users
  
  end
  
  end
  
  end
  
  

  Given that source code, the newrelic.yml config file might request instrumentation for both of these methods like so:

  automatic_custom_instrumentation_method_list:
    - MyCompany::Image#render_png
    - MyCompany::User.notify
  

  That configuration example uses YAML array syntax to specify both methods. Alternatively, a comma-delimited string can be used instead:

  automatic_custom_instrumentation_method_list: 'MyCompany::Image#render_png, MyCompany::User.notify'
  

  Whitespace around the comma(s) in the list is optional. When configuring the agent with a list of methods via the NEW_RELIC_AUTOMATIC_CUSTOM_INSTRUMENTATION_METHOD_LIST environment variable, this comma-delimited string format should be used:

... (truncated)

Commits

• 8fc3ea6 Merge pull request #2873 from newrelic/2870_test_and_changelog_entry
• ad5f9b8 add ViewComponent fix mention to the v9.14.0 summary
• 72d32e9 unit test and CHANGELOG entry for 2870
• 3063ea8 Merge pull request #2870 from navidemad/dev
• d3bd85e Merge pull request #2871 from newrelic/railsedge-31
• bbfdb8e Update min version in unshift_rails_edge
• 485b1f2 Update Envfiles for Rails 8.0
• 9587e77 Remove railsedge testing from Ruby 3.1
• df71498 Safety check in instrumentation render_in_with_tracing that identifier to sel...
• 2897f32 Merge pull request #2868 from newrelic/changelog-tweaks-914
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)