Skip to content

Conversation

@neiljpowell
Copy link
Contributor

@neiljpowell neiljpowell commented Oct 2, 2019

New categorical eventType to publish New Relic metrics and
meterNameEventTypeEnabled(true) for compatibility with previous
behavior of publishing an eventType per Meter/metric name.

NewRelic's own agents publish metrics to eventTypes aligned with broader
categories. To align with their recommendation the default behavior is
to publish metrics under a "SpringBootSample" category. When doing so,
additional context is provided by including "metricName" and "metricType" attributes.
See: https://docs.newrelic.com/docs/insights/insights-data-sources/default-data/insights-default-data-other-new-relic-products

@shakuzen
@breedx-nr

New categorical eventType to publish New Relic metrics and
meterNameEventTypeEnabled (true) for compatibility with previous
behavior of publishing an eventType per Meter/metric name.

NewRelic's own agents publish metrics to eventTypes aligned with broader
categories. To align with their recommendation the default behavior is
to publish metrics under a "SpringBootSample" category. When doing so,
additional context is provided by including "metricName" and
"metricType" attributes.
See: https://docs.newrelic.com/docs/insights/insights-data-sources/default-data/insights-default-data-other-new-relic-products
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Oct 2, 2019
@wilkinsona wilkinsona changed the title Add support for new Micrometer NewRelicConfig properties. Add support for new Micrometer NewRelicConfig properties Oct 2, 2019
@neiljpowell
Copy link
Contributor Author

Build failures appear to be issues unrelated to this PR. After merging in master, error is now from the Spring Boot Docs project:
Plugin org.asciidoctor:asciidoctor-maven-plugin:1.6.0 or one of its dependencies could not be resolved: Could not find artifact io.spring.asciidoctor:spring-asciidoctor-extensions-spring-boot:jar:0.3.0.RELEASE in central (https://repo.maven.apache.org/maven2)
@wilkinsona can you confirm?

@wilkinsona
Copy link
Member

Confirmed. Sorry for the inconvenience. The problem should be fixed in master now. Don't worry about the build failure as the changes proposed here are built before the docs module where the problem is occurring.

Copy link
Member

@shakuzen shakuzen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@shakuzen
Copy link
Member

shakuzen commented Oct 2, 2019

Just for reference, micrometer-metrics/micrometer#1588 is the pull request that added these config properties to Micrometer 1.3. Once these changes are made in Spring Boot, feel free to also send a pull request to Micrometer's micrometer-spring-legacy module on the 1.3.x branch if you're interested @neiljpowell.

@wilkinsona wilkinsona added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Oct 2, 2019
@wilkinsona wilkinsona added this to the 2.2.x milestone Oct 2, 2019
@philwebb philwebb added the for: merge-with-amendments Needs some changes when we merge label Oct 2, 2019
@neiljpowell
Copy link
Contributor Author

@wilkinsona Thanks for the quick confirmation and note. I'll still try another rebase from master to see if it will build cleanly. @shakuzen Thanks for the review and reference to the initiating PR. I'll be happy to get the legacy project updated.

New categorical eventType to publish New Relic metrics and
meterNameEventTypeEnabled (true) for compatibility with previous
behavior of publishing an eventType per Meter/metric name.

NewRelic's own agents publish metrics to eventTypes aligned with broader
categories. To align with their recommendation the default behavior is
to publish metrics under a "SpringBootSample" category. When doing so,
additional context is provided by including "metricName" and
"metricType" attributes.
See: https://docs.newrelic.com/docs/insights/insights-data-sources/default-data/insights-default-data-other-new-relic-products
@philwebb philwebb changed the title Add support for new Micrometer NewRelicConfig properties Support new Micrometer NewRelicConfig eventType properties Oct 3, 2019
@philwebb philwebb self-assigned this Oct 3, 2019
philwebb pushed a commit that referenced this pull request Oct 3, 2019
Update `NewRelicProperties` so that the event type sent with each
metric can be configured. An additional `boolean` property has
also been added if the previous behavior using the "meter-name"
is required.

NewRelic's own agents publish metrics to eventTypes aligned with broader
categories. To align with their recommendation the default behavior is
to publish metrics under a "SpringBootSample" category. When doing so,
additional context is provided by including "metricName" and
"metricType" attributes.

See gh-18472
philwebb added a commit that referenced this pull request Oct 3, 2019
@philwebb philwebb closed this in 4cfbe7f Oct 3, 2019
@philwebb philwebb modified the milestones: 2.2.x, 2.2.0.RC1 Oct 3, 2019
@philwebb
Copy link
Member

philwebb commented Oct 3, 2019

Thanks very much for the PR @neiljpowell. This has now been merged to master and should be in RC1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

for: merge-with-amendments Needs some changes when we merge type: enhancement A general enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants