CN110515806B - Probe configuration method, device, computer equipment and storage medium - Google Patents
Probe configuration method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110515806B CN110515806B CN201910818374.7A CN201910818374A CN110515806B CN 110515806 B CN110515806 B CN 110515806B CN 201910818374 A CN201910818374 A CN 201910818374A CN 110515806 B CN110515806 B CN 110515806B
- Authority
- CN
- China
- Prior art keywords
- probe
- module
- program
- virtual machine
- container
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3636—Software debugging by tracing the execution of the program
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Abstract
The embodiment of the invention discloses a probe configuration method, a probe configuration device, computer equipment and a storage medium. The method comprises the following steps: when detecting that an application program is started, adding a probe configuration module in an initial virtual machine creation module through a probe deployment module to form a target virtual machine creation module, wherein the application program runs in a virtual machine, the execution sequence of the probe configuration module is before that of the initial virtual machine creation module, and the probe configuration module is used for adding a pointing address of the probe program in a starting parameter of the virtual machine; and in the process of calling the target virtual machine creation module, starting a probe program according to the pointing address of the probe program so as to deploy the probe program in the application program. The embodiment of the invention can reduce the labor cost of probe deployment, reduce the complexity of probe deployment and improve the deployment efficiency of the probe.
Description
Technical Field
The embodiment of the invention relates to the field of data acquisition, in particular to a probe configuration method and device, computer equipment and a storage medium.
Background
The probe technology is a custom module embedded in an application program to monitor the performance of the application program.
Currently, the method for deploying the probe in an application program specifically includes: manually adding parameters of a probe code packet in the starting parameters of the application program so as to start the probe program while the application program is started; and manually adding authority data required by the operation of the probe program in the configuration file.
The existing probe deployment modes are all manual configuration, and with the increase of service data and the improvement of the complexity of a distributed system in a micro-service architecture, the workload of the manual configuration mode is increased progressively, and the probe deployment efficiency is reduced. Meanwhile, the manual deployment mode is increased along with the increment of workload, the higher the error probability is, and the difficulty in troubleshooting the errors of the probe deployment is higher. In addition, different application programs are deployed respectively, and the professional requirements on deployment personnel are high.
Disclosure of Invention
The embodiment of the invention provides a probe configuration method, a probe configuration device, computer equipment and a storage medium, which can reduce the labor cost of probe deployment, reduce the complexity of probe deployment and improve the deployment efficiency of probes.
In a first aspect, an embodiment of the present invention provides a probe configuration method, including:
when detecting that an application program is started, adding a probe configuration module in an initial virtual machine creation module through a probe deployment module to form a target virtual machine creation module, wherein the application program runs in a virtual machine, the execution sequence of the probe configuration module is before that of the initial virtual machine creation module, and the probe configuration module is used for adding a pointing address of the probe program in a starting parameter of the virtual machine;
and in the process of calling the target virtual machine creation module, starting a probe program according to the pointing address of the probe program so as to deploy the probe program in the application program.
In a second aspect, an embodiment of the present invention provides a probe configuring apparatus, including:
the virtual machine creating and injecting module is used for adding a probe configuration module in an initial virtual machine creating module through a probe deploying module to form a target virtual machine creating module when the application program is detected to be started, wherein the application program runs in the virtual machine, the execution sequence of the probe configuration module is before that of the initial virtual machine creating module, and the probe configuration module is used for adding a pointing address of the probe program in the starting parameters of the virtual machine;
and the probe program starting module is used for starting the probe program according to the pointing address of the probe program in the process of calling the target virtual machine creating module so as to realize the deployment of the probe program in the application program.
In a third aspect, an embodiment of the present invention further provides an apparatus, including a memory, a processor, and a computer program stored in the memory and operable on the processor, where the processor executes the computer program to implement the probe configuration method according to any one of the embodiments of the present invention.
In a fourth aspect, embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements a probe configuration method according to any one of the embodiments of the present invention.
According to the embodiment of the invention, the application program is monitored, when the application program is started, the pre-configured probe configuration module is executed firstly, the pointing address of the probe program is added into the virtual machine creation module, then the virtual machine creation module is executed, and the probe program is started according to the pointing address of the probe program in the operation of the virtual machine creation module, so that the probe program is deployed in the application program, and the probe program is started while the application program is started.
Drawings
FIG. 1a is a flow chart of a method for configuring a probe according to a first embodiment of the present invention;
FIG. 1b is a flowchart of a probe configuration method according to a first embodiment of the present invention;
FIG. 2a is a flowchart of a probe configuration method according to a second embodiment of the present invention;
FIG. 2b is a flowchart of a probe configuration method according to a second embodiment of the present invention;
FIG. 3 is a flowchart of a probe configuration method according to a third embodiment of the present invention;
FIG. 4a is a flowchart of a probe configuration method according to a fourth embodiment of the present invention;
FIG. 4b is a flowchart of a probe configuration method according to a fourth embodiment of the present invention;
FIG. 4c is a flowchart of a method for configuring a probe according to a fourth embodiment of the present invention;
FIG. 5 is a schematic structural diagram of a probe arranging apparatus according to a fifth embodiment of the present invention;
fig. 6 is a schematic structural diagram of a computer device in a sixth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1a is a flowchart of a probe configuration method in one embodiment of the present invention, where this embodiment is applicable to a case where a probe program is deployed in an application program, and the method may be executed by a probe configuration apparatus provided in an embodiment of the present invention, where the apparatus may be implemented in a software and/or hardware manner, and may generally be integrated into a computer device, for example, a terminal device or a server. As shown in fig. 1a, the method of this embodiment specifically includes:
s110, when detecting that an application program is started, adding a probe configuration module in an initial virtual machine creation module through a probe deployment module to form a target virtual machine creation module, wherein the application program runs in a virtual machine, the execution sequence of the probe configuration module is before the execution sequence of the initial virtual machine creation module, and the probe configuration module is used for adding a pointing address of the probe program in the starting parameters of the virtual machine.
The application program can be a client or a service instance.
In the embodiment of the present invention, the application may refer to a micro service, i.e. a service instance, deployed in a micro service architecture. The server can be used for deploying a plurality of application programs, and each application program can be deployed in different containers respectively; or only one application may be deployed in one server.
In addition, the application program in the embodiment of the invention runs in the environment of the virtual machine.
The initial virtual machine creation module is used for creating a virtual machine on which the application program runs. Illustratively, the initial virtual machine creation module is a JNI _ createjavvm function, i.e., a function for creating a Java virtual machine. All Java applications create a virtual machine through the JNI _ createjavvm function and set parameters.
Typically, during application startup: the operating system loads a process loader, wherein the process loader is used for loading all modules depended by the running of the application program into a memory, calling an initial virtual machine creating module and creating a virtual machine environment. Therefore, the application program can process according to the received access request or call other application programs to obtain and feed back the response result.
The probe deployment module is used for modifying the initial virtual machine creation module so that the initial virtual machine creation module starts a probe program in the calling process.
The probe configuration module is used for starting a probe program.
The target virtual machine creating module is used for creating a virtual machine and starting a probe program.
The probe program is used for monitoring the operation behavior of the application program, acquiring operation behavior data and sending the operation behavior data to the server, so that the server can evaluate the performance of the application program.
Adding a probe configuration module in the initial virtual machine creation module to form a target virtual machine creation module may refer to: and adding the code associated with the probe configuration module in the code associated with the initial virtual machine creation module, and meanwhile, placing the code associated with the probe configuration module in front of the code associated with the initial virtual machine creation module. Thereby ensuring that the execution order of the probe configuration module precedes the execution order of the initial virtual machine creation module.
It will be appreciated that starting the probe program at application start requires pre-configuration of the parameters associated with probe program start. The application program runs in the virtual machine, and the probe program can be started when the virtual machine is created, so that the information related to the probe program needs to be added to the starting parameters of the initial virtual machine creation module, so that the probe program is started when the initial virtual machine creation module is called.
Specifically, the pointing address of the probe program is used to acquire the probe program, and is actually an address pointing to a code file of the probe program. The pointing address of the probe program is added in the starting parameter of the virtual machine, and the probe program can be obtained and loaded into the memory according to the pointing address of the probe program when the virtual machine is established. The starting parameters of the virtual machine may refer to related parameters of the application program for loading in the process of calling the initial virtual machine creation module. The starting parameters of the virtual machine are used for loading relevant parameters associated with the creating operation of the virtual machine. The initial virtual machine creating module loads the application program associated with the creating operation of the virtual machine by acquiring the starting parameters of the virtual machine, so that the application program can be accurately and stably operated in the created virtual machine.
And S120, in the process of calling the target virtual machine creation module, starting a probe program according to the pointing address of the probe program so as to realize the deployment of the probe program in the application program.
And calling the target virtual machine creation module, modifying the starting parameters of the virtual machines in the initial virtual machine creation module, and starting each application program according to the updated starting parameters, wherein the started application programs comprise the added probe programs, so that the probe programs are started, and the probe programs monitor the application programs and acquire data.
Optionally, before the probe configuration module is added to the initial virtual machine creation module by the probe deployment module to form a target virtual machine creation module, the method further includes: loading a process loader module; sequentially loading the probe deployment module and the module to be loaded which is depended by the application program through the process loader module; the probe deployment module is a pre-designated pre-load module.
Specifically, the process loader module refers to a module that is commonly used in an operating system and is used for loading programs and dynamic libraries. The process loader module is a module loaded first after the application program is started, and is responsible for mapping files related to the application program from a file form into a memory, loading corresponding dependency modules, initializing executable modules and environments required by the application program, and finally calling a program entry point (main) to execute real work. The preloading module can refer to an application program which is loaded preferentially in the process of loading the application program by the process loader module.
The module to be loaded may refer to other modules to be loaded that are associated with the application. And the module to be loaded is used for supporting the normal operation of the application program.
In this embodiment, the operating system is a Linux system, and the probe deployment module may be set as a Preload module through a Linux Preload technology. Typically, the preload module runs after the process loader module runs.
Specifically, before the application is run, the probe deployment module may be designated as a preloaded module through the configuration file, so that when the process loader module loads the application, the designated preloaded module, that is, the probe deployment module, is inserted into the module table first, and then other modules on which the application depends are inserted, and the preloaded module is always located behind the process loader module in the position of the module table.
The probe deployment module is pre-designated as a pre-loading module, and the probe deployment module and the module to be loaded which is depended by the application program are sequentially loaded through the process loader module, so that the probe program deployment operation is completed before the application program runs, and the normal running of the probe program is ensured when the application program runs.
In addition, the probe program also needs to include the authority required by the probe program during running, so when the probe program is deployed, configuration information for configuring the probe program is required correspondingly.
Optionally, the probe configuration module is further configured to replace, in the start parameter of the virtual machine, the pointing address of the historical permission configuration file with the pointing address of the update permission configuration file that includes permission configuration data of the probe program.
The historical permission configuration file is used for describing permission information of each module related to the application program. And the updated authority configuration file is used for describing authority information of each module associated with the application program and authority information of the probe program. The pointing address of the update permission configuration file is used for pointing to the update permission configuration file, and the initial virtual machine creating module acquires the update permission configuration file.
Specifically, the historical permission configuration file can be obtained, and the update permission configuration file is generated according to the historical permission configuration file. Illustratively, the generation manner is specifically: and adding authority configuration data of the probe program at the tail part of the text in the historical authority configuration file to form an updated authority configuration file. In addition, permission configuration data of the probe program may be added to other text positions in the historical permission configuration file, and the updated permission configuration file may be generated in other manners.
The pointing address of the historical authority configuration file is replaced by the pointing address of the updated authority configuration file, so that when authority information is called, the content in the updated authority configuration file can be obtained according to the pointing address of the updated authority configuration file, authority configuration data of the probe program can be obtained, and the probe program can complete various monitoring tasks according to the authority configuration data.
By replacing the pointing address of the historical permission configuration file with the pointing address of the updated permission configuration file, permission configuration data of the probe program can be inquired in the permission configuration file, and permission information of the probe program is configured.
In a specific example, as shown in fig. 1b, the probe configuration method may include:
s101, when detecting that the application program is started, the processor loads a process loader module.
S102, the process loader module loads a probe configuration module.
The probe configuration module is a preloading module and is pre-designated by the Linux Preload technology.
S103, the probe configuration module adjusts the initial virtual machine creation module to form a target virtual machine creation module.
The initial virtual machine creation module is a JNI _ CreateJavaVM function.
S104, the processor calls the target virtual machine creating module.
S105, adding a pointing address of the probe program in the starting parameters of the virtual machine by the probe configuration module in the target virtual machine creation module, and replacing the pointing address of the historical authority configuration file with the pointing address of the updating authority configuration file containing the authority configuration data of the probe program.
Actually, the java code packet matched with the probe program is stored at the address pointed by the pointing address, and the authority configuration data of the probe program is added to the original authority configuration file.
And S106, completing the calling of the target virtual machine creating module.
S107, the processor starts the probe program to monitor the application program.
According to the embodiment of the invention, the application program is monitored, when the application program is started, the pre-configured probe configuration module is executed firstly, the pointing address of the probe program is added into the virtual machine creation module, then the virtual machine creation module is executed, and the probe program is started according to the pointing address of the probe program in the operation of the virtual machine creation module, so that the probe program is deployed in the application program, and the probe program is started while the application program is started.
Example two
Fig. 2a is a flowchart of a probe configuration method in the second embodiment of the present invention, which is optimized based on the above embodiment, and before detecting the start of the application program, the optimization is: monitoring a process associated with a container system when the container system is detected to be started; when the container establishing process is detected to exist, in the container establishing process, the probe deploying module is configured, and a directory of an access file related to the probe program is mounted in the container. The method of the embodiment specifically includes:
s210, when the container system is detected to be started, monitoring the process related to the container system.
In this embodiment, the application programs are deployed in containers, one container deploys one application, and different containers are separate and independent from each other. Thus, a probe deployment module deployed in an environment external to the container will not affect the container, i.e., no probe deployment module is deployed in the container. Therefore, there is a need to configure the probe deployment module in a container in which the application is deployed.
A container system may refer to a cluster of containers. Illustratively, the container system may be referred to as a Docker. In the Linux operating system, docker uses the Linux namespace to isolate the running environment of the container.
The detection of whether the container system is activated may specifically be: it is determined whether a process of the container system is occurring. If all running processes do not include any process associated with the container system before a certain time, after the certain time, one running process exists as the process associated with the container system, and the container system is determined to be started. The identification and detection of the process associated with the container system may be determined by a name of the process, for example, the process including the name of the identification information of the container system is the process associated with the container system. In addition, the process associated with the container system may also be determined in other manners, and whether the process of the container system occurs may also be determined in other manners, for example, if a starting process of the container system exists in all running processes, the starting process may refer to a process with a name specified in advance, which is not limited in the embodiment of the present invention.
The process associated with the container system may be a process that is running when the container system is operating normally.
Specifically, an application may be preconfigured to monitor the progress associated with the container system.
The process associated with the container system is monitored to detect whether the container system has a new container. Generally, the process of deploying and running the application in the container may specifically be: starting a container system, creating a container through the container system, configuring relevant parameters of the application program operation in the container creating process, and loading the application program in the created container. Therefore, after the creation operation of the container is detected, the related parameters of the probe program are added while the original related parameters of the application program running are configured, so that the probe program is deployed in the container.
Optionally, the detecting that the container system is started includes: traversing the process tree; and if the process related to the container engine container system appears in the process tree for the first time, determining that the container system is started.
A process tree may refer to a tree that includes multiple processes that are running, as well as relationships of the processes.
The first occurrence of the process related to the container system indicates that all running processes do not include any process related to the container system before the current time, and the current occurrence of the container system generally indicates that the container system is started and starts to work normally, and at this time, it can be determined that the container system is started. The process of first occurrence of the container system association may also refer to a process of first occurrence of the container system association within a set time period.
The starting of the container system can be accurately judged by traversing the process tree and determining the starting of the container system when the process associated with the container system appears in the process tree for the first time, and whether a new process of the container exists can be monitored in time, so that when the establishment process of the container exists is detected in time, a probe program is configured in the establishment process of the container, and the probe program is guaranteed to be accurately deployed in the container.
S220, when the existence of the establishment process of the container is detected, in the establishment process of the container, the probe deployment module is configured, and the directory of the access file related to the probe program is mounted in the container.
Specifically, when the process of a newly-built container is determined by monitoring the process associated with the container system, and when the process of establishing the container is detected to exist, the probe program starts to be deployed in the process of establishing the container.
The probe deployment module is configured such that the probe deployment module can be run in the container. Illustratively, configuring the probe deployment module includes designating the probe deployment module as a preloaded module.
In addition, the directory of the access file associated with the probe program needs to be mounted in the container, so that other modules can access the access file associated with the probe program in the container.
Wherein, the process related to the container system can be monitored through a Linux Ptrace breakpoint.
Optionally, when it is detected that there is a container establishing process, in the container establishing process, configuring the probe deployment module and mounting a directory of an access file associated with the probe program into the container, where the configuring includes: when a configuration signal of a file system is detected, suspending the establishment process of the container; configuring the probe deployment module; mounting a directory of access files associated with the probe program into the container; and returning to resume the operation of the establishment process of the container.
The configuration signal of the file system is used to allocate a file directory for the created container. Illustratively, the configuration signal of the file system is SYS _ mount or SYS _ pivot _ root.
Suspending the creation process of the container means that the creation process being executed suspends the execution.
And after the establishing process of the container is suspended, executing the operation of configuring the probe deployment module and mounting the directory of the access file associated with the probe program into the container.
Returning to the build process of the resume run container refers to resuming the build process of the suspended run container.
By suspending the running process when the configuration signal of the file system is detected, turning to the operation of executing the configuration probe deployment module, mounting the directory of the access file associated with the probe program into the container, and resuming the running of the suspended process after the configuration is completed, the running application program can be prevented from being modified, the modification of the original code is reduced, the error rate of the probe program deployment is reduced, and the compatibility of the probe program deployment is improved.
And S230, when the application program is detected to be started, adding a probe configuration module in an initial virtual machine creation module through a probe deployment module to form a target virtual machine creation module, wherein the application program runs in a virtual machine, the execution sequence of the probe configuration module is before the execution sequence of the initial virtual machine creation module, and the probe configuration module is used for adding the pointing address of the probe program in the starting parameters of the virtual machine.
The application program takes the container as the running environment.
The application program, the probe deployment module, the initial virtual machine creation module, the probe configuration module, the target virtual machine creation module, the start parameter, the probe program, and the like of the present embodiment may refer to the description of the above embodiments.
And S240, in the process of calling the target virtual machine creation module, starting a probe program according to the pointing address of the probe program so as to deploy the probe program in the application program.
In one particular example, deploying the probe deployment module within the container may be accomplished by a container system monitoring module and a container system auxiliary module. As shown in fig. 2b, the probe configuration method may include:
s201, the container system monitoring module detects whether the container system is started or not by traversing the process tree.
The container system includes a Docker.
S202, when detecting that the container system is started, the container system monitoring module starts the container system auxiliary module.
Specifically, the container system auxiliary module may be started by the processor when receiving the container system start-up information sent by the container system monitoring module.
S203, the auxiliary module of the container system detects all processes related to the container system.
S204, the auxiliary module of the container system monitors the container process and the container sub-process in all the processes related to the container system in a breakpoint manner.
S205, the container system auxiliary module determines to generate a configuration signal of the file system, wherein the configuration signal of the file system is generated in the process of establishing the container.
The configuration signal of the file system is SYS _ mount or SYS _ pivot _ root.
S206, configuring a probe deployment module by the container system auxiliary module.
The configuration probe deployment module is specifically added to the module list by adopting a Preload technology, and the process loader loads the module to be loaded in the module list. When the probe deployment module added by adopting the Preload technology is inserted into the module list, the preloaded marking information is added, the process loader inquires the marking information in the module to be loaded in the loading module list, and the preloaded module is loaded preferentially, namely the probe deployment module is loaded preferentially.
And S207, the container system auxiliary module mounts the directory of the access file associated with the probe program into the container.
And S208, starting the application program in the container.
The embodiment of the invention monitors the process related to the container system in the scene of running the application program in the container, configures the probe deployment module in the establishing process of the container when the establishing process of the container exists, and accurately deploys the probe deployment module into the container, so that the probe deployment module can be automatically run in the container, and simultaneously, the directory of the access file related to the probe program is mounted into the established container, so that the access file related to the probe program can be accessed in the container, and the probe program can be accurately deployed in the container.
EXAMPLE III
Fig. 3 is a flowchart of a probe configuration method in a third embodiment of the present invention, where the optimization is performed based on the above embodiment, and after the probe program is started, the optimization is as follows: generating first identification information of the application program according to the information of the probe program and/or the information of the application program, and reporting the first identification information to a server; receiving second identification information fed back by the server aiming at the first identification information, and sending the second identification information to the probe program; monitoring the application program through the probe program to acquire event data of the application program; forming monitoring data of the application program according to the event data, the first identification information and the second identification information; and reporting the monitoring data to the server through the probe program. The method of the embodiment specifically includes:
s310, when the application program is detected to be started, adding a probe configuration module in an initial virtual machine creation module through a probe deployment module to form a target virtual machine creation module, wherein the application program runs in a virtual machine, the execution sequence of the probe configuration module is before the execution sequence of the initial virtual machine creation module, and the probe configuration module is used for adding a pointing address of the probe program in the starting parameters of the virtual machine.
The application program, the probe deployment module, the initial virtual machine creation module, the probe configuration module, the target virtual machine creation module, the start parameter, the probe program, and the like of the present embodiment may refer to the description of the above embodiments.
And S320, in the process of calling the target virtual machine creating module, starting a probe program according to the pointing address of the probe program so as to deploy the probe program in the application program.
S330, generating first identification information of the application program according to the information of the probe program and/or the information of the application program, and reporting the first identification information to a server.
In this embodiment, only one application program is deployed in one container, and one probe program is deployed in one application program, so that the correspondence between the application programs and the probe programs is one-to-one. The first identification information is used to uniquely identify the application program and the probe program. The information of the probe program includes attribute information of the probe program, such as a name of the probe program and/or a pointing address of a code packet of the probe program.
S340, receiving second identification information fed back by the server aiming at the first identification information, and sending the second identification information to the probe program.
The second identification information is used to identify the computer device where the application program is located. The server may receive the application programs of multiple computer devices, and specifically, multiple application programs may be deployed in one computer device. The first identification information is used to identify a target application among a plurality of applications in one computer device, and the second identification information is used to identify the target computer device among the plurality of computer devices. The computer device may refer to a hardware device in which a micro service (i.e., a service instance) is deployed in a micro service architecture.
And S350, monitoring the application program through the probe program, and acquiring event data of the application program.
The event data is used for describing the operation process of the application program. Specifically, the event data may include operation behavior data of the probe program in the running process according to a preset monitoring rule. The event data may also include statistical data obtained by performing statistical analysis on the operation behavior data.
S360, according to the event data, the first identification information and the second identification information, the monitoring data of the application program are formed.
And S370, reporting the monitoring data to the server through the probe program.
And reporting the monitoring data added with the first identification information and the second identification information to a server, wherein the server can uniquely determine an object for acquiring event data through the first identification information and the second identification information, namely uniquely determine a target application program in target computer equipment. Thereby, the operational behaviour data is bound to the unique application and the computer device in the server.
According to the embodiment of the invention, after the probe program is started, the first identification information of the application program is generated in the local equipment or in the container, the second identification information determined by the server according to the first identification information is received, the first identification information and the second identification information are combined with event data acquired by the probe program and serve as monitoring data to be reported to the server together, and the corresponding relation between the probe program or the application program and the event data is established, so that the server can quickly determine the probe program or the application program of the monitoring data according to the first identification information and the second identification information, the source object of the monitoring data is uniquely identified, the server can conveniently count the monitoring data of the application program, the performance evaluation is carried out on the application program, the registration of the probe program is realized, and the accuracy of the data acquired by the probe program is improved.
Example four
Fig. 4a is a flowchart of a probe configuration method in a fourth embodiment of the present invention, where the embodiment is optimized based on the foregoing embodiment, and before the application program is detected to be started, the optimization is as follows: monitoring a process associated with a container system when the container system is detected to be started; when the container establishing process is detected to exist, in the container establishing process, the probe deploying module is configured, and a directory of an access file related to the probe program is mounted in the container. And after starting the probe program, optimizing as follows: generating first identification information of the application program according to the information of the probe program and/or the information of the application program, and reporting the first identification information to a server; receiving second identification information fed back by the server aiming at the first identification information, and sending the second identification information to the probe program; monitoring the application program through the probe program to acquire event data of the application program; forming monitoring data of the application program according to the event data, the first identification information and the second identification information; and reporting the monitoring data to the server through the probe program. The method of the embodiment specifically includes:
s410, when detecting that the container system is started, monitoring the process related to the container system.
The application program, the probe deployment module, the initial virtual machine creation module, the probe configuration module, the target virtual machine creation module, the start parameter, the probe program, and the like of the present embodiment may refer to the description of the above embodiments.
Optionally, the detecting that the container system is started includes: traversing the process tree; and if the process related to the container engine container system appears in the process tree for the first time, determining that the container system is started.
Optionally, when it is detected that there is a container establishing process, in the container establishing process, configuring the probe deployment module and mounting a directory of an access file associated with the probe program into the container, where the configuring includes: when a configuration signal of a file system is detected, suspending the establishment process of the container; configuring the probe deployment module; mounting a directory of access files associated with the probe program into the container; and returning to resume the operation of the establishment process of the container.
S420, when the existence of the establishment process of the container is detected, in the establishment process of the container, configuring the probe deployment module and mounting the directory of the access file associated with the probe program into the container.
S430, when detecting that the application program in the container is started, adding a probe configuration module in an initial virtual machine creation module through a probe deployment module to form a target virtual machine creation module, wherein the application program runs in a virtual machine, the execution sequence of the probe configuration module is before the execution sequence of the initial virtual machine creation module, and the probe configuration module is used for adding the pointing address of the probe program in the starting parameters of the virtual machine.
S440, in the process of calling the target virtual machine creating module, starting a probe program according to the pointing address of the probe program so as to deploy the probe program in the application program.
Optionally, before the probe configuration module is added to the initial virtual machine creation module by the probe deployment module to form a target virtual machine creation module, the method further includes: loading a process loader module; sequentially loading the probe deployment module and the module to be loaded which is depended by the application program through the process loader module; the probe deployment module is a pre-designated pre-load module.
Optionally, the probe configuration module is further configured to replace, in the start parameter of the virtual machine, the pointing address of the historical permission configuration file with the pointing address of the update permission configuration file that includes permission configuration data of the probe program.
And S450, generating first identification information of the application program according to the information of the probe program and/or the information of the application program, and reporting the first identification information to a server.
And S460, receiving second identification information fed back by the server aiming at the first identification information, and sending the second identification information to the probe program.
S470, monitoring the application program through the probe program, and acquiring event data of the application program.
S480, according to the event data, the first identification information and the second identification information, forming monitoring data of the application program.
And S490, reporting the monitoring data to the server through the probe program.
In one particular example, a probe configuration system includes a container system monitoring module, a container system assistance module, a probe registration module, and a probe deployment module.
The container system monitoring module is used for monitoring and starting the container system auxiliary module and the probe registration module.
The container system auxiliary module is used for monitoring a container process and a container sub-process by adopting a Linux Ptrace breakpoint, setting the probe deployment module as a preloading module and mounting an access file related to the probe program in the container.
The probe registration module is used for polling the process tree, automatically naming and registering the probe program, generating identification information and reporting the identification information to the server.
The probe deployment module is used for automatically identifying the application program and automatically deploying the probe program. By means of the Linux Preload technology, the probe deployment module is set as a preloading module, and the purpose of automatically embedding the target application program is achieved.
Specifically, as shown in fig. 4b to 4c, the probe configuration method provided in the embodiment of the present invention may specifically include:
s4101, the container system monitoring module detects a Docker process in a process tree traversal mode.
S4102, the container system auxiliary module is started.
S4103, the container system auxiliary module acquires container processes in all Dockers.
S4104, the container system auxiliary module monitors the container process and the sub-processes thereof by utilizing Linux Ptrace breakpoints.
S4105, the container system auxiliary module monitors the process of creating the container.
Specifically, when a container environment is created, a system call is triggered and monitored by the container system auxiliary module.
S4106, when a container is created, the container system auxiliary module configures a probe deployment module into the container and designates the probe deployment module as a preloaded module.
The auxiliary module of the container system adopts the Linux Preload technology to configure the probe deployment module.
S4107, the container system auxiliary module mounts the directory of the access file related to the probe program into the container.
The method and the device for accessing the probe program in the container can realize the access of the probe program in the container by mounting the directory of the access file associated with the probe program in the container.
S4108, an application is started in the container.
S4109, loading a process loader.
S4110, loading a process loader to preload the probe deployment module.
S4111, adding a probe configuration module in the initial virtual machine creation module by the probe deployment module to form a target virtual machine creation module.
Specifically, the probe deployment module modifies the JNI _ createjavvm function and adds its own logic.
The initial virtual machine creation module is a JNI _ CreateJavaVM function before modification.
The target virtual machine creation module is a modified JNI _ createjavvm function.
S4112, calling the target virtual machine creation module.
When the started application is a Java application, the JNI _ createjavvm function is called first.
S4113, the probe configuration module in the target virtual machine creation module adds a pointing address of a probe program in the starting parameters of the virtual machine, and replaces the pointing address of the historical permission configuration file with a pointing address of an update permission configuration file containing permission configuration data of the probe program.
S4114, starting a probe registration module.
S4115, the probe registration module generates first identification information of the application program according to the information of the probe program and/or the information of the application program, and reports the first identification information to a server.
S4116, the probe registration module receives second identification information fed back by the server aiming at the first identification information, and sends the second identification information to the probe program.
S4117, the probe program monitors the application program and obtains event data of the application program.
S4118, the probe program forms monitoring data of the application program according to the event data, the first identification information and the second identification information.
S4119, the probe program reports the monitoring data to the server.
Through the probe program deployment and operation process, only one line of commands are needed for installation under the Linux system, and then all newly started application programs can be automatically identified and automatically deploy the probe programs.
By combining the container system monitoring module, the container system auxiliary module, the probe registration module and the probe deployment module, the workload of a user can be greatly reduced, professional requirements required by the user are reduced, the difficulty of probe program deployment is reduced, and the efficiency of probe program deployment is improved.
The embodiment of the invention deploys the probe deployment module into the container in the scene of running the application program in the container, when the application program in the container is started, the pre-configured probe configuration module is executed firstly, the pointing address of the probe program is added in the virtual machine creation module, then the virtual machine creation module is executed, in the running of the virtual machine creation module, the probe program is started according to the pointing address of the probe program, the monitoring on the application program is started, the first identification information of the application program is generated, the second identification information determined by the server according to the first identification information is received, the first identification information and the second identification information are combined with event data collected by the probe program and serve as monitoring data to be reported to the server together, the corresponding relation between the probe program or the application program and the event data is established, the source object of the monitoring data is uniquely identified, the monitoring data of the application program is convenient to count by the server, and the performance evaluation is carried out on the application program, so that the application program running in the container is automatically deployed and the registration of the probe program is realized integrally, the accurate running of the probe program is ensured, the labor cost of deploying the probe deployment is reduced, the efficiency of the probe deployment is improved, and the accuracy of the probe program data collection is improved.
EXAMPLE five
Fig. 5 is a schematic diagram of a probe configuration apparatus according to a fifth embodiment of the invention. The fifth embodiment is a corresponding apparatus for implementing the probe configuration method provided by the foregoing embodiments of the present invention, and the apparatus may be implemented in a software and/or hardware manner, and may be generally integrated into an electronic device, for example, a computer device, etc.
Accordingly, the apparatus of the present embodiment may include:
a virtual machine creation injection module 510, configured to, when it is detected that an application program is started, add, by a probe deployment module, a probe configuration module to an initial virtual machine creation module to form a target virtual machine creation module, where the application program runs in a virtual machine, an execution sequence of the probe configuration module is before an execution sequence of the initial virtual machine creation module, and the probe configuration module is configured to add, in a start parameter of the virtual machine, a pointing address of the probe program;
and a probe program starting module 520, configured to start a probe program according to the pointing address of the probe program in the process of calling the target virtual machine creating module, so as to implement deployment of the probe program in the application program.
According to the embodiment of the invention, the application program is monitored, when the application program is started, the pre-configured probe configuration module is executed firstly, the pointing address of the probe program is added in the virtual machine creation module, then the virtual machine creation module is executed, and the probe program is started according to the pointing address of the probe program in the operation of the virtual machine creation module, so that the probe program is deployed in the application program, and the probe program is started when the application program is started.
Further, the probe configuration further comprises: the process loader module loading module is used for loading the process loader module before the probe configuration module is added in the initial virtual machine creating module through the probe deploying module to form a target virtual machine creating module; sequentially loading the probe deployment module and the module to be loaded which is depended by the application program through the process loader module; the probe deployment module is a pre-designated pre-load module.
Further, the probe configuration module is further configured to replace, in the start parameter of the virtual machine, the pointing address of the historical permission configuration file with the pointing address of the update permission configuration file containing permission configuration data of the probe program.
Further, the probe configuration further comprises: the system comprises a container system monitoring module, a storage module and a processing module, wherein the container system monitoring module is used for monitoring the process related to the container system when detecting the start of the container system before detecting the start of the application program; when the existence of a container establishing process is detected, the probe deployment module is configured and a directory of an access file related to the probe program is mounted in the container establishing process.
Further, the container system monitoring module includes: the process tree traversal unit is used for traversing the process tree; and if the process related to the container engine container system appears in the process tree for the first time, determining that the container system is started.
Further, the container system monitoring module includes: the container configuration unit is used for suspending the establishment process of the container when a configuration signal of the file system is detected; configuring the probe deployment module; mounting a directory of access files associated with the probe program into the container; and returning to resume the establishment process of the container.
Further, the probe configuration further comprises: the probe program registration module is used for generating first identification information of the application program according to the information of the probe program and/or the information of the application program and reporting the first identification information to a server; receiving second identification information fed back by the server aiming at the first identification information, and sending the second identification information to the probe program; monitoring the application program through the probe program to acquire event data of the application program; forming monitoring data of the application program according to the event data, the first identification information and the second identification information; and reporting the monitoring data to the server through the probe program.
The probe configuration device can execute the probe configuration method provided by the embodiment of the invention, and has the corresponding functional modules and beneficial effects of the executed probe configuration method.
EXAMPLE six
Fig. 6 is a schematic structural diagram of a computer device according to a sixth embodiment of the present invention. FIG. 6 illustrates a block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present invention. The computer device 12 shown in FIG. 6 is only an example and should not bring any limitations to the functionality or scope of use of embodiments of the present invention.
As shown in FIG. 6, computer device 12 is in the form of a general purpose computing device. The components of computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16. The computer device 12 may be a device that is attached to a bus.
Computer device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by computer device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and/or cache memory 32. The computer device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 6, and commonly referred to as a "hard drive"). Although not shown in FIG. 6, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a Compact disk Read-Only Memory (CD-ROM), digital Video disk (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. System memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described.
Computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with computer device 12, and/or with any devices (e.g., network card, modem, etc.) that enable computer device 12 to communicate with one or more other computing devices. Such communication may be through an Input/Output (I/O) interface 22. Further, the computer device 12 may communicate with one or more networks (e.g., local Area Network (LAN), wide Area Network (WAN) via the Network adapter 20. As shown, the Network adapter 20 communicates with other modules of the computer device 12 via the bus 18. It should be understood that although not shown in FIG. 6, other hardware and/or software modules may be used in connection with the computer device 12, including but not limited to microcode, device drivers, redundant processing units, external disk drive Arrays, (Redundant Arrays of Inextreme Disks, RAID) systems, tape drives, data backup storage systems, and the like.
The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, to implement a probe configuration method provided by any of the embodiments of the present invention.
EXAMPLE seven
An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the probe configuration method provided in all embodiments of the present invention:
that is, the program when executed by the processor implements: when detecting that an application program is started, adding a probe configuration module in an initial virtual machine creation module through a probe deployment module to form a target virtual machine creation module, wherein the application program runs in a virtual machine, the execution sequence of the probe configuration module is before that of the initial virtual machine creation module, and the probe configuration module is used for adding a pointing address of the probe program in a starting parameter of the virtual machine; and in the process of calling the target virtual machine creation module, starting a probe program according to the pointing address of the probe program so as to deploy the probe program in the application program.
Computer storage media for embodiments of the present invention may take the form of any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a RAM, a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a flash Memory, an optical fiber, a portable CD-ROM, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radio Frequency (RF), etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a LAN or a WAN, or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in some detail by the above embodiments, the invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the invention, and the scope of the invention is determined by the scope of the appended claims.
Claims (10)
1. A method of configuring a probe, comprising:
when detecting that an application program is started, adding a probe configuration module in an initial virtual machine creation module through a probe deployment module to form a target virtual machine creation module, wherein the application program runs in a virtual machine, the execution sequence of the probe configuration module is before that of the initial virtual machine creation module, and the probe configuration module is used for adding a pointing address of the probe program in a starting parameter of the virtual machine;
and in the process of calling the target virtual machine creation module, starting a probe program according to the pointing address of the probe program so as to deploy the probe program in the application program.
2. The method according to claim 1, before the adding the probe configuration module in the initial virtual machine creation module by the probe deployment module to form the target virtual machine creation module, further comprising:
loading a process loader module;
sequentially loading the probe deployment module and the module to be loaded which is depended by the application program through the process loader module; the probe deployment module is a pre-designated pre-load module.
3. The method of claim 1, wherein the probe configuration module is further configured to replace, in the startup parameters of the virtual machine, the pointing address of the historical privilege profile with the pointing address of the updated privilege profile containing the privilege configuration data of the probe program.
4. The method of claim 2, prior to detecting application launch, further comprising:
monitoring a process associated with a container system when the container system is detected to be started;
when the existence of a container establishing process is detected, the probe deployment module is configured and a directory of an access file related to the probe program is mounted in the container establishing process.
5. The method of claim 4, wherein the detecting of the container system activation comprises:
traversing the process tree;
and if the process related to the container engine container system appears in the process tree for the first time, determining that the container system is started.
6. The method according to claim 4, wherein when it is detected that there is a container establishing process, configuring the probe deployment module and mounting a directory of access files associated with the probe program into the container during the container establishing process, including:
when a configuration signal of a file system is detected, suspending the establishment process of the container;
configuring the probe deployment module;
mounting a directory of the access file associated with the probe program into the container;
and returning to resume the establishment process of the container.
7. The method of claim 1, after initiating the probe procedure, further comprising:
generating first identification information of the application program according to the information of the probe program and/or the information of the application program, and reporting the first identification information to a server;
receiving second identification information fed back by the server aiming at the first identification information, and sending the second identification information to the probe program;
monitoring the application program through the probe program to acquire event data of the application program;
forming monitoring data of the application program according to the event data, the first identification information and the second identification information;
and reporting the monitoring data to the server through the probe program.
8. A probe deployment apparatus, comprising:
the virtual machine creating and injecting module is used for adding a probe configuration module in an initial virtual machine creating module through a probe deploying module to form a target virtual machine creating module when the application program is detected to be started, wherein the application program runs in a virtual machine, the execution sequence of the probe configuration module is before that of the initial virtual machine creating module, and the probe configuration module is used for adding a pointing address of the probe program in the starting parameters of the virtual machine;
and the probe program starting module is used for starting the probe program according to the pointing address of the probe program in the process of calling the target virtual machine creating module so as to realize the deployment of the probe program in the application program.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor, when executing the program, implements the probe configuration method of any of claims 1-7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the probe configuration method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910818374.7A CN110515806B (en) | 2019-08-30 | 2019-08-30 | Probe configuration method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910818374.7A CN110515806B (en) | 2019-08-30 | 2019-08-30 | Probe configuration method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110515806A CN110515806A (en) | 2019-11-29 |
| CN110515806B true CN110515806B (en) | 2022-10-14 |
Family
ID=68628761
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910818374.7A Active CN110515806B (en) | 2019-08-30 | 2019-08-30 | Probe configuration method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110515806B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110909345B (en) * | 2019-12-02 | 2022-03-22 | 中国银行股份有限公司 | Tamper-proof method and system for Java system open source software |
| CN112948013B (en) * | 2019-12-24 | 2023-10-10 | 深圳市明源云科技有限公司 | Application probe configuration method and device, terminal equipment and storage medium |
| CN111506476B (en) * | 2020-04-15 | 2021-11-26 | 北京邮电大学 | Terminal authentication and process management system and control method thereof |
| CN111813498A (en) * | 2020-07-02 | 2020-10-23 | 深圳市国电科技通信有限公司 | Terminal container monitoring method, monitoring device, storage medium and processor |
| CN111813646B (en) * | 2020-07-16 | 2023-07-18 | 华北电力大学（保定） | Method and device for injecting application probe in docker container environment |
| CN113973127B (en) * | 2020-07-24 | 2024-03-19 | 中移(苏州)软件技术有限公司 | Network deployment method, device and storage medium |
| CN112148576B (en) * | 2020-09-28 | 2021-06-08 | 北京基调网络股份有限公司 | Application performance monitoring method and system and storage medium |
| CN112527638A (en) * | 2020-12-01 | 2021-03-19 | 北京大米科技有限公司 | Program monitoring system, method and computer readable storage medium |
| CN112751704B (en) * | 2020-12-17 | 2022-07-05 | 杭州安恒信息技术股份有限公司 | Method, device and equipment for checking connectivity of heterogeneous network in network target range |
| CN112749062A (en) * | 2021-01-18 | 2021-05-04 | 广州虎牙科技有限公司 | Server program monitoring method and device, computer equipment and storage medium |
| CN114610446B (en) * | 2022-03-11 | 2023-01-03 | 北京基调网络股份有限公司 | Method, device and system for automatically injecting probe |
| CN117032447A (en) * | 2022-05-31 | 2023-11-10 | 荣耀终端有限公司 | Alternate gesture interaction method and device, electronic chip and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105389243A (en) * | 2015-10-26 | 2016-03-09 | 华为技术有限公司 | Container monitoring method and apparatus |
| CN105610983A (en) * | 2016-03-07 | 2016-05-25 | 北京荣之联科技股份有限公司 | Distributive network monitoring method and system |
| CN108092852A (en) * | 2017-12-26 | 2018-05-29 | 北京科来数据分析有限公司 | A kind of OpenStack flow collection methods based on Transmission Control Protocol |
| CN108334399A (en) * | 2018-01-10 | 2018-07-27 | 天津理工大学 | A kind of multi-source heterogeneous cloud form state data capture method based on cloud probe |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105608239A (en) * | 2014-11-24 | 2016-05-25 | 富泰华工业（深圳）有限公司 | Coordinate measuring machine programming system and method |
-
2019
- 2019-08-30 CN CN201910818374.7A patent/CN110515806B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105389243A (en) * | 2015-10-26 | 2016-03-09 | 华为技术有限公司 | Container monitoring method and apparatus |
| CN105610983A (en) * | 2016-03-07 | 2016-05-25 | 北京荣之联科技股份有限公司 | Distributive network monitoring method and system |
| CN108092852A (en) * | 2017-12-26 | 2018-05-29 | 北京科来数据分析有限公司 | A kind of OpenStack flow collection methods based on Transmission Control Protocol |
| CN108334399A (en) * | 2018-01-10 | 2018-07-27 | 天津理工大学 | A kind of multi-source heterogeneous cloud form state data capture method based on cloud probe |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110515806A (en) | 2019-11-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110515806B (en) | Probe configuration method, device, computer equipment and storage medium | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| CN110780890A (en) | System upgrading method and device, electronic equipment and medium | |
| CN110045991B (en) | RAID configuration method and device of server, computer equipment and storage medium | |
| US11016794B2 (en) | Peripheral device access support for containers | |
| US20200233744A1 (en) | System and Methods for Diagnosing and Repairing a Smart Mobile Device by Disabling Components | |
| US20120210114A1 (en) | Log file processing system and method | |
| JP2021099888A (en) | Service information processing method, device, facility, computer storage medium, and program | |
| CN109117153B (en) | Application processing method, device, terminal and storage medium | |
| CN113760306A (en) | Method and device for installing software, electronic equipment and storage medium | |
| WO2022127196A1 (en) | Application identification method and apparatus, and device and storage medium | |
| US11799743B2 (en) | Node addition in cloud networks | |
| CN110928554A (en) | Deployment method, device, equipment and storage medium | |
| CN109271193B (en) | Data processing method, device, equipment and storage medium | |
| CN114356521A (en) | Task scheduling method and device, electronic equipment and storage medium | |
| US20230239212A1 (en) | Stable References for Network Function Life Cycle Management Automation | |
| US20170199733A1 (en) | Method for terminal to update operating system, terminal and system | |
| CN111399999A (en) | Computer resource processing method and device, readable storage medium and computer equipment | |
| CN116303099A (en) | Cross-platform rapid deployment method, device, medium and equipment for automatic test environment | |
| CN110413311A (en) | ' In System Reconfiguration Method and server | |
| CN113918373A (en) | Memory leak monitoring method, memory leak detection method and corresponding devices | |
| CN115237441A (en) | Upgrade test method, device and medium based on cloud platform | |
| CN113031970A (en) | Automatic installation and deployment method and system | |
| US9264398B2 (en) | Loading an operating system of a diskless compute node using a single virtual protocol interconnect (‘VPI’) adapter | |
| US20120150898A1 (en) | Dynamic Collection Of System Support Files In A Data Processing Environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |