CN113608982A - Function execution performance monitoring method and device, computer equipment and storage medium - Google Patents
Function execution performance monitoring method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN113608982A CN113608982A CN202110853139.0A CN202110853139A CN113608982A CN 113608982 A CN113608982 A CN 113608982A CN 202110853139 A CN202110853139 A CN 202110853139A CN 113608982 A CN113608982 A CN 113608982A
- Authority
- CN
- China
- Prior art keywords
- stack
- function
- target
- target application
- acquiring
- 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.)
- Pending
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/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
- G06F11/3419—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment by assessing time
-
- 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/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The disclosure discloses a function execution performance monitoring method and device, computer equipment and a storage medium, and belongs to the technical field of information processing. The method comprises the following steps: acquiring stack information data of a target thread stack at each time point; determining the execution time of each function in the target thread stack according to the stack information data at each time point; and acquiring the execution performance information of each function according to the execution time of each function. By the scheme, the problem of overlarge 'buried point' granularity generated in order to comprehensively monitor each function is solved, the universality of the execution performance of the monitoring function is improved, and therefore the consumption of system resources such as a CPU (Central processing Unit), a memory and the like is reduced.
Description
Technical Field
The present disclosure relates to the field of information processing technologies, and in particular, to a method and an apparatus for monitoring performance of function execution, a computer device, and a storage medium.
Background
At present, in the process of running an application program, a problem that the application program cannot run normally due to a method called in the application program or a function execution error may occur, so a developer needs to determine to execute an abnormal function or method to solve the problem in a targeted manner.
In the related art, a function is hard-coded in a 'buried point' manner, and the execution condition of the hard-coded function is tracked and recorded, including recording the starting execution time and the ending execution time of the function, determining the execution time of the function by calculating the difference between the starting execution time and the ending execution time, and transmitting the function execution time calculated in real time to a background or a client. And the developer judges whether the function is normally executed or not according to the feedback execution time.
However, in the related art, recording the execution time of the function in a hard-coded manner requires "embedding" the function to obtain the execution time of the function, a large number of functions need to be called in the running process of the application program, the granularity of the "embedding" needs to be increased in order to comprehensively detect the running process of the application program, and the large number of "embedding" causes excessive consumption of system resources such as a Central Processing Unit (CPU), a memory, and the like.
Disclosure of Invention
The disclosure provides a method and a device for monitoring function execution performance, a computer device and a storage medium. The technical scheme is as follows:
in one aspect, a method for monitoring performance of function execution is provided, where the method includes:
acquiring stack information data of a target thread stack at each time point; the target thread stack is a thread stack in the running process of a target application program; the stack information data is used for indicating a function called by the target application program at a corresponding time point;
determining the execution time of each function in the target thread stack according to the stack information data at each time point;
and acquiring execution performance information of each function according to the execution time of each function, wherein the execution performance information is used for indicating whether the corresponding function is abnormal in execution.
In a possible implementation manner, the acquiring stack information data of the target thread stack at each time point includes:
acquiring appointed configuration information, wherein the appointed configuration information comprises at least one of acquisition time interval, acquisition frequency and acquisition function range for acquiring the stack information data;
and acquiring the stack information data of the target thread stack at each time point according to the specified configuration information.
In a possible implementation manner, the acquiring stack information data of the target thread stack at each time point includes:
within the acquisition time interval, acquiring stack information data belonging to the acquisition function range in the target thread stack according to the acquisition frequency;
determining the execution time of each function in the target thread stack according to the stack information data at each time point, including:
determining the continuous stack information data acquisition quantity with the same stack information data; the stack information data are the same, namely the stack frames positioned at the top of the target thread stack are the same and the contents of all the stack frames in the target thread stack are the same;
acquiring a continuous time interval as the execution time of the target function; the continuous time interval is the product of the number of continuous stack information data acquired minus one and the acquisition frequency.
In a possible implementation manner, the acquiring, according to the specified configuration information, stack information data of the target thread stack at each time point includes:
acquiring target attribute information corresponding to the target application program; the target attribute information comprises at least one of a target application identifier, a target application priority level and a target application interface request delay;
acquiring the specified configuration information corresponding to the target attribute information;
and acquiring the stack information data of the target thread stack at each time point according to the specified configuration information.
In one possible implementation, in response to the target attribute information including the target application identification;
the obtaining of the specified configuration information corresponding to the target attribute information includes:
acquiring a mapping relation between the target application identifier and the specified configuration information;
and acquiring the specified configuration information corresponding to the target application identifier according to the mapping relation.
In one possible implementation, the target application priority level is included in response to the target attribute information;
the obtaining of the specified configuration information corresponding to the target attribute information includes:
acquiring the designated configuration information corresponding to the priority level of the target application; the target application priority level is positively correlated with the duration of the acquisition time interval, the acquisition frequency and the number of function types of the acquisition function range.
In one possible implementation, in response to the target attribute information including the target application interface request latency;
the obtaining of the specified configuration information corresponding to the target attribute information includes:
acquiring the request time delay of the target application interface and the expected request time delay of the target application interface;
determining a delay difference value according to the request delay of the target application interface and the expected request delay of the target application interface; the time delay difference value is positively correlated with the time length of the acquisition time interval, the acquisition frequency and the function type number of the acquisition function range.
In one aspect, an apparatus for monitoring performance of function execution is provided, the apparatus comprising:
the data acquisition module is used for acquiring stack information data of the target thread stack at each time point; the target thread stack is a thread stack in the running process of a target application program; the stack information data is used for indicating a function called by the target application program at a corresponding time point;
a time determining module, configured to determine, according to the stack information data at each time point, an execution time of each function in the target thread stack;
and the performance acquisition module is used for acquiring the execution performance information of each function according to the execution time of each function, wherein the execution performance information is used for indicating whether the corresponding function is abnormal in execution.
In one possible implementation manner, the data obtaining module includes:
the information acquisition submodule is used for acquiring appointed configuration information, and the appointed configuration information comprises at least one of acquisition time interval, acquisition frequency and acquisition function range for acquiring the stack information data;
and the data acquisition submodule is used for acquiring the stack information data of the target thread stack at each time point according to the specified configuration information.
In one possible implementation manner, the data obtaining module includes:
the stack acquisition submodule is used for acquiring stack information data which belongs to the acquisition function range in the target thread stack according to the acquisition frequency in the acquisition time interval;
the time determination module includes:
the quantity determining submodule is used for determining the continuous stack information data acquisition quantity with the same stack information data; the stack information data are the same, namely the stack frames positioned at the top of the target thread stack are the same and the contents of all the stack frames in the target thread stack are the same;
the time acquisition submodule is used for acquiring the continuous time interval as the execution time of the target function; the continuous time interval is the product of the number of continuous stack information data acquired minus one and the acquisition frequency.
In one possible implementation manner, the data obtaining sub-module includes:
the attribute acquiring unit is used for acquiring target attribute information corresponding to the target application program; the target attribute information comprises at least one of a target application identifier, a target application priority level and a target application interface request delay;
a configuration information obtaining unit, configured to obtain the specified configuration information corresponding to the target attribute information;
and the data acquisition unit is used for acquiring the stack information data of the target thread stack at each time point according to the specified configuration information.
In one possible implementation, in response to the target attribute information including the target application identification;
the configuration information obtaining unit is used for obtaining the configuration information,
acquiring a mapping relation between the target application identifier and the specified configuration information;
and acquiring the specified configuration information corresponding to the target application identifier according to the mapping relation.
In one possible implementation, the target application priority level is included in response to the target attribute information;
the configuration information obtaining unit is used for obtaining the configuration information,
acquiring the designated configuration information corresponding to the priority level of the target application; the target application priority level is positively correlated with the duration of the acquisition time interval, the acquisition frequency and the number of function types of the acquisition function range.
In one possible implementation, in response to the target attribute information including the target application interface request latency;
the configuration information obtaining unit is used for obtaining the configuration information,
acquiring the request time delay of the target application interface and the expected request time delay of the target application interface;
determining a delay difference value according to the request delay of the target application interface and the expected request delay of the target application interface; the time delay difference value is positively correlated with the time length of the acquisition time interval, the acquisition frequency and the function type number of the acquisition function range.
In another aspect, a computer device is provided, which includes a processor and a memory, where at least one instruction, at least one program, a set of codes, or a set of instructions is stored in the memory, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by the processor to implement the above-mentioned function execution performance monitoring method.
In yet another aspect, a computer-readable storage medium is provided, in which at least one instruction, at least one program, a set of codes, or a set of instructions is stored, which is loaded and executed by a processor to implement the above-mentioned function execution performance monitoring method.
According to one aspect of the present application, a computer program product is provided that includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the function execution performance monitoring method provided in the various alternative implementations of the above aspects.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
in the solution shown in the embodiment of the present disclosure, the computer device determines the execution time of each function according to the stack information data at each time point, so as to achieve the purpose of determining whether each function is abnormal, and by the above solution, the problem of excessive granularity of the "buried point" generated for comprehensively monitoring each function can be solved, the versatility of monitoring the execution performance of the function is improved, and thus the consumption of system resources such as a CPU and a memory is reduced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a schematic diagram illustrating a function execution performance monitoring system in accordance with an exemplary embodiment;
FIG. 2 is a flow diagram illustrating a method of function execution performance monitoring in accordance with an exemplary embodiment;
FIG. 3 is a flow diagram illustrating a method of function execution performance monitoring in accordance with an exemplary embodiment;
FIG. 4 is a schematic diagram of a function execution time prediction according to the embodiment shown in FIG. 3;
FIG. 5 is a diagram illustrating a function call stack slice-based time-consuming recording apparatus according to the embodiment shown in FIG. 3;
FIG. 6 is a schematic diagram of an on-demand collection time-consuming recording apparatus based on function call stack slices according to the embodiment shown in FIG. 3;
FIG. 7 is a block diagram illustrating a function execution performance monitoring apparatus in accordance with an exemplary embodiment;
FIG. 8 is a schematic diagram illustrating a configuration of a computer device, according to an example embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
It is to be understood that reference herein to "a number" means one or more and "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
For convenience of understanding, terms referred to in the embodiments of the present disclosure are explained below.
1)Java Agent
Java Agent is also called Java Agent technology, and after JDK (Java Development Kit) version 1.5 we can use Agent technology to build an application independent Agent that helps monitor, run and even replace programs on other JVMs (Java Virtual machines). By using the method, the AOP (Aspect organized Programming) function at the level of a virtual machine can be realized.
2) Thread stack
The thread stack refers to stack information of thread scheduling in a memory at a certain moment, and a currently called method is generally positioned at the top of the thread stack. The contents of the thread stack are dynamically changed as the program runs.
3) Stack
The stack is two data structures. The stack is a data structure in which data items are arranged in sequence, and the data items can be inserted and deleted only at one end, namely the top of the stack.
4) Stack frame
A stack frame, which may also be referred to as a procedure activity record, is a data structure used by a compiler to implement a function call procedure. In the C language, each stack frame corresponds to a function that has not been run. Logically, a stack frame is an environment for function execution: function call frameworks, function parameters, local variables of functions, where the function returns after execution, and the like. The stack is extended from a high address to a low address. Each function call has its own independent stack frame, which maintains the required information. Register ebp points to the bottom of the current stack frame (high address) and register esp points to the top of the current stack frame (low address).
FIG. 1 is a schematic diagram illustrating a function execution performance monitoring system in accordance with an exemplary embodiment. The function execution performance monitoring system includes a first server 110, a second server 120, and a terminal 130.
The observed target application is a Java language developed application deployed on the first server 110.
The first server 110 may be a virtual machine, a physical server, or a Docker container.
The performance observation service is deployed on the second server 120.
The second server 120 may be a virtual machine, a physical server, or a Docker container in the same cluster as the observed target application.
The first server 110 and the second server 120 may include memories, which may be used to store stack information data collected by each function at each time point.
The terminal 130 may perform data transmission with the first server 110 and the second server 120 through a wired or wireless network.
The server 120 may be a server, or may be a server cluster composed of several servers, or may include one or more virtualization platforms, or may be a cloud computing service center.
The first server 110 and the second server 120 may be independent physical servers, may be a server cluster or a distributed system formed by a plurality of physical servers, or may be cloud servers. The terminal may be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like. The terminal and the server may be directly or indirectly connected through wired or wireless communication, and the application is not limited herein.
Optionally, the wired or wireless networks described above use standard communication techniques and/or protocols. The Network is typically the Internet, but may be any Network including, but not limited to, any combination of Local Area Networks (LANs), Metropolitan Area Networks (MANs), Wide Area Networks (WANs), mobile, wireless networks, private networks, or virtual private networks. In some embodiments, data exchanged over a network is represented using techniques and/or formats including Hypertext Mark-up Language (HTML), Extensible Markup Language (XML), and the like. All or some of the links may also be encrypted using conventional encryption techniques such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), Internet Protocol Security (IPsec). In other embodiments, custom and/or dedicated data communication techniques may also be used in place of, or in addition to, the data communication techniques described above.
FIG. 2 is a flow diagram illustrating a method of function execution performance monitoring in accordance with an exemplary embodiment. The function execution performance monitoring method can be applied to computer equipment, and the execution time of each function is determined by carrying out snapshot on stack information data of each time point, so that the purpose of judging whether each function is abnormal in execution is achieved. The computer device may be at least one of the first server 110 and the second server 120 of the system of fig. 1 described above. As shown in fig. 2, the function execution performance monitoring method may include the steps of:
in step 201, stack information data of a target thread stack at each time point is acquired; the target thread stack is a thread stack in the running process of the target application program; the stack information data is used to indicate a function called by the target application at a corresponding point in time.
In the embodiment of the present disclosure, in the process of running the target application program, the server acquires the stack information data of the target thread stack at each time point, and the stack information data corresponding to the same function is the same.
The server simultaneously acquires stack information data of the execution function for a plurality of running threads, and the sequence of the thread execution function is serial for the synchronously called target function. That is, a thread executes a synchronization function in a continuous time slice.
In step 202, the execution time of each function in the target thread stack is determined according to the stack information data at each time point.
In the embodiment of the disclosure, the server determines the execution time of each function in the target thread stack according to the stack information data at each time point.
And in a continuous time interval, if the stack frame of the target function is at the top of the thread stack and the contents of the whole stack frame of the thread are consistent, the target function is in execution. Otherwise, the target function execution is complete.
In step 203, according to the execution time of each function, the execution performance information of each function is obtained, and the execution performance information is used for indicating whether the corresponding function is abnormal in execution.
In the embodiment of the disclosure, the server determines the execution performance information of each function according to the acquired execution time of each function in the target application program, and indicates that the function is abnormal when the execution time is abnormal.
When at least one calling function in the target application program has execution abnormity, the target application program has execution abnormity.
In summary, the function execution performance monitoring method provided in the embodiment of the present disclosure. Through the scheme, the computer equipment determines the execution time of each function through the stack information data of each time point, so that the purpose of judging whether each function is abnormal to execute is achieved.
FIG. 3 is a flow diagram illustrating a method of function execution performance monitoring in accordance with another exemplary embodiment. The function execution performance monitoring method can be applied to computer equipment, and the execution time of each function is determined by carrying out snapshot on stack information data of each time point, so that the purpose of judging whether each function is abnormal in execution is achieved. The computer device may be at least one of the first server 110 and the second server 120 of the system of fig. 1 described above. As shown in fig. 3, the function execution performance monitoring method may include the steps of:
in step 301, specified configuration information is acquired.
In the embodiment of the present disclosure, the terminal acquires the specified configuration information input by the developer setting from the server or acquires the specified configuration information automatically allocated from the server.
The designated configuration information includes at least one of an acquisition time interval, an acquisition frequency, and an acquisition function range for acquiring stack information data. The stack information data is used to indicate a function called by the target application at a corresponding point in time. The acquisition time interval is used for indicating the time interval of the server side for acquiring the stack information data. The acquisition frequency is used for indicating the frequency of the server side for acquiring the stack information data. The collection function range is used for indicating the server end to collect stack information data of a specified code packet, a specified class name or a specified function name.
In a possible implementation manner, a developer inputs at least one of the specified configuration information through the performance observation interface, so that the specified configuration information is stored in the server, and the terminal acquires the specified configuration information from the server.
In another possible implementation manner, the server sends the specified configuration information corresponding to the target application program to the terminal, so that the terminal acquires the specified configuration information.
In step 302, stack information data of the target thread stack at various time points is obtained according to the specified configuration information.
In the embodiment of the present disclosure, the terminal acquires, according to the execution configuration information, stack information data at each time point on a target thread stack of the target application, and sends the stack information data at each time point to the server.
The target thread stack is a thread stack in the running process of the target application program.
In a possible implementation manner, when the designated configuration information includes an acquisition time interval, an acquisition frequency and an acquisition function range for acquiring the stack information data, in the acquisition time interval, the terminal acquires the stack information data belonging to the acquisition function range in the target thread stack according to the acquisition frequency.
In a possible implementation manner, a jstack command is periodically executed by using a Java Agent technology according to a specified collection time interval, collection frequency and collection function range, context information of a target thread stack in a target application program is acquired, and thus stack information data at each time point is acquired.
The jstack command is used for generating a thread snapshot of the Java virtual machine at the current moment. A thread snapshot is a collection of method stacks that are being executed by each thread within the current Java virtual machine.
In one possible implementation manner, in response to that the designated configuration information is automatically allocated by the server, the server acquires target attribute information corresponding to the target application program, then acquires the designated configuration information corresponding to the target attribute information, and finally acquires stack information data of the target thread stack at each time point according to the designated configuration information.
In one possible implementation, the target attribute information includes at least one of a target application identifier, a target application priority level, and a target application interface request latency. The method for respectively acquiring the designated configuration information based on the target application identifier, the target application priority level and the target application interface request time delay comprises the following steps:
1) and responding to the target attribute information containing the target application identification, acquiring the mapping relation between the target application identification and the specified configuration information, and acquiring the specified configuration information corresponding to the target application identification according to the mapping relation.
Each application program corresponds to a designated application identifier, a target application program corresponds to a target application identifier, each application identifier and each designated configuration information have a mapping relation, one application identifier corresponds to one designated configuration information, and each application identifier can correspond to the same designated configuration information.
For example, a mapping relationship table between each application identifier and each specific configuration information may be stored in advance in the database of the server, and the mapping relationship table may include that the specific configuration information corresponding to the application identifier "1" is the first specific configuration information, the specific configuration information corresponding to the application identifier "2" is the second specific configuration information, and the specific configuration information corresponding to the application identifier "3" is the first specific configuration information. When the acquired target application identifier is the application identifier "3", the first type of specific configuration information corresponding to the application identifier "3" may be acquired as the specific configuration information corresponding to the target application identifier.
2) And acquiring the appointed configuration information corresponding to the target application priority level in response to the target attribute information containing the target application priority level.
The target application priority level is positively correlated with the duration of the acquisition time interval, the acquisition frequency and the number of the function types of the acquisition function range. The detailed degree of the function required to be monitored by the target application can be determined based on the priority level of the target application, so that the higher the priority level of the target application is, the higher the detailed degree of the function required to be monitored is indicated, the longer the acquisition time interval in the corresponding appointed configuration information of the target application is, the higher the acquisition frequency is, and the larger the acquisition function range is; the lower the priority level of the target application is, the lower the level of detail of the function to be monitored is indicated, the shorter the acquisition time interval in the corresponding specified configuration information is, the lower the acquisition frequency is, and the smaller the acquisition function range is.
For example, the application priority level to which each application identifier belongs may be determined by the identity of each application program. The application priority levels may be divided into A, B, C, D four priority levels, with the application priority level being the highest at level a and the application priority level being the lowest at level D. Corresponding to A, B, C, D four priority levels, first, second, third and fourth designated profiles are stored, respectively. When the obtained target application identifier is the application identifier "3", it may be determined that the application priority level of the target application is the level a, and the first specific configuration information corresponding to the application priority level of the level a is the specific configuration information corresponding to the target application program.
3) And responding to the target attribute information including the target application interface request time delay, the server acquires the target application interface request time delay and the target application interface predicted request time delay, and determines a time delay difference value according to the target application interface request time delay and the target application interface predicted request time delay.
The time delay difference value is positively correlated with the time length of the acquisition time interval, the acquisition frequency and the function type number of the acquisition function range. The number of functions with function performance execution problems of the application program can be determined based on the time delay difference, so that the larger the time delay difference is, the more functions are indicated to be monitored, the longer the acquisition time interval in the corresponding specified configuration information is, the higher the acquisition frequency is, and the larger the acquisition function range is; the smaller the delay difference value is, the less functions which need to be monitored are indicated, the shorter the acquisition time interval in the corresponding specified configuration information is, the lower the acquisition frequency is, and the smaller the acquisition function range is.
For example, the application program is started to be executed by sending an external request to the application program interface, when the application program is executed, the request is returned to the application program interface, a time interval from the reception request to the return request obtained by statistics is determined as target application interface request delay, and interface request delay of each application program in normal operation is predicted request delay of the target application interface. When the request delay of the target application interface is larger than the expected request delay of the target application interface, it is indicated that at least one function has an execution performance problem in each function called in the execution process of the target application program, and because the delay difference value can indicate the influence degree of the execution performance problem in the target application program on the application program, the larger the delay difference value is, the more the functions to be monitored are indicated, the longer the acquisition time interval in the corresponding specified configuration information is, the higher the acquisition frequency is, and the larger the acquisition function range is. A specific threshold may be set, and when the obtained delay difference is greater than the specific threshold, the specific configuration information is determined to be the high-efficiency specific configuration information, and when the obtained delay difference is less than or equal to the specific threshold, the specific configuration information is determined to be the low-efficiency specific configuration information. When the obtained delay difference is greater than the specified threshold, the specified configuration information corresponding to the target application program can be determined to be the high-efficiency specified configuration information.
In another possible implementation manner, when the target attribute information includes at least two of a target application identifier, a target application priority level, and a target application interface request delay, the method for acquiring the specified configuration information is determined according to the priority of each target attribute information.
For example, the priority of each target attribute information may be that the priority of the target application identifier is greater than the target application interface request delay by more than the target application priority. And when the target attribute information simultaneously comprises the target application identifier and the target application interface request delay, the server acquires the specified configuration information according to the mapping relation between the target application identifier and the specified configuration information.
In step 303, the execution time of each function in the target thread stack is determined according to the stack information data at each time point.
In the embodiment of the present disclosure, the server calculates and determines the start execution time and the end execution time of each function in the target thread stack, respectively, based on the stack information data at each time point, and determines the execution time of each function in the target thread stack.
In a possible implementation manner, the server determines the collection number of consecutive stack information data having the same stack information data, and then acquires the consecutive time interval as the execution time of the objective function.
The stack information data are the same, namely that the stack frames positioned at the top of the target thread stack are the same and the contents of all the stack frames in the target thread stack are the same. The continuous time interval is the product of the number of continuous stack information data acquisitions minus one and the acquisition frequency.
Illustratively, since two consecutive snapshots contain the same method stack, it may be indicated that the method function is in an execution state during the time interval between the two consecutive snapshots. The execution time of the calculation function can be accumulated at statistical time intervals by means of continuous snapshots.
For example, fig. 4 is a schematic diagram of a function execution time prediction according to an embodiment of the disclosure. As shown in fig. 4, the collection time points at which snapshots of the thread stack are continuously taken are represented by d0 to d9, and by comparing the stack information data collected by d0 to d9, it can be determined that the stack information data obtained at each collection time point between the stack information data obtained at d4 and the stack information data obtained at d8 are the same, that is, the stack frames at the top of the target thread stack are the same and the contents of the respective stack frames in the target thread stack are the same, the function execution start time indicated by the top stack frame is between d3 and d4, and the function execution end time is between d8 and d9, so that the execution time prediction 41 of the function execution can be calculated as the interval duration from d4 to d 8.
In step 304, the execution performance information of each function is obtained according to the execution time of each function.
In the embodiment of the present disclosure, the server obtains the execution time of each function in the target application program, and obtains the execution performance information of each function according to the execution time of each function.
The execution performance information is used for indicating whether the corresponding function is abnormal in execution.
In one possible implementation, the execution exception of the function is determined in response to the execution time of the function being greater than a specified threshold.
When the server acquires the execution performance information of each function, the server may acquire the name or address information of the function of which the execution performance information indicates that the execution is abnormal.
In step 305, performance information of the target application program is acquired based on the execution performance information of each function.
In thatBook of JapaneseOpening deviceIn an embodiment, the server is based on obtainingGetTo the execution performance information of each function, canTo be provided withDetermining a function with execution exception in the target application program, when the execution performance information of each function indicates that the function with execution exception does not appear in the target application program, acquiring the performance information of the target application program is normal execution, and if the execution performance information of each function indicates that the function with execution exception appears in the target application program, acquiring the performance information of the target application program is execution exception.
In one possible implementation mode, in response to the fact that the target application program has an execution exception, the name of the function with the execution exception and corresponding alarm information are displayed on the terminal.
For example, fig. 5 is a schematic diagram of a time-consuming recording apparatus based on function call stack slicing according to an embodiment of the present disclosure. As shown in fig. 5, in the observed application, i.e., the target application, the Java Agent technology is applied (S51), and the jstack command is periodically executed to obtain the context information of the target thread stack from the Java application (S52). If the Java Agent program executes the jstack command to acquire the stack information data in the continuous time interval from d0 to d9 at the acquisition frequency of every 5 ms. Then, the obtained stack information data is sent to the performance observation server in batch through the Java Agent program and reported to the data collector of the performance observation server, the data collector stores the obtained data (S53), the data stored in the data collector is queried through the analysis calculator, the execution time consumption of each function in the Java application is calculated according to the function execution time algorithm, that is, the stored stack information data of 10 sampling points are compared in the time interval from d0 to d9, and a continuous time interval with the same stack is obtained, for example, the continuous time interval from d4 to d8 is shown in fig. 4. It can be calculated that the execution time of the function is a duration from d4 to d8, (8-4+1) × 5ms ═ 25ms (S54). When the alarm threshold value which takes a long time is set to be 500ms, if the time taken for a certain function call calculated by the analysis calculator exceeds 500ms, an alarm is given by means of mails or short messages (S55).
In one possible implementation manner, in response to receiving an instruction to collect stack information data, the stack information data of each function is collected by the Java Agent program, otherwise, the Java Agent program is in a standby state.
For example, fig. 6 is a schematic diagram of an on-demand collection time-consuming recording apparatus based on function call stack slices according to an embodiment of the present disclosure. As shown in fig. 6, after the performance observation server sends the instruction to collect stack information data (S61), a Java Agent program is used according to the designated configuration information set by the engineer responsible for performance observation at the performance observation server, where the designated configuration information specifically includes the collection frequency, the collection time interval, and the collected code, where the collected code may be a packet name, a class name, and a method in Java (S62). If the collection frequency is set to 20ms, the collection time interval is from 12 o ' clock 00S at 8 month and 10 th day in 2020 to 12 o ' clock 10 o ' clock 00S at 8 month and 10 th day in 2020, the collected codes are com.test.log. The collection by specifying the configuration information generates 10 × 60 × 1000(ms)/20ms 30000 collected stack information data (S64). And sending the acquired stack information data to the performance observation server in batches through the Java Agent program, reporting the stack information data to a data acquisition unit of the performance observation server, and storing the acquired data by the data acquisition unit (S65).
The analysis calculator queries the stack information data collected by the data collector, calculates the time consumed by executing the function according to algorithm segmentation (100 data in each segment) of the function execution time, for example, the first segment is d0 to d99, the stack information data of 100 sampling points are compared in the time interval from d0 to d99, a continuous time interval with the same stack information data is obtained, the time interval is assumed to be d20 to d49, the execution time of the function is the time duration from d20 to d49, and the execution time is (49-20+1) × 20ms is 600ms (S66). When the alarm threshold value which takes a long time is set to be 500ms, if the time taken for a certain function call calculated by the analysis calculator exceeds 500ms, an alarm is given by means of mails or short messages (S67).
In another possible implementation manner, the server monitors the interface response speed of the target application program, and in response to that the difference between the target application interface request delay received by the server and the target application interface expected request delay is greater than a specified threshold, at this time, the target application program interface response speed is slow, the execution of steps 301 to 304 is triggered, and then abnormal function information is output. Whether the target application program is abnormal in operation or not is preliminarily monitored by the server by preferentially monitoring the response speed of the target application program interface, useless monitoring of the server is avoided when the target application program is normally operated, and therefore consumption of system resources of the server is reduced.
In summary, the function execution performance monitoring method provided in the embodiment of the present disclosure. Through the scheme, the computer equipment determines the execution time of each function through the stack information data of each time point, so that the purpose of judging whether each function is abnormal to execute is achieved.
Fig. 7 is a block diagram illustrating a function execution performance monitoring apparatus according to an exemplary embodiment, and as shown in fig. 7, the function execution performance monitoring apparatus may be implemented as all or part of a computer device in hardware or a combination of hardware and software to execute all or part of the steps of the method shown in the corresponding embodiment of fig. 2 or 3. The function execution performance monitoring apparatus may include:
a data obtaining module 710, configured to obtain stack information data of the target thread stack at each time point; the target thread stack is a thread stack in the running process of a target application program; the stack information data is used for indicating a function called by the target application program at a corresponding time point;
a time determining module 720, configured to determine, according to the stack information data at each time point, an execution time of each function in the target thread stack;
a performance obtaining module 730, configured to obtain, according to the execution time of each function, execution performance information of each function, where the execution performance information is used to indicate whether the corresponding function is abnormal in execution.
In a possible implementation manner, the data obtaining module 710 includes:
the information acquisition submodule is used for acquiring appointed configuration information, and the appointed configuration information comprises at least one of acquisition time interval, acquisition frequency and acquisition function range for acquiring the stack information data;
and the data acquisition submodule is used for acquiring the stack information data of the target thread stack at each time point according to the specified configuration information.
In a possible implementation manner, the data obtaining module 710 includes:
the stack acquisition submodule is used for acquiring stack information data which belongs to the acquisition function range in the target thread stack according to the acquisition frequency in the acquisition time interval;
the time determination module 720 includes:
the quantity determining submodule is used for determining the continuous stack information data acquisition quantity with the same stack information data; the stack information data are the same, namely the stack frames positioned at the top of the target thread stack are the same and the contents of all the stack frames in the target thread stack are the same;
the time acquisition submodule is used for acquiring the continuous time interval as the execution time of the target function; the continuous time interval is the product of the number of continuous stack information data acquired minus one and the acquisition frequency.
In one possible implementation manner, the data obtaining sub-module includes:
the attribute acquiring unit is used for acquiring target attribute information corresponding to the target application program; the target attribute information comprises at least one of a target application identifier, a target application priority level and a target application interface request delay;
a configuration information obtaining unit, configured to obtain the specified configuration information corresponding to the target attribute information;
and the data acquisition unit is used for acquiring the stack information data of the target thread stack at each time point according to the specified configuration information.
In one possible implementation, in response to the target attribute information including the target application identification;
the configuration information obtaining unit is used for obtaining the configuration information,
acquiring a mapping relation between the target application identifier and the specified configuration information;
and acquiring the specified configuration information corresponding to the target application identifier according to the mapping relation.
In one possible implementation, the target application priority level is included in response to the target attribute information;
the configuration information obtaining unit is used for obtaining the configuration information,
acquiring the designated configuration information corresponding to the priority level of the target application; the target application priority level is positively correlated with the duration of the acquisition time interval, the acquisition frequency and the number of function types of the acquisition function range.
In one possible implementation, in response to the target attribute information including the target application interface request latency;
the configuration information obtaining unit is used for obtaining the configuration information,
acquiring the request time delay of the target application interface and the expected request time delay of the target application interface;
determining a delay difference value according to the request delay of the target application interface and the expected request delay of the target application interface; the time delay difference value is positively correlated with the time length of the acquisition time interval, the acquisition frequency and the function type number of the acquisition function range.
In summary, the function execution performance monitoring method provided in the embodiment of the present disclosure. Through the scheme, the computer equipment determines the execution time of each function through the stack information data of each time point, so that the purpose of judging whether each function is abnormal to execute is achieved.
It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the above functional modules is illustrated, and in practical applications, the above functions may be distributed by different functional modules according to actual needs, that is, the content structure of the device is divided into different functional modules, so as to complete all or part of the functions described above.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
FIG. 8 is a schematic diagram illustrating a configuration of a computer device, according to an example embodiment. The computer apparatus 800 includes a Central Processing Unit (CPU) 801, a system Memory 804 including a Random Access Memory (RAM) 802 and a Read-Only Memory (ROM) 803, and a system bus 805 connecting the system Memory 804 and the CPU 801. The computer device 800 also includes a basic Input/Output system (I/O system) 806, which facilitates transfer of information between devices within the computer device, and a mass storage device 807 for storing an operating system 813, application programs 814, and other program modules 815.
The basic input/output system 806 includes a display 808 for displaying information and an input device 809 such as a mouse, keyboard, etc. for user input of information. Wherein the display 808 and the input device 809 are connected to the central processing unit 801 through an input output controller 810 connected to the system bus 805. The basic input/output system 806 may also include an input/output controller 810 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input-output controller 810 also provides output to a display screen, a printer, or other type of output device.
The mass storage device 807 is connected to the central processing unit 801 through a mass storage controller (not shown) connected to the system bus 805. The mass storage device 807 and its associated computer device-readable media provide non-volatile storage for the computer device 800. That is, the mass storage device 807 may include a computer device readable medium (not shown) such as a hard disk or Compact Disc-Only Memory (CD-ROM) drive.
Without loss of generality, the computer device readable media may comprise computer device storage media and communication media. Computer device storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer device readable instructions, data structures, program modules or other data. Computer device storage media includes RAM, ROM, Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), CD-ROM, Digital Video Disk (DVD), or other optical, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer device storage media is not limited to the foregoing. The system memory 804 and mass storage 807 described above may be collectively referred to as memory.
The computer device 800 may also operate as a remote computer device connected to a network through a network, such as the internet, in accordance with various embodiments of the present disclosure. That is, the computer device 800 may be connected to the network 812 through the network interface unit 811 coupled to the system bus 805, or may be connected to other types of networks or remote computer device systems (not shown) using the network interface unit 811.
The memory further includes one or more programs, the one or more programs are stored in the memory, and the central processing unit 801 executes the one or more programs to implement all or part of the steps of the method shown in fig. 2 or fig. 3.
Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in embodiments of the disclosure may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-device-readable medium. Computer device readable media includes both computer device storage media and communication media including any medium that facilitates transfer of a computer device program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer device.
The embodiment of the present disclosure further provides a computer device storage medium, which is used for storing computer device software instructions for the testing apparatus, and includes a program designed for executing the function execution performance monitoring method.
According to an aspect of the present disclosure, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the function execution performance monitoring method provided in the various alternative implementations of the above aspects.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A method for monitoring performance of executing a function, the method comprising:
acquiring stack information data of a target thread stack at each time point; the target thread stack is a thread stack in the running process of a target application program; the stack information data is used for indicating a function called by the target application program at a corresponding time point;
determining the execution time of each function in the target thread stack according to the stack information data at each time point;
and acquiring execution performance information of each function according to the execution time of each function, wherein the execution performance information is used for indicating whether the corresponding function is abnormal in execution.
2. The method of claim 1, wherein the obtaining stack information data of the target thread stack at each time point comprises:
acquiring appointed configuration information, wherein the appointed configuration information comprises at least one of acquisition time interval, acquisition frequency and acquisition function range for acquiring the stack information data;
and acquiring the stack information data of the target thread stack at each time point according to the specified configuration information.
3. The method of claim 2, wherein the obtaining stack information data of the target thread stack at each time point comprises:
within the acquisition time interval, acquiring stack information data belonging to the acquisition function range in the target thread stack according to the acquisition frequency;
determining the execution time of each function in the target thread stack according to the stack information data at each time point, including:
determining the continuous stack information data acquisition quantity with the same stack information data; the stack information data are the same, namely the stack frames positioned at the top of the target thread stack are the same and the contents of all the stack frames in the target thread stack are the same;
acquiring a continuous time interval as the execution time of the target function; the continuous time interval is the product of the number of continuous stack information data acquired minus one and the acquisition frequency.
4. The method according to claim 2, wherein the obtaining stack information data of the target thread stack at each time point according to the specified configuration information comprises:
acquiring target attribute information corresponding to the target application program; the target attribute information comprises at least one of a target application identifier, a target application priority level and a target application interface request delay;
acquiring the specified configuration information corresponding to the target attribute information;
and acquiring the stack information data of the target thread stack at each time point according to the specified configuration information.
5. The method of claim 4, wherein in response to the target attribute information including the target application identification;
the obtaining of the specified configuration information corresponding to the target attribute information includes:
acquiring a mapping relation between the target application identifier and the specified configuration information;
and acquiring the specified configuration information corresponding to the target application identifier according to the mapping relation.
6. The method of claim 4, wherein in response to the target attribute information including the target application priority level;
the obtaining of the specified configuration information corresponding to the target attribute information includes:
acquiring the designated configuration information corresponding to the priority level of the target application; the target application priority level is positively correlated with the duration of the acquisition time interval, the acquisition frequency and the number of function types of the acquisition function range.
7. The method of claim 4, wherein in response to the target attribute information including the target application interface request latency;
the obtaining of the specified configuration information corresponding to the target attribute information includes:
acquiring the request time delay of the target application interface and the expected request time delay of the target application interface;
determining a delay difference value according to the request delay of the target application interface and the expected request delay of the target application interface; the time delay difference value is positively correlated with the time length of the acquisition time interval, the acquisition frequency and the function type number of the acquisition function range.
8. A function execution performance monitoring apparatus, comprising:
the data acquisition module is used for acquiring stack information data of the target thread stack at each time point; the target thread stack is a thread stack in the running process of a target application program; the stack information data is used for indicating a function called by the target application program at a corresponding time point;
a time determining module, configured to determine, according to the stack information data at each time point, an execution time of each function in the target thread stack;
and the performance acquisition module is used for acquiring the execution performance information of each function according to the execution time of each function, wherein the execution performance information is used for indicating whether the corresponding function is abnormal in execution.
9. A computer device comprising a processor and a memory, the memory having stored therein at least one instruction, at least one program, set of codes, or set of instructions, the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded and executed by the processor to implement the method of performing performance monitoring as claimed in any one of claims 1 to 7.
10. A computer-readable storage medium having at least one program code stored therein, the program code being loaded and executed by a processor to implement the method of function execution performance monitoring of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110853139.0A CN113608982A (en) | 2021-07-27 | 2021-07-27 | Function execution performance monitoring method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110853139.0A CN113608982A (en) | 2021-07-27 | 2021-07-27 | Function execution performance monitoring method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113608982A true CN113608982A (en) | 2021-11-05 |
Family
ID=78305668
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110853139.0A Pending CN113608982A (en) | 2021-07-27 | 2021-07-27 | Function execution performance monitoring method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113608982A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115794604A (en) * | 2022-10-14 | 2023-03-14 | 寒武纪行歌(南京)科技有限公司 | Data generation method, apparatus, device, medium, and program product |
| CN115858399A (en) * | 2023-02-09 | 2023-03-28 | 创智和宇信息技术股份有限公司 | Method and system for performing code-level performance analysis by using thread stack snapshot |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106445769A (en) * | 2015-08-11 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Computer operation monitoring method, device and system |
| US20170124319A1 (en) * | 2015-10-29 | 2017-05-04 | International Business Machines Corporation | Using call stack snapshots to detect anomalous computer behavior |
| CN109542719A (en) * | 2018-10-26 | 2019-03-29 | 金蝶软件（中国）有限公司 | Thread state monitoring method and device, computer equipment and storage medium |
| CN110457277A (en) * | 2019-08-19 | 2019-11-15 | 北京博睿宏远数据科技股份有限公司 | Service process performance analysis method, device, equipment and storage medium |
| CN111124791A (en) * | 2019-12-06 | 2020-05-08 | 深圳前海微众银行股份有限公司 | System testing method and device |
| CN112596938A (en) * | 2020-12-26 | 2021-04-02 | 中国农业银行股份有限公司 | Abnormity monitoring method and device |
| CN113032215A (en) * | 2021-03-24 | 2021-06-25 | 北京字节跳动网络技术有限公司 | Thread snapshot analysis method, device, equipment and storage medium |
-
2021
- 2021-07-27 CN CN202110853139.0A patent/CN113608982A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106445769A (en) * | 2015-08-11 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Computer operation monitoring method, device and system |
| US20170124319A1 (en) * | 2015-10-29 | 2017-05-04 | International Business Machines Corporation | Using call stack snapshots to detect anomalous computer behavior |
| CN109542719A (en) * | 2018-10-26 | 2019-03-29 | 金蝶软件（中国）有限公司 | Thread state monitoring method and device, computer equipment and storage medium |
| CN110457277A (en) * | 2019-08-19 | 2019-11-15 | 北京博睿宏远数据科技股份有限公司 | Service process performance analysis method, device, equipment and storage medium |
| CN111124791A (en) * | 2019-12-06 | 2020-05-08 | 深圳前海微众银行股份有限公司 | System testing method and device |
| CN112596938A (en) * | 2020-12-26 | 2021-04-02 | 中国农业银行股份有限公司 | Abnormity monitoring method and device |
| CN113032215A (en) * | 2021-03-24 | 2021-06-25 | 北京字节跳动网络技术有限公司 | Thread snapshot analysis method, device, equipment and storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115794604A (en) * | 2022-10-14 | 2023-03-14 | 寒武纪行歌(南京)科技有限公司 | Data generation method, apparatus, device, medium, and program product |
| CN115794604B (en) * | 2022-10-14 | 2024-04-19 | 寒武纪行歌(南京)科技有限公司 | Data generation method, device, equipment, medium and program product |
| CN115858399A (en) * | 2023-02-09 | 2023-03-28 | 创智和宇信息技术股份有限公司 | Method and system for performing code-level performance analysis by using thread stack snapshot |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9369521B2 (en) | Naming of distributed business transactions | |
| US10904112B2 (en) | Automatic capture of detailed analysis information based on remote server analysis | |
| CN108984366B (en) | Terminal monitoring processing method, device and equipment | |
| US20130080502A1 (en) | User interface responsiveness monitor | |
| CN109656782A (en) | Visual scheduling monitoring method, device and server | |
| CN113608982A (en) | Function execution performance monitoring method and device, computer equipment and storage medium | |
| CN110659109A (en) | Openstack cluster virtual machine monitoring system and method | |
| US20160226728A1 (en) | Automatic capture of detailed analysis information for web application outliers with very low overhead | |
| CN112306567B (en) | Cluster management system and container management and control method | |
| CN112328448A (en) | Zookeeper-based monitoring method, monitoring device, equipment and storage medium | |
| CN114356499A (en) | Kubernetes cluster alarm root cause analysis method and device | |
| CN111339118A (en) | Kubernetes-based resource change history recording method and device | |
| EP3852363A1 (en) | Device state monitoring method and apparatus | |
| CN115543746A (en) | Graphics processor monitoring method, system and device and electronic equipment | |
| CN115525392A (en) | Container monitoring method and device, electronic equipment and storage medium | |
| CN114371980A (en) | Call link performance monitoring method and device, computer equipment and storage medium | |
| CN114598622A (en) | Data monitoring method and device, storage medium and computer equipment | |
| CN112416698B (en) | Expansion method and device of monitoring system, storage medium and electronic equipment | |
| JP2018160020A (en) | Monitoring system, program and monitoring method | |
| CN108449343B (en) | SSH protocol text data acquisition method, acquisition device and computer equipment | |
| CN114884807A (en) | Link log generation method and device, Internet of things platform and storage medium | |
| CN116366508A (en) | Container exception handling method and device, processor and electronic equipment | |
| CN117785382A (en) | Resource monitoring and dynamic scheduling method, equipment and medium based on k8s cluster | |
| CN114090382A (en) | Health inspection method and device for super-converged cluster | |
| CN112615912A (en) | Node scheduling processing method and device 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 |