zooniverse / education-api

Backend for Zooniverse Classrooms
1 stars 1 forks source link

Bump newrelic_rpm from 4.7.1.340 to 9.1.0 #401

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps newrelic_rpm from 4.7.1.340 to 9.1.0.

Release notes

Sourced from newrelic_rpm's releases.

9.1.0

No release notes provided.

9.1.0-pre

Pre-release for v9.1.0

9.0.0

No release notes provided.

9.0.0-pre

Pre-release for 9.0.0

8.16.0

No release notes provided.

8.16.0-pre2

No release notes provided.

8.16.0-pre

Pre-release for 8.16.0

CHANGELOG

8.15.0

No release notes provided.

8.15.0-pre2

Updates to set infinite tracing batching to true by default.

Full Changelog: https://github.com/newrelic/newrelic-ruby-agent/compare/8.14.0...8.15.0-pre2

8.15.0-pre

Pre-release for 8.15.0

8.14.0

No release notes provided.

8.14.0-pre

New Relic Ruby agent release 8.14.0-pre

What's Changed:

  • Deployment Recipe: Restore desired Capistrano-based changelog lookup behavior #1653
  • Speed up GUID generation #1693
  • Support for Rails ActiveSupport::Notifications for custom events #1659
  • Bugfix: Support older versions of the RedisClient gem, handle unknown Redis database index #1673
  • Bugfix: Defer agent startup in Rails until after application-defined initializers have run #1658

Full Changelog: https://github.com/newrelic/newrelic-ruby-agent/compare/8.13.1...8.14.0-pre

... (truncated)

Changelog

Sourced from newrelic_rpm's changelog.

v9.1.0

Version 9.1.0 of the agent delivers support for two new errors inbox features: error fingerprinting and user tracking, identifies the Amazon Timestream data store, removes Distributed Tracing warnings from agent logs when using Sidekiq, fixes bugs, and is tested against the recently released JRuby 9.4.2.0.

  • Feature: Error fingerprinting - supply your own errors inbox group names

    Are your error occurrences grouped poorly? Set your own error fingerprint via a callback function. A new set_error_group_callback public API method has been added that will accept a user defined proc. The proc will be invoked for each noticed error and whenever it returns a string, that string will be used as the error group name for the error and will take precedence over any server-side grouping that takes place with the New Relic errors inbox. This gives users much greater control over the grouping of their errors.

    The customer defined proc will be expected to receive exactly one input argument, a hash. The hash contains the following:

    Key Value
    :error The Ruby error class instance. Offers #class, #message, and #backtrace
    :customAttributes Any customer defined custom attributes for the current transaction
    :'request.uri' The current request URI if available
    :'http.statusCode' The HTTP status code (200, 404, etc.) if available
    :'http.method' The HTTP method (GET, PUT, etc.) if available
    :'error.expected' Whether (true) or not (false) the error was expected
    :'options' The options hash passed to NewRelic::Agent.notice_error

    The callback only needs to be set once per initialization of the New Relic agent.

    Example usage:

    proc = proc { |hash| "Access" if hash[:'http.statusCode'] == 401 }
    NewRelic::Agent.set_error_group_callback(proc)
    
  • Feature: User tracking - associate errors with a user id

    You can now see the number of users impacted by an error group. Identify the end user with a new set_user_id public API method that will accept a string representation of a user id and associate that user id with the current transaction. Transactions and errors will then have a new enduser.id agent attribute associated with them. This will allow agent users to tag transactions and errors as belonging to given user ids in support of greater filtering and alerting capabilities.

  • Identify Amazon Timestream when the amazon_timestream AR adapter is used

    When the agent sees the activerecord-amazon-timestream-adapter gem being used, it will now identify the data store as "Timestream". Thanks very much to @​wagner for contributing this enhancement! PR#1872

  • Bugfix: Remove Distributed Tracing related warnings from agent logs when headers are not present in Sidekiq

    Previously, the agent would log a warning to newrelic_agent.log every time it attempted to accept empty Distributed Tracing headers from Sidekiq jobs which could result in an excessive number of warnings. Now the agent will no longer create these warnings when using Sidekiq. PR#1834

  • Bugfix: Log request headers in debug-level logs instead of human-readable Objects

    Previously, the agent sometimes received children of the NewRelic::Agent::HTTPClients::AbstractRequest class as an argument when NewRelic::Agent::Transaction::DistributedTracers#log_request_headers was called. This caused debug-level log messages that print the request headers to show human-readable Objects (ex. #<NewRelic::Agent::HTTPClients::HTTPClientRequest:0x00007fd0dda983e0>) instead of the request headers. Now, the hash of the request headers should always be logged. PR#1839

  • Bugfix: Fix undefined method controller_path logged in Action Controller Instrumentation

    Previously, the agent could log an error when trying to determine the metric name in the Action Controller instrumentation if the controller class did not respond to controller_path. This has been resolved and the agent will no longer call this method unless the class responds to it. Thank you to @​gsar for letting us know about this issue. PR#1844

  • Bugfix: Fix Transaction#finish exception and decrease log level for related warning during async transactions

... (truncated)

Commits
  • a5d5bad Merge pull request #1912 from newrelic/v910
  • 13478cb v9.1.0
  • 6eae525 Merge pull request #1883 from newrelic/error_fingerprinting_user_tracking
  • 99ef842 Merge pull request #1897 from newrelic/test_mdx_parser
  • 71ad8ad Update .github/workflows/scripts/generate_release_notes.rb
  • 7bc24ca Make script classy
  • a8d966d Update CHANGELOG.md
  • 168e466 errors inbox CHANGELOG updates for dev merge
  • 8629f0d Merge branch 'dev' into error_fingerprinting_user_tracking
  • a637ebc CHANGELOG updates for error inbox features
  • 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 1 year ago

Superseded by #404.