railsbridge / bridge_troll

Event management system for all the Bridges (RailsBridge, MobileBridge, GoBridge, etc!)
https://www.bridgetroll.org
Other
281 stars 259 forks source link

Bump newrelic_rpm from 6.14.0 to 8.9.0 #1255

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps newrelic_rpm from 6.14.0 to 8.9.0.

Release notes

Sourced from newrelic_rpm's releases.

8.9.0

No release notes provided.

8.9.0-pre

No release notes provided.

8.8.0

No release notes provided.

8.8.0-pre

No release notes provided.

8.7.0

No release notes provided.

8.7.0-pre2

No release notes provided.

8.7.0-pre

Prerelease for 8.7.0

8.6.0

No release notes provided.

8.6.0-pre2

No release notes provided.

8.6.0-pre

No release notes provided.

8.5.0

No release notes provided.

8.50-pre

Prerelease for 8.5.0

8.4.0

No release notes provided.

8.4.0-pre

Prerelease for 8.4.0

8.3.0

No release notes provided.

8.3.0-pre

Prerelease for 8.3.0

8.2.0

No release notes provided.

... (truncated)

Changelog

Sourced from newrelic_rpm's changelog.

New Relic Ruby Agent Release Notes

v8.9.0

  • Add support for Dalli 3.1.0 to Dalli 3.2.2

    Dalli versions 3.1.0 and above include breaking changes where the agent previously hooked into the gem. We have updated our instrumentation to correctly hook into Dalli 3.1.0 and above. At this time, 3.2.2 is the latest Dalli version and is confirmed to be supported.

  • Bugfix: Infinite Tracing hung on connection restart

    Previously, when using infinite tracing, the agent would intermittently encounter a deadlock when attempting to restart the infinite tracing connection. This bug would prevent the agent from sending all data types, including non-infinite-tracing-related data. This change reworks how we restart infinite tracing to prevent potential deadlocks.

  • Bugfix: Use read_nonblock instead of read on pipe

    Previously, our PipeChannelManager was using read which could cause Resque jobs to get stuck in some versions. This change updates the PipeChannelManager to use read_nonblock instead. This method can leverage error handling to allow the instrumentation to gracefully log a message and exit the stuck Resque job.

v8.8.0

  • Support Makara database adapters with ActiveRecord

    Thanks to a community submission from @​lucasklaassen with [PR #1177](newrelic/newrelic-ruby-agent#1177), the Ruby agent will now correctly work well with the Makara gem. Functionality such as SQL obfuscation should now work when Makara database adapters are used with Active Record.

  • Lowered the minimum payload size to compress

    Previously the Ruby agent used a particularly large payload size threshold of 64KiB that would need to be met before the agent would compress data en route to New Relic's collector. The original value stems from segfault issues that very old Rubies (< 2.2) used to encounter when compressing smaller payloads. This value has been lowered to 2KiB (2048 bytes), which should provide a more optimal balance between the CPU cycles spent on compression and the bandwidth savings gained from it.

  • Provide Code Level Metrics for New Relic CodeStream

    For Ruby on Rails applications and/or those with manually traced methods, the agent is now capable of reporting metrics with Ruby method-level granularity. When the new code_level_metrics.enabled configuration parameter is set to a true value, the agent will associate source-code-related metadata with the metrics for things such as Rails controller methods. Then, when the corresponding Ruby class file that defines the methods is loaded up in a New Relic CodeStream-powered IDE, the four golden signals for each method will be presented to the developer directly.

  • Supportability Metrics will always report uncompressed payload size

    New Relic's agent specifications call for Supportability Metrics to always reference the uncompressed payload byte size. Previously, the Ruby agent was calculating the byte size after compression. Furthermore, compression is only performed on payloads of a certain size. This means that sometimes the value could have represented a compressed size and sometimes an uncompressed one. Now the uncompressed value is always used, bringing consistency for comparing two instances of the same metric and alignment with the New Relic agent specifications.

v8.7.0

  • APM logs-in-context log forwarding on by default

    Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about about this feature see here, and additional configuration options are available here. To learn about how to toggle log ingestion on or off by account see here.

  • Improved async support and Thread instrumentation

    Previously, the agent was not able to record events and metrics inside Threads created inside of an already running transaction. This release includes 2 new configuration options to support multithreaded applications to automatically instrument threads. A new configuration option,instrumentation.thread.tracing (disabled by default), has been introduced that, when enabled, will allow the agent to insert New Relic tracing inside of all Threads created by an application. To support applications that only want some threads instrumented by New Relic, a new class is available, NewRelic::TracedThread, that will create a thread that includes New Relic instrumentation, see our API documentation for more details.

    New configuration options included in this release:

... (truncated)

Commits
  • 5f83459 Merge pull request #1249 from newrelic/bump_version_890
  • 0cba340 Update CHANGELOG.md
  • aac0bf8 add changelog entry for read_nonblock bugfix
  • 34ca2e4 bump versions
  • ff9a6cb Merge pull request #1174 from newrelic/bugfix/infinite-tracing-agent-restarts
  • f7a647f Merge pull request #1230 from newrelic/fail_fast_interrupt_young_and_leave_a_...
  • 281838b Merge branch 'dev' into bugfix/infinite-tracing-agent-restarts
  • 713e944 Merge pull request #1236 from newrelic/フォークが存在する場合は実行しないでください
  • 478327c Merge pull request #1213 from newrelic/support_dalli_321
  • 669badc CI: don't run simplecov against forks
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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[bot] commented 2 years ago

Superseded by #1258.