I am building a Spring Boot 2.2.1.RELEASE application and using Micrometer, Actuator and DynatraceMetricsRegistry for piping custom metrics, JVM and HTTP metrics into Dynatrace . But this is not working as expected in Dynatrace.
I get the following errors as per the polling interval configured in the application.properties for Dynatrace :
Log Excerpt :
2020-02-06 02:21:06.234 ERROR 64357 --- [trics-publisher] i.m.dynatrace.DynatraceMeterRegistry : failed to create custom metric custom:jvm.threads.states in dynatrace: {“error”:{“code”:400,“message”:“The dimensions of an already configured timeseries id cannot be changed. Currently configured dimensions are: jvm.threads.states”}}
2020-02-06 02:21:06.634 ERROR 64357 --- [trics-publisher] i.m.dynatrace.DynatraceMeterRegistry : failed to create custom metric custom:http.server.requests.count in dynatrace: {“error”:{“code”:400,“message”:"The dimensions of an already configured timeseries id cannot be changed. Currently configured dimensions are: coffee"}}
2020-02-06 02:21:06.973 ERROR 64357 --- [trics-publisher] i.m.dynatrace.DynatraceMeterRegistry : failed to create custom metric custom:http.server.requests.max in dynatrace: {“error”:{“code”:400,“message”:“The dimensions of an already configured timeseries id cannot be changed. Currently configured dimensions are: coffee”}}
…
…
2020-02-06 02:21:09.997 ERROR 64357 --- [trics-publisher] i.m.dynatrace.DynatraceMeterRegistry : failed to send metrics to dynatrace: {“error”:{“code”:400,“message”:“Constraints violated.”,“constraintViolations”:[{“path”:“series[20].dimensions”,“message”:“Dimensions don’t match dimensions specified in configuration. Allowed extra dimensions from the configuration are: jvm.gc.memory.allocated”,“parameterLocation”:“PAYLOAD_BODY”,“location”:null}]}}
I have created a custom device under the technologies section in Dynatrace and no metrics are getting captured in the dynatrace dashboard. Please help .
My application.properties are :
management.endpoints.web.exposure.include=health,info
Although the below ones are obfuscated they are correct and worked when I tested this using a REST client tool :
management.metrics.export.dynatrace.api-token=XXXXXX
management.metrics.export.dynatrace.uri=https://XXXXXX.live.dynatrace.com
management.metrics.export.dynatrace.device-id=XXXXXX
management.metrics.export.dynatrace.enabled=true
management.metrics.export.dynatrace.group=XXXXXX
management.metrics.export.dynatrace.step=1m