-
Notifications
You must be signed in to change notification settings - Fork 1k
Graphite tag support #1806
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
Merged
Merged
Graphite tag support #1806
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fitzoh
commented
Jan 18, 2020
...micrometer-registry-graphite/src/main/java/io/micrometer/graphite/GraphiteTagNameMapper.java
Outdated
Show resolved
Hide resolved
fitzoh
commented
Jan 18, 2020
...ometer-registry-graphite/src/test/java/io/micrometer/graphite/GraphiteTagNameMapperTest.java
Outdated
Show resolved
Hide resolved
fitzoh
commented
Jan 18, 2020
...micrometer-registry-graphite/src/main/java/io/micrometer/graphite/GraphiteTagNameMapper.java
Outdated
Show resolved
Hide resolved
fitzoh
commented
Jan 18, 2020
...ometer-registry-graphite/src/test/java/io/micrometer/graphite/GraphiteTagNameMapperTest.java
Outdated
Show resolved
Hide resolved
jkschneider
reviewed
Jan 25, 2020
...ometer-registry-graphite/src/test/java/io/micrometer/graphite/GraphiteTagNameMapperTest.java
Outdated
Show resolved
Hide resolved
...ometer-registry-graphite/src/test/java/io/micrometer/graphite/GraphiteTagNameMapperTest.java
Outdated
Show resolved
Hide resolved
...micrometer-registry-graphite/src/main/java/io/micrometer/graphite/GraphiteTagNameMapper.java
Outdated
Show resolved
Hide resolved
...micrometer-registry-graphite/src/main/java/io/micrometer/graphite/GraphiteTagNameMapper.java
Outdated
Show resolved
Hide resolved
...micrometer-registry-graphite/src/main/java/io/micrometer/graphite/GraphiteTagNameMapper.java
Outdated
Show resolved
Hide resolved
fitzoh
commented
Jan 25, 2020
...ometer-registry-graphite/src/test/java/io/micrometer/graphite/GraphiteTagNameMapperTest.java
Outdated
Show resolved
Hide resolved
fitzoh
commented
Jan 25, 2020
...ometer-registry-graphite/src/test/java/io/micrometer/graphite/GraphiteTagNameMapperTest.java
Outdated
Show resolved
Hide resolved
… handled by the naming convention tests)
jkschneider
suggested changes
Jan 26, 2020
...istry-graphite/src/main/java/io/micrometer/graphite/GraphiteDimensionalNamingConvention.java
Outdated
Show resolved
Hide resolved
Thanks for the cool feature @fitzoh! |
This PR seems broken, it always generate broken names due to DropWizard behavior. From DropWizard, GraphiteReporter [1]: final string sent to graphite: "my.metric;tag=valuep99" Unless we patch DropWizard side i can't see how this code may work |
j-sandy
added a commit
to j-sandy/kayenta
that referenced
this pull request
Sep 12, 2022
…g-boot to 2.3.12 While upgrading the spring-boot by transitively upgrading the orca version in kayenta and enforcing the dependencies, the kayenta-integration-tests:GraphiteStandaloneCanaryAnalysisTest failed with below error: ``` java.lang.AssertionError: 1 expectation failed. JSON path executionStatus doesn't match. Expected: is "SUCCEEDED" Actual: TERMINAL at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:72) at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:59) at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:277) at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:493) at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source) at io.restassured.internal.ResponseSpecificationImpl.validateResponseIfRequired(ResponseSpecificationImpl.groovy:674) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAcc ``` The root cause for this issue is upgrade of io.micrometer:micrometer-registry-graphite from 1.3.16 to 1.5.14 as transitive dependency of spring-boot. In the newer version of micrometer-registry-graphite, there is addition of native Graphite tag support and making it as default behaviour from 1.4+ version. Now the legacy hierarchical tag names need to be explicitly enabled by disabling native graphite support. https://github.com/micrometer-metrics/micrometer/releases/tag/v1.4.0 micrometer-metrics/micrometer#1806 Based on the discussions [here](micrometer-metrics/micrometer-docs#123) spring-boot has also exposed the property to disable the native graphite tag support, and implemented in 2.3.x [here](spring-projects/spring-boot#20834). To fix this issue, explicitly specifying this property `management.metrics.export.graphite.graphite-tags-enabled=false` in test environment and in kayenta config.
mergify bot
pushed a commit
to spinnaker/kayenta
that referenced
this pull request
Sep 12, 2022
…g-boot to 2.3.12 (#909) While upgrading the spring-boot by transitively upgrading the orca version in kayenta and enforcing the dependencies, the kayenta-integration-tests:GraphiteStandaloneCanaryAnalysisTest failed with below error: ``` java.lang.AssertionError: 1 expectation failed. JSON path executionStatus doesn't match. Expected: is "SUCCEEDED" Actual: TERMINAL at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:72) at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:59) at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:277) at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:493) at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source) at io.restassured.internal.ResponseSpecificationImpl.validateResponseIfRequired(ResponseSpecificationImpl.groovy:674) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAcc ``` The root cause for this issue is upgrade of io.micrometer:micrometer-registry-graphite from 1.3.16 to 1.5.14 as transitive dependency of spring-boot. In the newer version of micrometer-registry-graphite, there is addition of native Graphite tag support and making it as default behaviour from 1.4+ version. Now the legacy hierarchical tag names need to be explicitly enabled by disabling native graphite support. https://github.com/micrometer-metrics/micrometer/releases/tag/v1.4.0 micrometer-metrics/micrometer#1806 Based on the discussions [here](micrometer-metrics/micrometer-docs#123) spring-boot has also exposed the property to disable the native graphite tag support, and implemented in 2.3.x [here](spring-projects/spring-boot#20834). To fix this issue, explicitly specifying this property `management.metrics.export.graphite.graphite-tags-enabled=false` in test environment and in kayenta config.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
registry: graphite
A Graphite Registry related issue
release notes
Noteworthy change to call out in the release notes
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Super JankyQuite reasonable (@jkschneider edit) support for #491.Adds an alternative dimensional name mapper and naming convention for graphite that supports tagging.