CN116302833A - Data monitoring method and device of JAVA virtual machine, computer equipment and storage medium - Google Patents

Abstract

The invention provides a data monitoring method and device of a JAVA virtual machine, computer equipment and storage medium, wherein the method comprises the following steps: configuring a plug-in for docking Prometheus in a target application of the micro-service cluster, and configuring a monitoring function module for the application, wherein the monitoring function module is used for discovering each monitoring index interface configured by the monitoring function module and used for monitoring the target application; writing an operation and maintenance feature description configuration file of the target application, wherein the operation and maintenance feature description configuration file comprises application feature information writing in metadata of the service, so that Prometheus automatically discovers the target application, and each monitoring index interface configured by a monitoring function module of the target application is discovered; adding a real-time monitoring class library of the target item in the Prometaus configuration file; and configuring application characteristic information to be dynamically discovered by Prometheus; prometaus address information is configured for Grafana so that Prometaus is connected with Grafana; and checking the JAVA virtual machine state of the target application of the configured micro service cluster through Prometaus.

Description

Data monitoring method and device of JAVA virtual machine, computer equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for monitoring data of a JAVA virtual machine, a computer device, and a storage medium.

Background

In the container orchestration engine Kubernetes environment, applications run across multiple nodes within a cluster, while services will also be distributed across multiple clusters or multiple cloud vendors, which makes tracking, monitoring the health of these applications and the infrastructure they rely on very challenging. In such an environment, prometheus has grown in concert to support Kubernetes, as the best monitoring tool for container scenarios.

In a production environment, the stability of a system is an important basic stone for maintaining business stability, and the running state of the JVM directly relates to the stability of the system. Providing scientific and reliable clues for the examination questions and combining the monitoring data of the JVM can optimize the functions and the performance of the application program to a certain extent.

There are many types of monitoring methods for the current micro-service JVM, including jmxexporter, springbootadmin, jvisualvm, jstatd, kubernetesservice, but these methods are not suitable for JAVA virtual machine monitoring in the field of cloud protogenesis, or are cumbersome to use, mainly because:

(1) The monitored objects are usually small, and the configuration is complex or the operation is troublesome when the data is too much;

(2) The monitored objects are typically static and are typically accessible via a fixed address;

(3) jmx it is necessary to mount jar of a specific directory in a container environment, then set jar paths in operation parameters, deployment is difficult in the container environment, and fault migration is also relatively difficult;

(4) The monitored targets cannot be found in a dynamic batch mode, and the target addresses need to be added in a static mode in Prometaus;

(5) The microservices in Kubernetes are running in Pod, which has erratic characteristics and therefore cannot fix the monitoring address to which the application is exposed.

Kubernetesservice is a relatively good way to pull JVM data in a fixed manner. However, the dynamic discovery capability is lacking, the target address needs to be statically added in Prometaus every time a service is added, and after a new service is added, the new service cannot be dynamically discovered by Prometaus, and thus the newly added application target JVM cannot be monitored, and the monitoring of a micro-service cluster in the Kubernetes environment faces little difficulty and challenges.

Disclosure of Invention

In order to overcome the technical defects, the invention aims to provide a data monitoring method, equipment, computer equipment and storage medium for a JAVA virtual machine, which are used for realizing simple and efficient monitoring of a micro service cluster based on the characteristics of cloud protogenesis, thereby reducing the use cost and improving the operation efficiency.

The invention discloses a data monitoring method of a JAVA virtual machine of a micro-service cluster, which comprises the following steps: configuring a plug-in for interfacing with a monitoring module in a target application of a micro-service cluster, and configuring a monitoring function module for the application, wherein the monitoring module is used for finding out all monitoring index interfaces configured by the monitoring function module and used for monitoring the target application; writing an operation and maintenance feature description configuration file of the target application, wherein the operation and maintenance feature description configuration file comprises application feature information writing in metadata of a service, so that the monitoring module automatically discovers the target application, and each monitoring index interface configured by the monitoring function module of the target application is discovered; adding a real-time monitoring class library of a target item in the monitoring module configuration file; the application characteristic information to be dynamically found by the monitoring module is configured; configuring the monitoring module address information for a monitoring display module, so that the monitoring module is connected with the monitoring display module; and configuring a JAVA virtual machine template in the monitoring display module, so that the JAVA virtual machine state of the target application of the configured micro service cluster is checked through the monitoring module, wherein the JAVA virtual machine state comprises various monitoring indexes provided by the various monitoring index interfaces.

Preferably, the real-time monitoring class library of the target item is added in the monitoring module configuration file; after the application characteristic information to be dynamically discovered by the monitoring module is configured, the method comprises the following steps: and the monitoring module reloads the configuration file.

Preferably, the monitoring function module includes a monitoring function unit.

Preferably, after configuring a plug-in for interfacing with the monitoring module in the target application of the micro service cluster and configuring a monitoring function module for an application, the method further includes: integrating a service discovery and registration module in the target application of the micro service cluster, and constructing a mirror image of the target application.

Preferably, the service discovery and registration module includes a first service registry, a second service registry, and a third service registry.

Preferably, the application characteristic information includes one or more of application type, port number, interface of the docked monitoring module, service rule, service name space, and application service name in metadata of the service.

Preferably, the method further comprises: and modifying the application characteristic information in the operation and maintenance characteristic description configuration file of the target application and modifying the application characteristic information of the monitoring module, so that the data dynamic monitoring of the JAVA virtual machine of the micro-service cluster is realized.

The invention also discloses a data monitoring system of the JAVA virtual machine of the micro service cluster, which comprises the micro service cluster, a monitoring module, a service discovery and registration module and a monitoring display module; configuring a plug-in for interfacing with a monitoring module in a target application of the micro service cluster, and configuring a monitoring function module for the application, wherein the monitoring module is used for finding each monitoring index interface configured by the monitoring function module and used for monitoring the target application; writing an operation and maintenance feature description configuration file of the target application, wherein the operation and maintenance feature description configuration file comprises application feature information writing in metadata of a service, so that the monitoring module automatically discovers the target application, and each monitoring index interface configured by the monitoring function module of the target application is discovered; integrating the service discovery and registration module in the target application of the micro service cluster, and constructing a mirror image of the target application; the service discovery and registration module comprises a first service registration center, a second service registration center and a third service registration center; adding a real-time monitoring class library of a target item in a configuration file of the monitoring module; the application characteristic information to be dynamically found by the monitoring module is configured; configuring the monitoring module address information for the monitoring display module so that the monitoring module is connected with the monitoring display module; and configuring a JAVA virtual machine template in a monitoring display module, so that the JAVA virtual machine state of the target application of the configured micro service cluster is checked through the monitoring module, wherein the JAVA virtual machine state comprises various monitoring indexes provided by the various monitoring index interfaces.

The invention also discloses a computer device, which comprises: a memory and a processor; the memory is used for storing computer instructions; the processor executes computer instructions to implement the method of any of the above.

The invention also discloses a computer readable storage medium storing computer instructions which when executed perform the method of any of the above.

After the technical scheme is adopted, compared with the prior art, the method has the following beneficial effects:

1. the invention can more efficiently realize the monitoring of the running state of the JAVA virtual machine of the large-scale micro service under the Kubernetes, enables Prometaus to dynamically acquire the address change condition of a monitoring target by introducing a simple dynamic discovery mechanism, can realize batch discovery, dynamic discovery and large-scale access, and realizes the state monitoring of the micro service JAVA virtual machine of the cloud primary environment more simply and efficiently as the deployed nodes are more in number and the service scale is larger and the corresponding maintenance cost is lower.

Drawings

Fig. 1 is a flowchart of a data monitoring method of JAVA virtual machines of a micro service cluster provided by the present invention;

fig. 2 is a schematic block diagram of a data monitoring system of a JAVA virtual machine of a micro service cluster according to the present invention.

Detailed Description

Advantages of the invention are further illustrated in the following description, taken in conjunction with the accompanying drawings and detailed description.

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

In the description of the present invention, it should be understood that the terms "longitudinal," "transverse," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," and the like indicate orientations or positional relationships based on the orientation or positional relationships shown in the drawings, merely to facilitate describing the present invention and simplify the description, and do not indicate or imply that the devices or elements referred to must have a specific orientation, be configured and operated in a specific orientation, and therefore should not be construed as limiting the present invention.

In the description of the present invention, unless otherwise specified and defined, it should be noted that the terms "mounted," "connected," and "coupled" are to be construed broadly, and may be, for example, mechanical or electrical, or may be in communication with each other between two elements, directly or indirectly through intermediaries, as would be understood by those skilled in the art, in view of the specific meaning of the terms described above.

In the following description, suffixes such as "module", "component", or "unit" for representing elements are used only for facilitating the description of the present invention, and are not of specific significance per se. Thus, "module" and "component" may be used in combination.

Representative techniques for cloud protogenesis described herein include containers, service grids, micro-services, immutable infrastructure, and declarative APIs. Cloud native applications are applications that fit the cloud computing features, yun Yuansheng applications were designed from the beginning to run in the cloud, whether private or public. Three major features of cloud native applications: containerized, dynamically managed and microservices. (1) containerized packaging: based on the container, the overall development level is improved, code and component reuse is formed, maintenance of the cloud native application program is simplified, the application program and the process are operated in the container and used as independent units for application program deployment, and high-level resource isolation is realized; (2) dynamic management: dynamically managing and scheduling by a centralized scheduling system; (3) micro-service oriented: the dependencies between services are defined and decoupled from each other.

Microservices (Microservices) is an architectural style, a large complex software application consisting of one or more Microservices. The micro services in the system can be deployed independently, with loose coupling between the micro services. Each micro-service is focused on completing only one task and performing that task well. In all cases, each task represents a small business capability.

The container is a standardized, stand-alone software package that contains all the necessary elements and can be run anywhere without customization, including application code and supporting libraries. The container is similar to a virtual machine, one process can be virtualized into one container, deployment of applications can be carried, a simple isolation mechanism is provided, and efficient resource utilization and rapid packaging and deployment can be achieved.

As containerized applications become more complex, developers need tools that can coordinate interactions between containers running on different virtual machines, and even on different physical machines. Such tools are known as container orchestration platforms, and Kubernetes is a type of container orchestration platform. Kubernetes can work with any container that meets the Open Container Initiative (OCI) image specification, which is met by the container of Podman. Kubernetes is an open source for managing containerized applications on multiple hosts in a cloud platform, and the goal of Kubernetes is to make deploying containerized applications simple and efficient, and Kubernetes provides a mechanism for application deployment, planning, updating, and maintenance. Vividly, kubernetes can be understood as a centralized bin integrated vehicle. Kubernetes is a cloud-native cornerstone, and with the rapid development of cloud-native architecture container orchestration engine modules, more and more companies, teams, deploy services in a containerized form on cloud-native architecture k8s clusters.

Pod is the smallest unit that can be created and managed in the Kubernetes system, and multiple application services can be deployed in one Pod. Typically a service that a user runs within a cluster may be abstracted to Pod. Pod is the basic execution unit, also called service work unit, of a cloud native architecture container orchestration engine module application, which is the smallest and simplest unit created or deployed in a cloud native architecture container orchestration engine module object model, pod representing a process running on a cluster. Pod and other container orchestration engine module resources are typically created by providing JSON or YAML files to container orchestration engine module RESTAPI. For example, a Pod may be created using a nginx mirror.

Service defines a logical grouping of Pod, a policy that can access them, for discovering Pod and load balancing of Pod.

The JVM is a specification for a computing device, which is a fictitious computer implemented by emulating various computer functions on an actual computer, and is an operating virtual machine in JAVA language. The JAVA virtual machine in the present invention refers to (but is not limited to) JVM.

Prometaus is an open source service monitoring system and time series database for monitoring the operational status of the respective systems.

The invention introduces a simple dynamic discovery mechanism to enable Prometheus to dynamically acquire the address change condition of a monitoring target, and concretely, referring to fig. 1, a JVM data monitoring method of a micro-service cluster comprises the following steps:

s100, configuring a plug-in for interfacing with a monitoring module in a target application of a micro-service cluster, and configuring a monitoring function module for the application, wherein the monitoring module is used for finding all monitoring index interfaces configured by the monitoring function module and used for monitoring the target application;

s200, compiling an operation and maintenance feature description configuration file of the target application, wherein the operation and maintenance feature description configuration file comprises application feature information writing in metadata of the service, so that the monitoring module automatically discovers the target application, and each monitoring index interface configured by a monitoring function module of the target application is discovered;

s300, adding a real-time monitoring class library of a target item in a monitoring module configuration file;

s400, configuring application characteristic information to be dynamically discovered by the monitoring module;

s500, configuring monitoring module address information for the monitoring display module so that the monitoring module is connected with the monitoring display module;

s600, configuring a JVM template in the monitoring display module, so that the JVM state of the target application of the configured micro-service cluster is checked through the monitoring module, wherein the JVM state comprises various monitoring indexes provided by various monitoring index interfaces.

It should be noted that, the target application of the present invention is a part or all of the micro-service cluster, the monitoring module mainly refers to promethaus, the service mainly refers to service, and the monitoring display module mainly refers to Grafana monitoring large screen, but the protection scope of the present invention is not limited thereto.

The solution of the invention can be understood to comprise three main phases: an application tuning phase, a Prometheus configuration phase and a Grafana monitor large screen configuration phase. Wherein steps S100-S200 belong to the application adjustment phase, S300-S400 belong to the Prometaus configuration phase, and S500-S600 belong to the Grafana monitoring large screen configuration phase.

In some embodiments, the plug-in for interfacing with the monitoring module (e.g., prometaus) is typically a micrometer plug-in, which is not limited herein. In some embodiments, the monitoring function is preferably an actuator for exposing a monitoring index interface of the target application for promethaus discovery. By introducing a plug-in (such as a micrometer plug-in) for docking Prometaus into the target application and adding application monitoring dependence (such as an actuator) into the target application, the Prometaus can accurately access the target application and acquire data of a monitoring index interface of the target application, so that the target application is monitored.

For step S100, the monitoring indicator interface is configured to monitor real-time status parameters of the running target application, and indicators that the monitoring indicator interface may monitor include, but are not limited to, one or more of CPU usage, open file count, system load, heap memory pool, GC count, connection count, etc., and in some embodiments, the monitoring indicator interface may include a health check interface (e.g., configured to monitor whether the current status of the target application is healthy, etc.), although not limited thereto. When the application monitoring dependency (such as a executor) is increased, further, endpoint exposure is required, and the monitoring index interface of the target application is exposed by configuring the exposure range of the monitoring index interface, the exposed service name and the like. In some embodiments, endpoint exposure includes the following flow: (1) configuring an endpoint: in a SpringBoot application, management. For example, all Web endpoints may be opened by setting management. (2) registering the endpoint: the SpringBoot application will automatically register all open endpoints in one manager. A manager is a collection that maintains all registered endpoints. (3) endpoint access: the SpringBoot application will generate a URL address for each registered endpoint. By accessing this URL address, the functionality of the endpoint may be accessed. For example, health information of an application may be obtained by accessing/actor/health. (4) security configuration: by default, the SpringBoot endpoint does not require authentication. However, it is possible to control which endpoints should be open and which should be closed by configuring the management. Meanwhile, the SpringSecurity may be used to configure authentication and authorization for endpoints.

After the monitoring index interface (such as the health check interface) is configured and exposed, a service discovery and registration module is integrated in the target application of the micro service cluster, and a mirror image of the target application is constructed. The service discovery and registration module is preferably an ETCD registry, which is implemented based on go language, and is mainly used for sharing components for configuration and service discovery, and is a component for providing strong consistency and high availability in a distributed system, and is used for storing a small amount of important data. Of course, the service discovery and registration module may be another service discovery and registration module such as a nacos or eurka, which is not limited herein.

And for the step S200, writing an operation and maintenance feature description configuration file of the target application, and writing application feature information so that the monitoring module automatically discovers the target application, thereby discovering all monitoring index interfaces configured by a monitoring function module of the target application. In some embodiments, writing the operation and maintenance feature description configuration file may be adding application feature information in an announcements in metadata (metadata) of a service (service), where the application feature information includes one or more of an application type, a port number, an interface of a docked Prometaus, a service rule, a service namespace, an application service name(s), and so forth, and provides for auto discovery. In some embodiments, the operation and maintenance profile may be an app.yaml format file, not limited herein.

After steps S100 and S200 are completed, the target application may then be deployed into the Kubernetes cluster, with the application tuning phase completed. Prometaus configuration is then performed.

For step S300, a real-time monitoring class library of target items is added to the profile of promethaus, and in some embodiments, the target items may be spring items, and the real-time monitoring class library may be metrics, which is only used as an example and not as a limitation. Optionally, the job_ name, kubernetes _sd_configs information is also required to be configured next.

For step S400, application feature information to be dynamically discovered by promethaus is configured, the application feature information including (and not limited to) one or more of an application type in metadata (metadata) of a service (service), a port number, an interface of the docked promethaus, a service rule, a service namespace, and an application service name. It should be understood that the application feature information in the operation and maintenance feature description configuration file of the application targeted for carrying the monitoring data and the application feature information to be dynamically discovered by configuring Prometaus are one or more of application type, port number, interface of the docked monitoring module, service rule, service naming space, application service name. When the operation and maintenance feature description configuration file of the target application is matched with the application feature information to be dynamically discovered by configuring Prometaus, the Prometaus can discover the target application to be monitored.

After the application feature information to be dynamically discovered by Prometaus is configured in step S400, prometaus reloads the configuration file and the loaded target can be seen at the console.

Therefore, the application and the Prometheus monitoring end are configured, and the Grafana monitoring large screen configuration is entered to display the monitoring information in the Grafana monitoring large screen. Specifically, prometaus is connected, prometaus address information is configured, then JVM monitoring templates are configured, corresponding templates are found in Grafana official websites for downloading, grafana templates are imported, and JVM states of related services are checked. The JVM state of the target application of the micro-service cluster configured by promethaus can be seen on Grafana, and the JVM state includes the above monitoring indicators (e.g., monitoring indicators of whether the target application is healthy, JVM memory information occupied by the target application, open file count, system load, heap memory pool, GC count, connection count, etc.).

And after the application characteristic information in the operation and maintenance characteristic description configuration file of the target application and the application characteristic information in the configuration file of Prometaus are modified, another batch of different application characteristic information can be monitored, so that the JVM state is monitored in a large batch and dynamically.

Furthermore, the exposed monitoring index interface is changed, so that monitoring of different application characteristic information can be realized.

The invention mainly introduces plug-in dependence (e.g. actuator) and endpoint exposure in the target application, and modifies the tasks information in metadata of the service in the operation and maintenance feature description configuration file of the target application, and only needs to modify relevant configuration according to the application feature information for the Prometaus configuration part, so that the dynamic, batched and large-scale micro-service cluster JVM operation data can be accessed to the Prometaus monitoring system efficiently and conveniently.

Referring to fig. 2, the invention also discloses a data monitoring system of the JVM of the micro service cluster, which comprises the micro service cluster (application a, application B), prometheus, ETCD registry and Grafana.

Configuring a micrometer plug-in for docking Prometaus in a target application of the micro-service cluster, and adding an application monitoring dependency actuator for the Prometaus to find each monitoring index interface configured by the actuator for monitoring the target application; writing an operation and maintenance feature description configuration file of the target application, wherein the operation and maintenance feature description configuration file comprises application feature information writing in the announcements in the metadata of the service, so that Prometaus automatically discovers the target application, and each monitoring index interface configured by the actuator of the target application is discovered; integrating an ETCD registry in the target application of the micro service cluster, and constructing a mirror image of the target application.

Adding a real-time monitoring class library (e.g., metrics) of target items (e.g., spring items) in a profile of Prometaus; and configures application feature information to be dynamically discovered by Prometheus.

Prometaus address information is configured for Grafana so that Prometaus is connected with Grafana; the JVM template is configured in Grafana so that the JVM state of the target application of the configured micro-service cluster is viewed through promethaus, the JVM state including the monitor metrics provided by the monitor metrics interfaces.

The invention also discloses a computer device, which comprises: a memory and a processor; the memory is used for storing computer instructions; the processor executes computer instructions to implement the method of any of the above.

The invention also discloses a computer readable storage medium storing computer instructions that when executed perform the method of any of the above.

It should be noted that the embodiments of the present invention are preferred and not limited in any way, and any person skilled in the art may make use of the above-disclosed technical content to change or modify the same into equivalent effective embodiments without departing from the technical scope of the present invention, and any modifications or equivalent changes and modifications to the above-described embodiments according to the technical substance of the present invention still fall within the scope of the technical scope of the present invention.

Claims (10)

1. The data monitoring method of the JAVA virtual machine of the micro service cluster is characterized by comprising the following steps of:

configuring a plug-in for interfacing with a monitoring module in a target application of a micro-service cluster, and configuring a monitoring function module for the application, wherein the monitoring module is used for finding out all monitoring index interfaces configured by the monitoring function module and used for monitoring the target application;

writing an operation and maintenance feature description configuration file of the target application, wherein the operation and maintenance feature description configuration file comprises application feature information writing in metadata of a service, so that the monitoring module automatically discovers the target application, and each monitoring index interface configured by the monitoring function module of the target application is discovered;

adding a real-time monitoring class library of a target item in the monitoring module configuration file; the application characteristic information to be dynamically found by the monitoring module is configured;

configuring the monitoring module address information for a monitoring display module, so that the monitoring module is connected with the monitoring display module; and configuring a JAVA virtual machine template in the monitoring display module, so that the JAVA virtual machine state of the target application of the configured micro service cluster is checked through the monitoring module, wherein the JAVA virtual machine state comprises various monitoring indexes provided by the various monitoring index interfaces.

2. The method for monitoring data of JAVA virtual machines of a micro service cluster according to claim 1, wherein a real-time monitoring class library of target items is added in the monitoring module configuration file; after the application characteristic information to be dynamically discovered by the monitoring module is configured, the method comprises the following steps:

and the monitoring module reloads the configuration file.

3. The method for monitoring data of JAVA virtual machines of a micro service cluster according to claim 1, wherein the monitoring function module comprises a monitoring function unit.

4. The method for monitoring data of JAVA virtual machines in a micro service cluster according to claim 1, wherein after configuring a plug-in for interfacing with the monitoring module in the target application in the micro service cluster and configuring a monitoring function module for an application, the method further comprises:

integrating a service discovery and registration module in the target application of the micro service cluster, and constructing a mirror image of the target application.

5. The method for monitoring data of JAVA virtual machines of a micro service cluster according to claim 4, wherein the service discovery and registration module comprises a first service registry, a second service registry, and a third service registry.

6. The method for monitoring data of JAVA virtual machines of a micro service cluster according to claim 1, wherein the application characteristic information includes one or more of application type, port number, interface of the docked monitoring module, service rule, service namespace, application service name in metadata of the service.

7. The method for monitoring data of JAVA virtual machines of a micro service cluster according to claim 1, further comprising:

and modifying the application characteristic information in the operation and maintenance characteristic description configuration file of the target application and modifying the application characteristic information of the monitoring module, so that the data dynamic monitoring of the JAVA virtual machine of the micro-service cluster is realized.

8. The data monitoring system of the JAVA virtual machine of the micro service cluster is characterized by comprising the micro service cluster, a monitoring module, a service discovery and registration module and a monitoring display module;

configuring a plug-in for interfacing with a monitoring module in a target application of the micro service cluster, and configuring a monitoring function module for the application, wherein the monitoring module is used for finding each monitoring index interface configured by the monitoring function module and used for monitoring the target application; writing an operation and maintenance feature description configuration file of the target application, wherein the operation and maintenance feature description configuration file comprises application feature information writing in metadata of a service, so that the monitoring module automatically discovers the target application, and each monitoring index interface configured by the monitoring function module of the target application is discovered;

integrating the service discovery and registration module in the target application of the micro service cluster, and constructing a mirror image of the target application; the service discovery and registration module comprises a first service registration center, a second service registration center and a third service registration center;

adding a real-time monitoring class library of a target item in a configuration file of the monitoring module; the application characteristic information to be dynamically found by the monitoring module is configured;

configuring the monitoring module address information for the monitoring display module so that the monitoring module is connected with the monitoring display module; and configuring a JAVA virtual machine template in a monitoring display module, so that the JAVA virtual machine state of the target application of the configured micro service cluster is checked through the monitoring module, wherein the JAVA virtual machine state comprises various monitoring indexes provided by the various monitoring index interfaces.

9. A computer device, the device comprising: a memory and a processor; the memory is used for storing computer instructions; the processor executing computer instructions to implement the method of any one of claims 1-7.

10. A computer readable storage medium, characterized in that computer instructions are stored, which when executed perform the method of any of claims 1-7.

Images