CN113157347A - Automatic probe deployment method, electronic device and storage medium - Google Patents
Automatic probe deployment method, electronic device and storage medium Download PDFInfo
- Publication number
- CN113157347A CN113157347A CN202110540117.9A CN202110540117A CN113157347A CN 113157347 A CN113157347 A CN 113157347A CN 202110540117 A CN202110540117 A CN 202110540117A CN 113157347 A CN113157347 A CN 113157347A
- Authority
- CN
- China
- Prior art keywords
- module
- probe
- target process
- kernel
- target
- 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.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- 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/3668—Software testing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
Abstract
The invention discloses an automatic probe deployment method, electronic equipment and a storage medium, wherein the method comprises the following steps: when determining that a target process on target equipment is started through a driving module, loading an identification module for the target process; and determining the application type of the target process by the identification module, acquiring the probe matched with the application type, and deploying the probe into the target process. The identification module is loaded in the target process, the probe adapted to the target process is determined through the identification module, and the determined probe is automatically deployed in the target process, so that the efficiency and the accuracy of probe deployment are improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of data processing, in particular to an automatic probe deployment method, electronic equipment and a storage medium.
Background
The probe technology is a technology that a custom module is embedded in an application to achieve the purpose of monitoring the application performance, different applications correspond to different probes at present, each application is matched with a configuration file, and the configuration file contains the configuration mode and the path of the probe, so that technicians need to manually deploy the probes for different applications according to the configuration files.
However, the process of deploying the probe by manual configuration is tedious at present, and different applications on the same machine require operation and maintenance personnel to be familiar with the configuration files, so that the technical requirements on technical personnel are high, and errors are easy to occur when the probe is deployed by the manual configuration mode in the face of a huge machine group, so that the existing probe deployment mode is not only low in efficiency but also low in accuracy.
Disclosure of Invention
The embodiment of the invention provides an automatic probe deployment method, electronic equipment and a storage medium, so as to realize automatic probe deployment in a target process.
In a first aspect, an embodiment of the present invention provides an automatic probe deployment method, which is applied to an automatic probe deployment system, where the automatic probe deployment system includes: a driving module and a recognition module, wherein,
when determining that a target process on target equipment is started through a driving module, loading an identification module for the target process;
and determining the application type of the target process by the identification module, acquiring the probe matched with the application type, and deploying the probe into the target process.
In a second aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:
one or more processors;
storage means for storing one or more programs;
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the methods of any of the embodiments of the present invention.
In a third aspect, the embodiments of the present invention also provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program implements the method of any embodiment of the present invention.
In the embodiment of the invention, the identification module is loaded in the target process, the probe adapted to the target process is determined through the identification module, and the determined probe is automatically deployed in the target process, so that the probe deployment efficiency and accuracy are improved.
Drawings
FIG. 1 is a flow chart of a method for automatically deploying a probe according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of an automatic deployment system of a probe according to an embodiment of the present invention;
FIG. 3 is an interaction sequence diagram for loading an identity module for a target process according to an embodiment of the present invention;
FIG. 4 is a timing diagram illustrating interaction of a deployment probe according to an embodiment of the present invention;
FIG. 5 is a flowchart of a method for automatically deploying a probe according to a second embodiment of the present invention;
fig. 6 is a block diagram of an electronic device according to a third 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 limiting of 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. 1 is a flowchart of an automatic probe deployment method according to an embodiment of the present invention, where the embodiment is applicable to a case where a probe is automatically deployed for a target process, and the method may be performed by an automatic probe deployment system according to an embodiment of the present invention. Fig. 2 is a block diagram of an automatic probe deployment system according to the present embodiment, and as shown in fig. 2, the automatic probe deployment system includes: the system comprises a driving module 11, a recognition module 12, a kernel module 13, a probe identification generation module 14 and a monitoring module 15. The function of each module is described below based on the automatic probe deployment process shown in fig. 1, and the method of the embodiment of the present invention specifically includes the following steps:
step S101, when the driver module determines that the target process on the target device is started, the driver module loads an identification module for the target process.
Optionally, when determining that the target process on the target device is started by the driver module, before loading the identification module for the target process, the method further includes: sending a process callback registration message to the kernel module through the driving module according to the designated port, wherein the process callback registration message comprises a designated receiving address; when a starting instruction of a user for a target process is received through a kernel module, a kernel object is created for the target process to start the target process; and generating a process creation message of the target process based on the callback registration message through the kernel module, and sending the process creation message to a specified address of the driver module.
It should be noted that, in this embodiment, the driving module may be a smartgentnt, the recognition module may be an agenloader, the monitoring module may be a watchdog, and the probe identifier generating module may be a machineagent. Of course, this embodiment is merely an example and does not limit the specific type of each module.
The target process refers to a process that has not been started to run on the target device, and the number of the target processes is not limited, so the probe is mainly deployed for a process in a to-be-started state in this embodiment.
Optionally, when determining that the target process on the target device is started by the driver module, loading the identification module for the target process may include: adding a mark for a target process according to the process creation message through a driving module; loading a kernel dynamic library to the target process added with the mark through a kernel module, generating a kernel dynamic library loading completion message, and sending the kernel dynamic library loading completion message to a drive module; adding the code segment of the loading identification module into a specified kernel function when the driver module determines that the kernel dynamic library loading completion message is received; and calling a specified kernel function through the kernel module to load the identification module for the target process.
Optionally, before adding the code segment of the recognition module to the specified kernel function, the method may further include: and determining that the target process is in a preset loading list through the driving module, wherein the preset loading list comprises a process identifier of the identification module needing to be loaded.
Specifically, as shown in fig. 3, an interaction sequence diagram for loading an identity module for a target process according to the embodiment includes:
1. the configuration is loaded.
Specifically, the driver module automatically loads configuration when being started, the configuration includes a preset loading list and a complete path of the identification module, and the preset loading list includes a process identifier of the identification module to be loaded.
2. The process calls back registration information.
Specifically, before the kernel module creates a process, the driver module sends process callback registration information to the kernel module according to the specified port, and the callback registration information includes a specified receiving address.
For example, the callback is created/destroyed by the port api PsSetCreateProcessNotifyRoute registration process; through the port api: PsSetCreateThreadNotififyRouteine registration thread creation/destruction callback; through the port api: and the PsSetLoadImageNotifyRoute registration module loads a callback and the like. Of course, this embodiment is merely an example, and does not limit the specific type of the designated port.
3. And starting instructions sent by the user.
The method comprises the steps of receiving a starting instruction sent by a user through a kernel module, and specifically, obtaining the starting instruction through a trigger function NtCreateProcess by the user.
4. A kernel object is created for the target process.
The kernel module creates a kernel object for the target process to start the target process.
5. The process creates a message.
The kernel module distributes identification for the target process, generates a process creating message of the target process based on the callback registration message acquired before, and sends the process creating message to a designated address of the driver module to inform the driver module that the target process is created completely.
6. A tag is added to the target process.
After acquiring the process creation message sent by the kernel module, the driver module adds a mark to the created target process, and the marked process indicates that the identification module needs to be loaded subsequently.
7. And loading the kernel dynamic library for the marked target process.
Before the identification module is loaded on the target process, the kernel module loads a kernel dynamic library on the target process to which the tag is added, so as to ensure the implementation of the basic function of the target process, and the kernel dynamic library may be ntdll.
8. And loading a complete message by the kernel dynamic library.
After the kernel dynamic library is loaded, the kernel module generates a kernel dynamic library loading completion message and triggers a callback to notify the driver module that the kernel dynamic library is loaded.
9. And determining that the target process is in a preset loading list.
The driver module determines whether the identifier of the target process loaded by the kernel dynamic library is in a preset loading list configured before, if so, the driver module indicates that the subsequent identification module needs to be loaded, otherwise, the driver module indicates that the subsequent identification module does not need to be loaded.
10. The code segment that loads the recognition module is added to the specified kernel function.
Specifically, when the driver module determines that the kernel dynamic library loading completion message is received, the code segment of the identification module is added to the specified kernel function. The specified kernel function may be specifically an LdrInitialize Thunk function.
11. And calling a specified kernel function to load the identification module for the target process.
The kernel module can take a code for loading the identification module as a springboard code, when a new process is created, the kernel module calls an LdrInitialize Thunk function, and then the springboard code is entered for loading the identification module, so that each target process corresponds to one identification module respectively.
And S102, determining the application type of the target process through the identification module, acquiring a probe matched with the application type, and deploying the probe into the target process.
Optionally, determining, by the identification module, an application type to which the target process belongs may include: determining the type of a starting function called by a target process through an identification module; and determining the application type of the target process according to the type of the starting function.
Fig. 4 is a timing interaction diagram of a deployment probe provided in this embodiment, and in this embodiment, an example is mainly performed by taking an example that a target process belongs to a Java application, where the diagram includes:
1. the identification module is preloaded.
When the process is started, the identification module agentloader is mainly preloaded through the driver module smartgentmtnt.
2. The start function JNI _ createjavvm is modified.
The recognition module will modify the boot function JNI _ createjavvm to add its own logical code.
3. The start function is called when the Java application is started.
And when the called starting function JNI _ CreateJavaVM is determined when the target process is started, determining that the application type of the target process is Java application.
4. And adjusting the starting parameters and adding the probe configuration into the starting parameters.
When the identification module determines that the application type of the target process is Java, the different applications are respectively matched with different probes, and the probes matched with the Java applications are Java agents, so that the probes required to be deployed in the target process can be determined. The startup parameters are adjusted by the recognition module, and probe configuration is appended to the startup parameters, for example, Java.
5. The probe deployment is completed.
And deploying the probe java agent to a target process, thereby completing the deployment of the probe.
6. And (5) probe flow.
The probe performs corresponding operations in the target process, such as data acquisition, etc., and this embodiment is merely an example, and does not limit the specific operation manner of the probe.
In the embodiment of the invention, the identification module is loaded in the target process, the probe adapted to the target process is determined by the identification module, and the determined probe is automatically deployed in the target process, so that the efficiency and the accuracy of probe deployment are improved.
Example two
Fig. 5 is a flowchart of an automatic probe deployment method according to an embodiment of the present invention, where the embodiment is based on the foregoing embodiment, and after the probe is deployed to a target process, the method further includes: and acquiring data of the target process through the probe, binding the acquired data with the unique probe identification, and reporting the bound data to the server.
As shown in fig. 5, the method of the embodiment of the present disclosure specifically includes:
step S201, when determining that the target process on the target device is started through the driver module, loading an identification module for the target process.
Optionally, when determining that the target process on the target device is started by the driver module, before loading the identification module for the target process, the method further includes: sending a process callback registration message to the kernel module through the driving module according to the designated port, wherein the process callback registration message comprises a designated receiving address; when a starting instruction of a user for a target process is received through a kernel module, a kernel object is created for the target process to start the target process; and generating a process creation message of the target process based on the callback registration message through the kernel module, and sending the process creation message to a specified receiving address of the driver module.
Optionally, when determining that the target process on the target device is started by the driver module, loading the identification module for the target process may include: adding a mark for a target process according to the process creation message through a driving module; loading a kernel dynamic library to the target process added with the mark through a kernel module, generating a kernel dynamic library loading completion message, and sending the kernel dynamic library loading completion message to a drive module; adding the code segment of the loading identification module into a specified kernel function when the driver module determines that the kernel dynamic library loading completion message is received; and calling a specified kernel function through the kernel module to load the identification module for the target process.
Optionally, before adding the code segment of the recognition module to the specified kernel function, the method may further include: and determining that the target process is in a preset loading list through the driving module, wherein the preset loading list comprises a process identifier of the identification module needing to be loaded.
Step S202, determining the application type of the target process through the identification module, acquiring the probe matched with the application type, and deploying the probe into the target process.
Optionally, determining, by the identification module, an application type to which the target process belongs may include: determining the type of a starting function called by a target process through an identification module; and determining the application type of the target process according to the type of the starting function.
And step S203, acquiring data of the target process through the probe, binding the acquired data with the unique identifier of the probe, and reporting to the server.
Optionally, the method further comprises: and monitoring the probe identification generation module through the monitoring module, and controlling the probe identification generation module to be in a starting state according to a monitoring result.
Optionally, after controlling the probe identifier generating module to be in the start state according to the monitoring result, the method further includes: and generating a probe unique identifier for the probe by the probe identifier generating module in a starting state, and sending the probe unique identifier to the probe.
Specifically, the monitoring module in this embodiment is configured to monitor the probe identification generating module in real time, and send a start instruction to the probe identification generating module when it is determined that the probe identification generating module is down, so as to control the probe identification generating module to be in a start state all the time.
In order to ensure the uniqueness of the probe identification, the probe identification generating module in the starting state is used for generating the probe unique identification for the probe in the working state at regular time, and sending the probe unique identification to the corresponding probe. Therefore, data acquisition is carried out on the target process through the probe, and the acquired data is bound with the unique identifier of the probe and then reported to the server.
In the embodiment of the invention, the identification module is loaded in the target process, the probe adapted to the target process is determined by the identification module, and the determined probe is automatically deployed in the target process, so that the efficiency and the accuracy of probe deployment are improved. And carrying out data acquisition on the target process through the probe, binding the acquired data with the unique probe identification and reporting to the server so as to accurately analyze the related data of the target process with the server.
EXAMPLE III
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. FIG. 6 illustrates a block diagram of an exemplary electronic device 412 suitable for use in implementing embodiments of the present invention. The electronic device 412 shown in fig. 6 is only an example and should not bring any limitations to the functionality and scope of use of the embodiments of the present invention.
As shown in fig. 6, the electronic device 412 is in the form of a general purpose computing device. The components of the electronic device 412 may include, but are not limited to: one or more processors 416, a memory 428, and a bus 418 that couples the various system components (including the memory 428 and the processors 416).
The memory 428 is used to store instructions. Memory 428 can include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)430 and/or cache memory 432. The electronic device 412 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 434 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 6, 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 CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 418 by one or more data media interfaces. Memory 428 can 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 440 having a set (at least one) of program modules 442 may be stored, for instance, in memory 428, such program modules 442 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. The program modules 442 generally perform the functions and/or methodologies of the described embodiments of the invention.
The electronic device 412 may also communicate with one or more external devices 414 (e.g., keyboard, pointing device, display 424, etc.), with one or more devices that enable a user to interact with the electronic device 412, and/or with any devices (e.g., network card, modem, etc.) that enable the electronic device 412 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 422. Also, the electronic device 412 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) through the network adapter 420. As shown, network adapter 420 communicates with the other modules of electronic device 412 over bus 418. It should be appreciated that although not shown in FIG. 6, other hardware and/or software modules may be used in conjunction with the electronic device 412, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The processor 416, by executing instructions stored in the memory 428, performs an automated deployment method of probes: when determining that a target process on target equipment is started through a driving module, loading an identification module for the target process; and determining the application type of the target process by the identification module, acquiring the probe matched with the application type, and deploying the probe into the target process.
Example four
Embodiments of the present invention also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a method for automatic deployment of probes, comprising: when determining that a target process on target equipment is started through a driving module, loading an identification module for the target process; and determining the application type of the target process by the identification module, acquiring the probe matched with the application type, and deploying the probe into the target process.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling an electronic device (which may be a personal computer, a server, or a network device) to execute the automatic deployment method of the probe according to the embodiments of the present invention.
It should be noted that, the units and modules included in the above embodiments are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
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 greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. The automatic deployment method of the probe is applied to an automatic deployment system of the probe, and the automatic deployment system of the probe comprises the following steps: a driving module and a recognition module, wherein,
when the driver module determines that a target process on target equipment is started, the driver module loads the identification module for the target process;
determining the application type of the target process through the identification module, acquiring a probe matched with the application type, and deploying the probe into the target process.
2. The method according to claim 1, wherein the system further includes a kernel module, and the determining, by the driver module, that the target process on the target device is started before the identifying module is loaded for the target process further includes:
sending a process callback registration message to the kernel module through the drive module according to a designated port, wherein the process callback registration message comprises a designated receiving address;
when a starting instruction of a user for the target process is received through the kernel module, a kernel object is created for the target process so as to start the target process;
and generating a process creation message of the target process based on the callback registration message through the kernel module, and sending the process creation message to the specified receiving address of the driver module.
3. The method according to claim 2, wherein the loading the identification module for the target process when the driver module determines that the target process on the target device is started comprises:
adding a mark for the target process according to the process creation message through the driving module;
loading a kernel dynamic library to the target process added with the mark through the kernel module, generating a kernel dynamic library loading completion message, and sending the kernel dynamic library loading completion message to the drive module;
adding a code segment for loading the identification module into a specified kernel function when the driver module determines that the kernel dynamic library loading completion message is received;
and calling the specified kernel function through a kernel module to load the identification module for the target process.
4. The method of claim 3, wherein prior to adding the code segments of the identified module to the specified kernel function, further comprising:
and determining that the target process is in a preset loading list through the driving module, wherein the preset loading list comprises a process identifier of a module needing to be loaded and identified.
5. The method of claim 1, wherein the determining, by the identification module, the application type to which the target process belongs comprises:
determining the type of a starting function called by the target process through the identification module;
and determining the application type of the target process according to the type of the starting function.
6. The method of claim 1, wherein the system further comprises a monitoring module and a probe identity generation module connected to the monitoring module,
the method further comprises the following steps:
and monitoring the probe identification generation module through the monitoring module, and controlling the probe identification generation module to be in a starting state according to a monitoring result.
7. The method according to claim 6, wherein after controlling the probe identity generating module to be in the activated state according to the monitoring result, the method further comprises:
generating a probe unique identifier for the probe through the probe identifier generating module in a starting state, and sending the probe unique identifier to the probe.
8. The method of claim 7, wherein after said deploying said probe into said target process, further comprising:
and acquiring data of the target process through the probe, binding the acquired data with the unique identifier of the probe, and reporting the bound data to a server.
9. An electronic device, characterized in that the electronic device comprises:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-8.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110540117.9A CN113157347A (en) | 2021-05-18 | 2021-05-18 | Automatic probe deployment method, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110540117.9A CN113157347A (en) | 2021-05-18 | 2021-05-18 | Automatic probe deployment method, electronic device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113157347A true CN113157347A (en) | 2021-07-23 |
Family
ID=76876631
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110540117.9A Withdrawn CN113157347A (en) | 2021-05-18 | 2021-05-18 | Automatic probe deployment method, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113157347A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114024879A (en) * | 2021-10-18 | 2022-02-08 | 中国联合网络通信集团有限公司 | Network probe deployment method, device and storage medium |
| CN114610446A (en) * | 2022-03-11 | 2022-06-10 | 北京基调网络股份有限公司 | Method, device and system for automatically injecting probe |
| CN115599410A (en) * | 2022-12-15 | 2023-01-13 | 杭州数列网络科技有限责任公司（Cn） | Large-scale JAVA probe management method and system |
| CN115904863A (en) * | 2022-10-26 | 2023-04-04 | 荣耀终端有限公司 | PC scene recognition method and electronic equipment |
-
2021
- 2021-05-18 CN CN202110540117.9A patent/CN113157347A/en not_active Withdrawn
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114024879A (en) * | 2021-10-18 | 2022-02-08 | 中国联合网络通信集团有限公司 | Network probe deployment method, device and storage medium |
| CN114610446A (en) * | 2022-03-11 | 2022-06-10 | 北京基调网络股份有限公司 | Method, device and system for automatically injecting probe |
| CN114610446B (en) * | 2022-03-11 | 2023-01-03 | 北京基调网络股份有限公司 | Method, device and system for automatically injecting probe |
| CN115904863A (en) * | 2022-10-26 | 2023-04-04 | 荣耀终端有限公司 | PC scene recognition method and electronic equipment |
| CN115904863B (en) * | 2022-10-26 | 2023-11-07 | 荣耀终端有限公司 | PC scene recognition method and electronic equipment |
| CN115599410A (en) * | 2022-12-15 | 2023-01-13 | 杭州数列网络科技有限责任公司（Cn） | Large-scale JAVA probe management method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113157347A (en) | Automatic probe deployment method, electronic device and storage medium | |
| US11392461B2 (en) | Method and apparatus for processing information | |
| EP2840495B1 (en) | Container-based processing method and apparatus | |
| CN107807839B (en) | Method and device for modifying memory data of virtual machine and electronic equipment | |
| US6698016B1 (en) | Method for injecting code into another process | |
| KR20110098567A (en) | Method and apparatus for generating minimal boot image | |
| CN111506386A (en) | Virtual machine online migration method, device, equipment and computer readable storage medium | |
| CN1212062A (en) | Extended BIOS adapted for remote diagnostic repair | |
| CN102999343A (en) | Method and device for forbidding self-starting of startup project | |
| US8180930B2 (en) | Information processing device, and device initialization method in the information processing device | |
| CN112650658A (en) | Application program exception recording and reproduction method, device and storage medium | |
| CN110716845A (en) | Method for reading log information of Android system | |
| CN103019706A (en) | Method and device for processing startup item | |
| CN112000574A (en) | Pressure testing method, device, equipment and storage medium | |
| CN109582542B (en) | Method for dumping core of embedded system | |
| CN112925606A (en) | Memory management method, device and equipment | |
| CN110414218B (en) | Kernel detection method and device, electronic equipment and storage medium | |
| CN113485755B (en) | Device driver verification method, device and storage medium | |
| US9852028B2 (en) | Managing a computing system crash | |
| US8209443B2 (en) | System and method for identifying lost/stale hardware in a computing system | |
| CN111399999A (en) | Computer resource processing method and device, readable storage medium and computer equipment | |
| CN113505026B (en) | Method, device and equipment for verifying backup data and storage medium | |
| CN111090458B (en) | Gray release system and application release method based on gray release system | |
| CN114691496A (en) | Unit testing method, unit testing device, computing equipment and medium | |
| CN113791874A (en) | Configuration method and device for virtual machine boot, computer equipment and storage medium |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210723 |
|
| WW01 | Invention patent application withdrawn after publication |