maixiaohai commented on issue #2257:
URL: https://github.com/apache/rocketmq/issues/2257#issuecomment-675984832


   > > for developer use
   > > https://juejin.im/post/6844903655456374792
   > 
   > > for exporting metrics to monitoring systems
   > > https://www.datadoghq.com/blog/java-runtime-monitoring-with-jvm-metrics/
   > > https://segmentfault.com/a/1190000016791460
   > 
   > If we just need JVM metrics, we can export JVM metrics without making any 
modifications to the code (and we shouldn't. Apparently JVM metrics should be 
available for every Java application, and it would be so awkward if we need to 
write metrics code for every java application if we want to export metrics).
   > 
   > However, if we want to add some Rocketmq-specific metrics via JMX, this 
would be ok. We can create some metrics beans to JMX agent and other monitoring 
tools like datadog or Prometheus would create their own JMX exporters to 
collect metrics.
   > 
   > In your case I think you can collect JVM metrics already, either by using 
j-something command line tools (which is pretty much the standard way to 
monitor JVM) or using some monitoring tool like dd or prometheus.
   
   Thanks for you reply. It help a lot.
   Actually, we found jmx_exporter is very useful.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to