Skip to content

Commit 8fc3ea6

Browse files
authored
Merge pull request #2873 from newrelic/2870_test_and_changelog_entry
unit test and CHANGELOG entry for 2870
2 parents 3063ea8 + ad5f9b8 commit 8fc3ea6

File tree

2 files changed

+16
-1
lines changed

2 files changed

+16
-1
lines changed

CHANGELOG.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## v9.14.0
44

5-
Version 9.14.0 adds Apache Kafka instrumentation for the rdkafka and ruby-kafka gems, introduces a configuration-based, automatic way to add custom instrumentation method tracers, correctly captures MIME type for AcionDispatch 7.0+ requests, properly handles Boolean coercion for `newrelic.yml` configuration, fixes a JRuby bug in the configuration manager, and fixes a bug related to `Bundler.rubygems.installed_specs`.
5+
Version 9.14.0 adds Apache Kafka instrumentation for the rdkafka and ruby-kafka gems, introduces a configuration-based, automatic way to add custom instrumentation method tracers, correctly captures MIME type for AcionDispatch 7.0+ requests, properly handles Boolean coercion for `newrelic.yml` configuration, fixes a JRuby bug in the configuration manager, fixes a bug related to `Bundler.rubygems.installed_specs`, and fixes a bug to make the agent compatible with ViewComponent v3.15.0+.
66

77
- **Feature: Add Apache Kafka instrumentation for the rdkafka and ruby-kafka gems**
88

@@ -78,6 +78,10 @@ Version 9.14.0 adds Apache Kafka instrumentation for the rdkafka and ruby-kafka
7878

7979
To address a recent Bundler deprecation warning, we started using `Bundler.rubygems.installed_specs` instead of `Bundler.rubygems.all_specs` in environments that seemed appropriate. We discovered the version constraint we used was too low. Now, rather than check the version, we check for the method using `respond_to?`. [PR#2853](https://github.com/newrelic/newrelic-ruby-agent/pull/2853)
8080

81+
- **Bugfix: Support view_component v3.15.0+**
82+
83+
Previously the agent had been making use of a private API to obtain a component identifier value. This private API was dropped in v3.15.0 of view_component, resulting in errors from the New Relic Ruby agent's continued attempts to use it. Many thanks to community member [@navidemad](https://github.com/navidemad) for bringing this issue to our attention and supplying a bugfix with [PR#2870](https://github.com/newrelic/newrelic-ruby-agent/pull/2870).
84+
8185
## v9.13.0
8286

8387
Version 9.13.0 enhances support for AWS Lambda functions, adds experimental OpenSearch instrumentation, updates framework detection, silences a Bundler deprecation warning, fixes Falcon dispatcher detection, fixes a bug with Redis instrumentation installation, and addresses a JRuby-specific concurrency issue.

test/multiverse/suites/view_component/view_component_instrumentation_test.rb

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,4 +57,15 @@ def test_error_raised
5757
assert_equal(500, get('/view_components'))
5858
end
5959
end
60+
61+
# Test metric name being built when the controller class doesn't respond to :identifier
62+
# https://github.com/newrelic/newrelic-ruby-agent/pull/2870
63+
def test_the_metric_name_omits_the_identifier_when_absent
64+
in_transaction do |txn|
65+
FAKE_CLASS.render_in_with_tracing { 11 * 38 }
66+
actual_name = txn.segments.last.name
67+
68+
assert_equal 'View/component/DummyViewComponentInstrumentationClass', actual_name
69+
end
70+
end
6071
end

0 commit comments

Comments
 (0)