Bump newrelic_rpm from 9.14.0 to 9.16.0

[dependabot]

Bumps newrelic_rpm from 9.14.0 to 9.16.0.

Changelog

Sourced from newrelic_rpm's changelog.

v9.16.0

Version 9.16.0 introduces the following features and bug fixes:

• Feature: Instrumentation for aws-sdk-lambda

  When the aws-sdk-lambda gem is available and used to invoke remote AWS Lambda functions, the timing and error details of the invocations will be reported to New Relic. PR#2926.

• Feature: Add new configuration options to attach custom tags (labels) to logs

  The Ruby agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs. With custom tags on logs, platform engineers can easily filter, search, and correlate log data for faster and more efficient troubleshooting, improved performance, and optimized resource utilization. PR#2925

• Feature: Update View Component instrumentation+

  The .identifier method will be formally exposed as part of the View Component public API. The agent will now use this method for building metric names when available, ensuring ongoing compatibility with all View Component versions. PR#2956

• Bugfix: Record explain plan traces on Rails 7.2+

  Rails 7.2 removed adapter-specific connection methods (ex. ActiveRecord::Base.postgresql_connection) and replaced them with ActiveRecord::Base.with_connection. Our explain plan feature relies on making a connection to the database to create an explain plan trace. Due to a bug in our tests, we missed this regression. Now, the agent uses the new method to fetch explain plans on Rails 7.2+. Thank you, @​gsar and @​gstark for bringing this to our attention! Issue#2922 PR#2940

v9.15.0

Version 9.15.0 updates View Component instrumentation to use a default metric name when one is unavailable, adds a configuration option to associate the AWS account ID with the DynamoDB calls from the AWS SDK, resolves a bug in rdkafka instrumentation when using the karafka-rdkafka gem, resolves a bug in the ruby-kafka instrumentation, fixes a bug with Grape instrumentation, and addresses a bug preventing the agent from running in serverless mode in an AWS Lambda layer.

• Feature: New configuration option cloud.aws.account_id

  A new configuration option has been added, cloud.aws.account_id, that will allow New Relic to provide more details about certain calls made using the AWS SDK. For example, relationships between AWS services instrumented with New Relic's CloudWatch Metric Streams will have relationships formed in the service map with APM applications. Currently, the DynamoDB instrumentation is the only instrumentation that will make use of this configuration option, but this will be used in future instrumentation as well. PR#2904

• Feature: Use default View/component metric name for unidentified View Components

  Previously, when a View Component metric name could not be identified, the agent would set the name as nil. Now, the agent defaults to using View/component as the metric name when one can not be identified. PR#2907

• Bugfix: Instrumentation errors when using the karafka-rdkafka gem

  Due to version differences between the rdkafka gem and karafka-rdkafka gem, the agent could encounter an error when it tried to install rdkafka instrumentation. This has now been resolved. Thank you to @​krisdigital for bringing this issue to our attention. PR#2880

• Bugfix: Stop calling deprecated all_specs method to check for the presence of newrelic-grape

  In 9.14.0, we released a fix for calls to the deprecated Bundler.rubygems.all_specs, but the fix fell short for the agent's Grape instrumentation and deprecation warnings could still be raised. The condition has been simplified and deprecation warnings should no longer be raised. Thank you, @​excelsior for bringing this to our attention. Issue#2885 PR#2906

• Bugfix: Instrumentation errors when using the ruby-kafka gem

  Kafka::Consumer#each_message takes keyword arguments, while the prepended method is defined with a single splat positional argument. In Ruby >= 3.0, this signature mismatch raises an ArgumentError. Thank you @​patrickarnett for providing this bugfix. PR#2915

• Bugfix: Restore AWS Lambda layer operational functionality

  Version 9.14.0 of the agent introduced an optimization related to how the agent handles boolean configuration parameters which inadvertently caused the agent to stop operating properly in an AWS Lambda layer context. Issue#2919PR#2920

Commits

• 8cb06d2 Merge pull request #2965 from newrelic/vale-linter-fixes
• 1daa60d Address vale linter concerns on config doc text
• 448f085 Merge pull request #2960 from newrelic/add-trivy-yaml
• fb2ceec Add trivy.yaml to .build_ignore
• 9ca5ec4 Add trivy.yaml for report mode scans
• 2e43f6e Merge pull request #2963 from newrelic/main-to-dev-merge-conflicts
• 0bc0c3a Merge branch 'main' into main-to-dev-merge-conflicts
• f919753 Update config
• a2fe273 Merge pull request #2958 from newrelic/prerelease_updates_9.16.0-pre
• 9981434 Merge pull request #2961 from newrelic/skip-thread-profiling
• 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)

[dependabot]

Superseded by #745.