I found that Dynatrace added support for Netflix OSS monitoring. But there no enough details about it. In the setting I see that it is a JMX monitoring. I configured JMX for one my service and export servo metrics to it but still don't see any details in Dynatrace.
So can you please provide more details information about how Netflix OSS monitoring is supported and what required from me in order to make it work?
Sorry for the inconvenience.
Any Java process that exports Hystrix or Eureka metrics should automatically expose that information to Dynatrace.
For viewing them, please go to the process screen of the according Java process (it's important to be on the process screen, not the service screen). There you should find a button labeled "Further metrics" just below the infographic which will bring you to the screen that's also shown on the website, containing the metrics you're looking for.
If that doesn't work, please let us know.
Thanks for answer.
I am using Spring Cloud Netflix component and by default it does not export Netflix OSS metrics. It happens because by default it use BasicMonitorRegistry which does not export anything. It is required to replace it with JmxMonitorRegistry by using the following configuration property:
After that changes and configuration of JMX I can see Hystrix and Eureka metrics. But article also mention a support for Zuul monitoring. Where it can be found?
Ok, it makes sense now to me. So, you're not running on a Servlet container, right?
Tomcat, Jetty, and all the other containers should automatically export the metrics (including Spring Boot).
Zuul support is not working right now, unfortunately, as it exports its data in a different way. Sorry for the inconvenience, I will make sure that the website is not misleading here anymore.
Once we have Zuul monitoring working, I will let you know.
Hi Alexander -
Do you remember the version of the Springboot app and Servo-Core jar that you had used when you came across this problem and solved it?
We have similar setup and when we tried to expose the mbeans as you have mentioned we are always getting initialization error with constructor.
2017-08-15 15:54:01.811 ERROR 2761 --- [ost-startStop-1] c.netflix.servo.DefaultMonitorRegistry : failed to create instance of class com.netflix.servo.jmx.JmxMonitorRegistry, using default class com.netflix.servo.jmx.JmxMonitorRegistry
at java.lang.Class.newInstance(Class.java:427) ~[na:1.8.0_77]
at com.netflix.servo.DefaultMonitorRegistry.<init>(DefaultMonitorRegistry.java:79) [servo-core-0.10.1.jar:0.10.1]