[dependabot]

Bumps newrelic_rpm from 10.7.1 to 10.9.1.

Changelog

Sourced from newrelic_rpm's changelog.

v10.9.1

• Bugfix: Action Controller instrumentation no longer errors when it can't identify the controller class

  When the agent could not identify a request's controller class, it logged TypeError: no implicit conversion of nil into String and then NoMethodError: undefined method 'finish' for nil, and recorded no data for that request. These transactions are now named Controller/(unknown)/<action> and recorded normally. PR#3691

• Bugfix: Prevent Parallel workers from hanging when reporting large payloads

  When parallel instrumentation was enabled, Parallel.each/Parallel.map with in_processes: could hang forever. Each worker inherited the pipe write ends the agent registered for its earlier siblings, so those pipes couldn't reach end-of-file, and the agent's pipe listener thread blocked waiting on one of them. Any worker whose data exceeded the operating system pipe buffer then blocked on exit. Now, the agent closes each pipe's write end in the parent right after forking, and the listener no longer blocks on a single pipe while others still have data waiting. Thank you to @​yayamochi for reporting this bug. Issue#3680 PR#3688

• Bugfix: gRPC calls no longer fail on requests from Synthetics monitors

  When a request from a Synthetics monitor made a gRPC call, the agent added X-NewRelic-Synthetics to the call's metadata. gRPC only allows lowercase metadata keys, so the call raised ArgumentError: 'X-NewRelic-Synthetics' is an invalid header key. The agent now sends the synthetics headers in lowercase. gRPC server transactions also now read the synthetics headers from incoming metadata, so a gRPC service called during a Synthetics check records its trace and Synthetics attributes. PR#3693

v10.9.0

• Feature: Continuous Profiling (preview)

  Continuous Profiling is a new feature which is not yet generally available for use. The agent-side component code is now present in the agent but to actually use it ahead of the General Availability release, you will need to contact your New Relic sales representative to join the preview early.

  Continuous Profiling repeatedly samples the Ruby call stacks of your running application and reports them to New Relic, so you can see which methods are consuming the most CPU time (or allocating the most objects) in production, without adding code to your app.

  To turn it on, add the stackprof and google-protobuf gems to your application's Gemfile, then set profiling.enabled to true:

    profiling.enabled: true

  With only profiling.enabled set, the agent samples CPU time every 10 milliseconds for the life of the process. These options let you tune that behavior:

  Configuration name	Default	Behavior
  profiling.enabled	false	If true, the agent collects and reports continuous profiling data.
  profiling.include	cpu	What to sample: cpu for CPU time, or object for object allocations.
  profiling.sample_period	0.01	Seconds between stack samples. Only used when profiling.include is cpu. Must be between 0.000001 and 0.999999.
  profiling.object_allocation_interval	10000	Object allocations between stack samples. Only used when profiling.include is object. Must be between 1000 and 999999.
  profiling.delay	0	Milliseconds to wait before profiling starts. 0 starts immediately.
  profiling.duration	0	Milliseconds to profile before stopping automatically. 0 profiles until the process exits.

  PR#3617

• Feature: Add support for Dalli 5.1.1

  Dalli 5.1.1 added arguments to some of the methods the agent instruments, which could raise an ArgumentError on multi-key operations or cause request options to be silently dropped. Now, the agent accepts and forwards a variable number of positional and keyword arguments for these methods. PR#3683

v10.8.0

• Feature: Report a unique hostname for Google Cloud Run Worker Pools and Jobs

  The Cloud Run hostname support added in PR#3609 detected Cloud Run by looking for K_REVISION, which Cloud Run Services set. The agent now also recognizes CLOUD_RUN_REVISION (Worker Pools) and CLOUD_RUN_EXECUTION (Jobs), so utilization.gcp_cloud_run.use_instance_as_host applies to all three resource types. When utilization.gcp_cloud_run.include_revision_in_host is true, the hostname uses whichever of those variables is set, for example {CLOUD_RUN_EXECUTION}-{instance id} on a Job. Issue#3651 Thanks to @​choznerol for contributing this enhancement! PR#3652

... (truncated)

Commits

• 7c08652 Merge pull request #3699 from newrelic/prerelease_updates_10.9.1-pre
• d7293c6 bump version
• 2c995af Merge pull request #3693 from newrelic/grpc_synthetics_monitoring
• 8008f90 Refactor
• 2fd8687 Add changelog and tests
• 59d2e68 Merge pull request #3696 from newrelic/make_test_app_rails_edge_able
• 8c5b53b they changed rails edge, the thing we were doing in our test app is illegal now
• 0b3b3ef Merge pull request #3695 from newrelic/dependabot/github_actions/actions/chec...
• 32ec933 Bump actions/checkout from 7.0.0 to 7.0.1
• cde3efe Merge pull request #3694 from newrelic/dependabot/github_actions/ruby/setup-r...
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 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)