Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename OneAgentMetadataEnrichment to DynatraceMetadataEnrichment #2692

Conversation

pirgeo
Copy link
Contributor

@pirgeo pirgeo commented Jul 8, 2021

This renames the config property from OneAgent metadata to Dynatrace metadata since the metadata retrieved is not restricted to only the OneAgent but might come from other components in the future.

I will update both spring-projects/spring-boot#26258 and micrometer-metrics/micrometer-docs#160 as soon as this is merged.

@jonatan-ivanov jonatan-ivanov added registry: dynatrace A Dynatrace Registry related issue type: task A general task labels Jul 8, 2021
@jonatan-ivanov jonatan-ivanov added this to the 1.8.0-M1 milestone Jul 8, 2021
@@ -71,7 +71,7 @@ public DynatraceExporterV2(DynatraceConfig config, Clock clock, HttpSender httpC
.withPrefix(config.metricKeyPrefix())
.withDefaultDimensions(parseDefaultDimensions(config.defaultDimensions()));

if (config.enrichWithOneAgentMetadata()) {
if (config.enrichWithDynatraceMetadata()) {
Copy link
Member

Choose a reason for hiding this comment

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

Do you also want to replace this (line#94)?

Potential misconfiguration detected: Token is provided, but the endpoint is set to the local OneAgent endpoint,

@@ -117,7 +117,7 @@ void testV2Defaults() {
assertThat(config.uri()).isSameAs(DynatraceMetricApiConstants.getDefaultOneAgentEndpoint());
assertThat(config.metricKeyPrefix()).isEmpty();
assertThat(config.defaultDimensions()).isEmpty();
assertThat(config.enrichWithOneAgentMetadata()).isTrue();
assertThat(config.enrichWithDynatraceMetadata()).isTrue();
Copy link
Member

Choose a reason for hiding this comment

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

Do you also want to rename testOneAgentEndpointWithDifferentPort?

@pirgeo
Copy link
Contributor Author

pirgeo commented Jul 9, 2021

Thanks for taking a look! There are two different features here which happen to have similar names:

  • The metadata enrichment, which we renamed in this PR, does not only work with the OneAgent but also with other metadata sources (hence the renaming).
  • The local OneAgent endpoint requires a OneAgent, therefore the wording stayed the same for this component.

@jonatan-ivanov jonatan-ivanov merged commit 61aabb2 into micrometer-metrics:main Jul 9, 2021
@jonatan-ivanov
Copy link
Member

@pirgeo Makes sense, thank you for the fix! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
registry: dynatrace A Dynatrace Registry related issue type: task A general task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants