jar package is a binary file, which is not convenient to mount via ConfigMap, so it is recommended to package the JMX Exporter jar package and configuration file into the business container image directly. The JMX Exporter jar package and configuration file should be specified when starting the JVM using the in-process method. Steps Expose JVM monitoring metrics using JMX Exporter This article takes the JVM in-process startup (in-process) approach as an example, using JMX Exporter to expose JVM monitoring metrics in a Kubernetes environment. Officially, it is not recommended to use the start independent process approach, which is complex to configure and requires a separate process, and the monitoring of the process itself raises new issues. Specify the parameters when the JVM starts, run the JMX Exporter jar package as a javaagent, read the JVM runtime state data in-process, convert it to Prometheus metrics format, and expose the port for Prometheus to collect. JMX Exporter calls RMI to get JVM runtime state data, converts it to Prometheus metrics format, and exposes the port for Prometheus to collect. JMX Exporter provides two ways to expose JVM monitoring metrics, starting a standalone process and in-process (in-process) JVM. JMX Exporter uses Java’s JMX mechanism to read JVM runtime monitoring data and convert it to Prometheus-aware metrics format so that Prometheus can monitor and collect it. Java Management Extensions, JMX, is an extension framework for managing Java, and JMX Exporter is based on this framework for reading the runtime state of the JVM. Learn how to use Prometheus with JMX Exporter to monitor Java applications once your Java business has been containerized to Kubernetes in this article. The Prometheus community has developed the JMX Exporter to export JVM monitoring metrics for use with Prometheus to capture monitoring data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |