James Bunch

As @kaylareopelle mentions above in reference to #2341, there are 2 key aspects to this issue: - Supporting JSON formatted log data - Supporting the Logstasher gem's functions When we...

For this issue to be addressed in the same manner as #2378, we'd want to store a fork of [resolve-replace.rb](https://github.com/ruby/resolv-replace/blob/master/lib/resolv-replace.rb) locally and then reference it with a `require_relative` and remove...

Hi @ArturT, Thank you for sharing the workaround. > But if you selected API endpoint instead of background sidekiq worker then Redis host name is not visible. It's just showing...

> To keep this issue separate I created a new issue Perfect. Thanks, @ArturT!

We have a great [internal conversation](https://newrelic.slack.com/archives/C050GQJM4/p1698860222998639) going that references a repro repo. The definition of done for this issue will be to have that repo no longer able to reproduce...

The .gem files available from RubyGems.org are gzipped tarballs and they contain a gzipped `checksums.yaml` file. I wonder if the checksums stored within that file could establish trust. Unfortunately if...

Here's where we're at currently for alignment with the existing NR Lambda spec: **Complete** - The absence of a config file should be expected and not warned about - The...

All agent work is now ready for review with 2474. Other NR repos for Lambda and documentation will still need to be updated.

The original scope of this one has been satisfied. We're code complete and will track testing, documentation, and updates to relevant CI/CD repos separately with other issues.

NOTE: RJIT innovation has been split out into the separate innovation issue https://github.com/newrelic/newrelic-ruby-agent/issues/2332