CN108933802B - Method and apparatus for monitoring operation - Google Patents
Method and apparatus for monitoring operation Download PDFInfo
- Publication number
- CN108933802B CN108933802B CN201710384821.3A CN201710384821A CN108933802B CN 108933802 B CN108933802 B CN 108933802B CN 201710384821 A CN201710384821 A CN 201710384821A CN 108933802 B CN108933802 B CN 108933802B
- Authority
- CN
- China
- Prior art keywords
- server
- record information
- information
- identifier
- monitoring
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
- G06F11/327—Alarm or error message display
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Alarm Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
Methods and apparatus for monitoring operations are disclosed. One embodiment of the method comprises: receiving at least one piece of recording information sent by a first server, wherein the recording information comprises a first operation identifier, and the first operation identifier is used for indicating that the first server requests a first operation executed by a second server; selecting record information from the received record information, wherein a first operation identifier in the selected record information is the same as a first target operation identifier, and the first target operation identifier is used for indicating a first target operation; determining parameter values of parameters for monitoring according to the selected record information; and generating and outputting alarm information in response to determining that the parameter value is not in a parameter value range which is set for the monitoring parameter in advance. This embodiment enriches the way in which operations are monitored.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to the field of internet technologies, and in particular, to a method and an apparatus for monitoring operations.
Background
With the development of internet technology, services provided through a network are increasingly diversified. The basis for supporting diversified services is the increasingly complex interaction between servers. In general, the functions of a server may be unified, and other servers may implement the functions by calling an interface of the server, i.e., requesting the server to perform operations to implement the functions, if necessary.
However, the conventional monitoring operation method generally monitors the server executing the function by the server calling the interface of the server, and thus, has a problem of single monitoring method.
Disclosure of Invention
The object of the present application is to propose an improved method and device for monitoring operation that solves the technical problems mentioned in the background section above.
In a first aspect, an embodiment of the present application provides a method for monitoring an operation, where the method includes: receiving at least one piece of recording information sent by a first server, wherein the recording information comprises a first operation identifier, and the first operation identifier is used for indicating the first server to request a first operation executed by a second server; selecting record information from the received record information, wherein a first operation identifier in the selected record information is the same as a first target operation identifier, and the first target operation identifier is used for indicating a first target operation; determining parameter values of parameters for monitoring according to the selected record information; and generating and outputting alarm information in response to the fact that the parameter value is not in a parameter value range which is set for the monitoring parameter in advance.
In a second aspect, an embodiment of the present application provides an apparatus for monitoring an operation, where the apparatus includes: the system comprises a first receiving unit, a second receiving unit and a processing unit, wherein the first receiving unit is used for receiving at least one piece of recording information sent by a first server, the recording information comprises a first operation identifier, and the first operation identifier is used for indicating that the first server requests a first operation executed by a second server; the device comprises a selecting unit, a judging unit and a judging unit, wherein the selecting unit is used for selecting the recording information from the received recording information, a first operation identifier in the selected recording information is the same as a first target operation identifier, and the first target operation identifier is used for indicating a first target operation; the determining unit is used for determining the parameter value of the parameter for monitoring according to the selected record information; and the first generation unit is used for responding to the condition that the parameter value is not in the parameter value range which is set for the monitoring parameter in advance, and generating and outputting alarm information.
In a third aspect, an embodiment of the present application provides a server, where the server includes: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out the method according to the first aspect.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor, implements the method according to the first aspect.
According to the method and the device for monitoring operation, the record information is selected from the record information which is sent by the first server and comprises the first operation identifier, the first operation identifier in the selected record information is the same as the first target operation identifier, then the parameter value of the parameter for monitoring is determined according to the selected record information, whether the parameter value is in the parameter value range which is set for the parameter for monitoring in advance is determined, if not, alarm information is generated and output, and therefore the first operation executed by the second server can be monitored, and the monitoring operation mode is enriched.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow diagram of one embodiment of a method for monitoring operation according to the present application;
FIG. 3 is a schematic diagram of an application scenario of a method for monitoring operation according to the present application;
FIG. 4 is a flow diagram of yet another embodiment of a method for monitoring operation according to the present application;
FIG. 5 is an exemplary system architecture diagram in which the method provided by the embodiment shown in FIG. 4 may be applied;
FIG. 6 is a schematic block diagram of one embodiment of an apparatus for monitoring operation according to the present application;
FIG. 7 is a block diagram of a computer system suitable for use in implementing a server according to embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the present method for monitoring operations or apparatus for monitoring operations may be applied.
As shown in fig. 1, the system architecture 100 may include backend servers 101, 102, 103, a network 104, and a monitoring server 105. The network 104 serves as a medium for providing communication links between the background servers 101, 102, 103 and the monitoring server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The background servers 101, 102, 103 may be servers providing various services, such as background web servers providing support for web pages displayed on the terminal. The backend servers 101, 102, 103 may interact with terminals used by users or other backend servers to receive or send messages or the like. The backend servers 101, 102, 103 may process data requests sent by terminals used by users or other backend servers. Also, the backend servers 101, 102, 103 may send data requests to other backend servers.
The monitoring server 105 may be a server that monitors operations performed by the backend servers, for example, the monitoring server 105 may monitor whether operations performed by other backend servers requested by the backend servers 101, 102, 103 are abnormal according to the record information sent by the backend servers 101, 102, 103, and may output alarm information if the operations are abnormal.
It should be noted that the method for monitoring operation provided by the embodiment of the present application is generally performed by the monitoring server 105, and accordingly, the apparatus for monitoring operation is generally disposed in the monitoring server 105.
It should be understood that the number of backend servers, network and monitoring servers in fig. 1 is merely illustrative. There may be any number of backend servers, network and monitoring servers, as desired for implementation.
With continued reference to FIG. 2, a flow 200 of one embodiment of a method for monitoring operation according to the present application is shown. The method for monitoring operation described above, comprising the steps of:
In this embodiment, the electronic device (e.g., the monitoring server shown in fig. 1) on which the method for monitoring operation operates may receive at least one piece of record information transmitted by the first server.
In this embodiment, the record information may include the first operation identifier. Here, the first operation identifier is used to indicate that the first server requests the second server to perform the first operation.
By way of example, the first operation may include, but is not limited to, an add-and-delete-and-check operation. Further, the first operation may be a specific add/delete/modify operation, for example, the first operation may be an operation that the first server requests the second server to perform a price inquiry on the product.
As an example, the first operation identification may be information for identifying the first operation. For example, the first operation identification may be used to identify the encoding of the first operation.
It should be noted that, the first server and the second server are both generic terms, and can be used to distinguish between a sender and a receiver of a data request. Here, there may be a plurality of pairs of the first server and the second server. The record information received by the monitoring server may come from a plurality of first servers.
It should be noted that the first server requests the operation performed by the second server, which may be referred to as a first operation. A first server may request a second server to perform a different first operation; a first server may request that multiple second servers perform different operations. Therefore, the first operation identifiers in the at least one piece of recorded information may be the same or different. As an example, a first server requests two operations from a second server, both of which may be referred to as first operations, both of which are identified by respective operations.
In this embodiment, the electronic device (e.g., the monitoring server shown in fig. 1) on which the method for monitoring operation is executed may select the log information from the received log information. Here, the first operation identifier in the selected record information is the same as the first target operation identifier. Here, the first target operation flag is used to indicate a first target operation.
And step 203, determining the parameter value of the parameter for monitoring according to the selected record information.
In this embodiment, the electronic device (for example, the monitoring server shown in fig. 1) on which the method for monitoring operation is executed may determine the parameter value of the parameter for monitoring according to the selected record information.
In some optional implementations of this embodiment, the parameter for monitoring may include, but is not limited to, one or more of the following: an execution failure rate, an average execution time, a longest execution time, a shortest execution time, and a number of executions within a predetermined period of time.
In some optional implementations of this embodiment, the logging information further includes information indicating success or failure of the second server to perform the first operation. Here, the second server executes the first operation, and the result returned to the first server may be returned result data, or may be regarded as information indicating that the second server executed the first operation successfully; or may be information returned indicating that the second server failed to perform the first operation.
In some optional implementations of this embodiment, step 203 may include: counting the number of pieces of target record information including information indicating that the second server performing the first target operation failed to perform the first target operation, from the selected record information. Determining an execution failure rate according to a ratio of the number of pieces of the target recording information to the number of pieces of the selected recording information. That is, the ratio of the number of pieces of target recording information to the number of pieces of selected recording information is determined as a parameter value of the execution failure rate.
In some optional implementations of this embodiment, the record information may further include a request sending time and a result returning time. Here, the request sending time is used to indicate a time when the first server sends the first data request including the first operation identifier to the second server. The result return time is used for indicating the time when the first server receives the result of executing the first operation returned by the second server.
In some optional implementations of this embodiment, step 203 may include: and for each piece of record information in the selected record information, determining the execution time length according to the request sending time and the result returning time in the piece of record information. And determining the average execution time length, the longest execution time length and the shortest execution time length according to the determined execution time length. That is, the parameter value for the average execution duration, the parameter value for the longest execution duration, and the parameter value for the shortest execution duration are determined.
As an example, the determined plurality of execution time periods may be averaged to obtain the longest execution time period. The longest execution duration and the shortest execution duration may be selected from the determined plurality of execution durations.
And step 204, responding to the fact that the parameter value is not in the parameter value range which is set for the monitoring parameter correspondingly in advance, and generating and outputting alarm information.
In this embodiment, an electronic device (e.g., a monitoring server shown in fig. 1) on which the method for monitoring operation is executed may generate and output alarm information in response to a determination that a parameter value of a parameter for monitoring is not within a parameter value range set in advance for the parameter for monitoring.
As an example, an execution failure rate range may be set in advance for the execution failure rate, for example, the execution failure rate range is 90% or more and 100% or less. If the execution failure rate is not within the range, alarm information is generated and sent out.
As an example, the average execution time length range may be set in advance for the average execution time length, and for example, the average execution time length may be 10 seconds or more and 20 seconds or less. If the average execution time length is not within the range, alarm information is generated and sent out.
In this embodiment, the alarm information may be information indicating that the monitoring parameter for the first target operation is abnormal.
With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the method for monitoring operation according to the present embodiment. In the application scenario of fig. 3, first, the first server 301 requests the second server 302 to perform a first operation. Then, the first server 301 sends the record information 304 including the first operation identification to the monitoring server 303. Then, the monitoring server 303 may select the record information from the received record information, where the first operation identifier in the selected record information 305 is the same as the first target operation identifier. Then, the monitoring server 303 may determine a parameter value 306 of the monitoring parameter from the selected record information 305. Finally, monitoring server 303 may generate and output alarm information 307 in response to determining that parameter value 306 is not within a parameter value range set in advance for the corresponding monitoring parameter.
In the method provided by the foregoing embodiment of the present application, the record information is selected from the record information including the first operation identifier sent by the first server, where the first operation identifier in the selected record information is the same as the first target operation identifier, then the parameter value of the parameter for monitoring is determined according to the selected record information, and it is determined whether the parameter value is within a parameter value range set in advance for the parameter for monitoring, and if not, the alarm information is generated and output, so that the first operation executed by the second server can be monitored, and the manner of monitoring operation is enriched.
With further reference to FIG. 4, a flow 400 of yet another embodiment of a method for monitoring operation is shown. The process 400 of the method for monitoring operation includes the steps of:
In this embodiment, the electronic device (e.g., the monitoring server shown in fig. 1) on which the method for monitoring operation operates may receive at least one piece of record information transmitted by the first server.
To facilitate the explanation of the present embodiment, please refer to fig. 5, which shows an exemplary system architecture to which the method provided by the present embodiment can be applied.
According to the system architecture shown in fig. 5, the terminal 501 may send the third operation identifier to the application server 502. Here, the third operation identifier is used to indicate that the terminal requests the third operation performed by the application server.
The application server 502 may send the application server information to the third server 503. Here, the application server information may include at least one of: an application server identification and a third operation identification.
The third server 503 may generate a second data request based on the third operation described above. The third server 503 may send the second data request to the first server 504. Here, the second data request may include a second operation identifier, where the second operation identifier is used to indicate that the third server requests the first server to perform the second operation.
One or more third servers 503 may be provided.
If there is one third server, the third server 503 generates the second data request based on the third operation, and may be implemented as follows: the third server 503 generates a second data request during the third operation.
If there are more than one third server, the third server 503 generates the second data request based on the third operation, and may be implemented as follows: the first server receiving the application server information transmitted by the application server may perform the third operation described above. The third server No. one may generate a new data request in the process of performing the third operation described above. The first third server may send the generated new data request to the second third server, and the second third server may generate a new data request when executing the new data request and send the new data request to the third server. By analogy, the last third server may generate the second data request when executing a certain data request.
The first server 504 may generate the first data request during the execution of the second operation. The first server 504 may send the first data request to the second server 505.
The first server 504 may also send the logging information to the monitoring server 506. Here, the log information may include the first operation identifier, the above-mentioned information indicating success or failure of the second server to perform the first operation, the request transmission time, the result return time, and the second data request. Here, the second data request may include the second operation identification and the application server information. Here, the application server information may include an application server identification and a third operation identification.
It can be seen that, in this embodiment, the record information may include the first operation identifier, information indicating success or failure of performing the first operation by the second server, a request sending time, a result returning time, the second operation identifier, the application server identifier, and the third operation identifier.
Here, the first operation identifier is used to indicate that the first server requests the second server to perform the first operation.
Here, the request sending time is used to indicate a time when the first server sends the first data request including the first operation identifier to the second server, and the result returning time is used to indicate a time when the first server receives a result of executing the first operation returned by the second server.
And step 403, determining parameter values of the parameters for monitoring according to the selected record information.
And step 404, generating and outputting alarm information in response to the fact that the parameter value is not in the parameter value range which is set for the monitoring parameter in advance.
Here, the operations of step 402, step 403 and step 404 are substantially the same as the operations of step 202, step 203 and step 204, and are not described again here.
In this embodiment, an electronic device (for example, a monitoring server shown in fig. 1) on which the method for monitoring operations is executed may generate, for each piece of record information in at least one piece of record information, an identification sequence corresponding to the piece of record information according to an execution sequence of operations indicated by a first operation identifier, a second operation identifier, and a third operation identifier in the piece of record information.
In some optional implementations of the embodiment, for each piece of record information in the at least one piece of record information, the identification sequence corresponding to the piece of record information may be a sequence arranged in the following order: the third operation identification, the first operation identification and the second operation identification.
In some optional implementations of the embodiment, for each piece of record information in the at least one piece of record information, the identification sequence corresponding to the piece of record information may be a sequence arranged in the following order: the device comprises an application server identifier, a third operation identifier, a first operation identifier and a second operation identifier.
In some optional implementation manners of this embodiment, the electronic device may further receive a time for requesting to execute a third operation and a time for returning a result of executing the third operation, which are sent by the application server, and may further determine a total time consumed for executing each operation in the identification sequence. And, the electronic device may monitor whether the total consumed time is within a preset total consumed time range, and if not, send out alarm information.
At step 406, a query request including an identification of a second target operation is received.
In this embodiment, an electronic device (e.g., the monitoring server shown in fig. 1) on which the method for monitoring operations operates may receive a query request including an identifier of the second target operation. Here, the second target operation flag may indicate a second target operation.
In some optional implementations of this embodiment, the query request may further include a target application server identifier.
In this embodiment, the electronic device (e.g., the monitoring server shown in fig. 1) on which the method for monitoring operation is executed may search for an identification sequence including the second target operation identification from the generated at least one identification sequence.
In some optional implementation manners of this embodiment, the electronic device may further find, from the found identifier sequence including the second target operation identifier, an identifier sequence including the target application server identifier.
In step 408, the operation identifier next to the second target operation identifier is obtained from the searched identifier sequence.
In this embodiment, the electronic device (for example, the monitoring server shown in fig. 1) on which the method for monitoring operation is executed may obtain the operation identifier located next to the second target operation identifier in the searched identifier sequence.
And step 409, outputting the acquired operation identifier.
In this embodiment, an electronic device (e.g., the monitoring server shown in fig. 1) on which the method for monitoring an operation is executed may output the acquired operation identification. The acquired operation identifier can be output to a terminal which can be used by a worker to acquire information, so that the worker can acquire the information from the terminal in time.
As can be seen from fig. 4, compared with the corresponding embodiment of fig. 2, the flow 400 of the method for monitoring operation in this embodiment highlights the steps of generating the identification sequence and further searching the operation identifier next to the second target operation identifier from the generated identification sequence. Therefore, the scheme described in the embodiment can introduce more keyword related data, so that more comprehensive candidate push information selection and more effective monitoring operation can be realized.
With further reference to fig. 6, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of an apparatus for monitoring operations, which corresponds to the method embodiment shown in fig. 2, and which is particularly applicable in various electronic devices.
As shown in fig. 6, the apparatus 600 for monitoring operation described above in this embodiment includes: a first receiving unit 601, a selecting unit 602, a determining unit 603 and a first generating unit 604. The first receiving unit is configured to receive at least one piece of recording information sent by a first server, where the recording information includes a first operation identifier, and the first operation identifier is used to indicate that the first server requests a first operation executed by a second server; the device comprises a selecting unit, a judging unit and a judging unit, wherein the selecting unit is used for selecting the recording information from the received recording information, a first operation identifier in the selected recording information is the same as a first target operation identifier, and the first target operation identifier is used for indicating a first target operation; the determining unit is used for determining the parameter value of the parameter for monitoring according to the selected record information; and the first generation unit is used for responding to the condition that the parameter value is not in the parameter value range which is set for the monitoring parameter in advance, and generating and outputting alarm information.
In this embodiment, specific processes of the first receiving unit 601, the selecting unit 602, the determining unit 603, and the first generating unit 604 and technical effects thereof can refer to the related descriptions of step 201, step 202, step 203, and step 204 in the corresponding embodiment of fig. 2, which are not repeated herein.
In some optional implementations of this embodiment, the recorded information further includes information for indicating that the second server has succeeded or failed in executing the first operation, and the parameter for monitoring includes an execution failure rate; and the determining unit is further configured to: counting the number of target record information from the selected record information, wherein the target record information comprises information for indicating that a second server executing the first target operation fails to execute the first target operation; determining an execution failure rate according to a ratio of the number of pieces of the target recording information to the number of pieces of the selected recording information.
In some optional implementations of this embodiment, the record information further includes a request sending time and a result returning time, where the request sending time is used to indicate a time when the first server sends the first data request including the first operation identifier to the second server, the result returning time is used to indicate a time when the first server receives a result of executing the first operation returned by the second server, and the parameter values for monitoring include an average execution duration, a longest execution duration, and a shortest execution duration; and the determining unit is further configured to: for each piece of record information in the selected record information, determining the execution duration according to the request sending time and the result returning time in the piece of record information; and determining the average execution time length, the longest execution time length and the shortest execution time length according to the determined execution time length.
In some optional implementations of this embodiment, the record information further includes a second data request sent by a third server to the first server, where the second data request includes a second operation identifier, the second operation identifier is used to indicate that the third server requests a second operation executed by the first server, and the first data request is sent by the first server to the second server in a process of executing the second operation.
In some optional implementations of this embodiment, the second data request further includes application server information sent by the application server to the third server, and the application server information includes at least one of: the application server identifier and a third operation identifier, wherein the third operation identifier is used for indicating that the terminal requests a third operation executed by the application server, and the second data request is generated by the third server according to the third operation; and the above apparatus further comprises: a second generating unit (not shown) configured to, for each piece of record information in the at least one piece of record information, generate an identifier sequence corresponding to the piece of record information according to an execution sequence of operations indicated by the first operation identifier, the second operation identifier, and the third operation identifier in the piece of record information.
In some optional implementations of this embodiment, the apparatus further includes: a second receiving unit (not shown) for receiving a query request including a second target operation identifier; a searching unit (not shown) configured to search, from the generated at least one identification sequence, for an identification sequence including the second target operation identification; an obtaining unit (not shown) configured to obtain, in the searched identifier sequence, an operation identifier located next to the second target operation identifier; an output unit (not shown) for outputting the acquired operation identifier.
It should be noted that, for details of implementation and technical effects of each unit in the apparatus for monitoring operation provided in this embodiment, reference may be made to descriptions of other embodiments in this application, and details are not described herein again.
Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use in implementing a server according to embodiments of the present application. The server shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program, when executed by a Central Processing Unit (CPU)701, performs the above-described functions defined in the method of the present application.
It should be noted that the computer readable medium mentioned above in the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a first receiving unit, a selecting unit, a determining unit, and a first generating unit. Here, the names of the units do not constitute a limitation to the units themselves in some cases, and for example, the first receiving unit may also be described as "a unit that receives at least one piece of recording information transmitted by the first server".
As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be present separately and not assembled into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: receiving at least one piece of recording information sent by a first server, wherein the recording information comprises a first operation identifier, and the first operation identifier is used for indicating the first server to request a first operation executed by a second server; selecting record information from the received record information, wherein a first operation identifier in the selected record information is the same as a first target operation identifier, and the first target operation identifier is used for indicating a first target operation; determining parameter values of parameters for monitoring according to the selected record information; and generating and outputting alarm information in response to the fact that the parameter value is not in a parameter value range which is set for the monitoring parameter in advance.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (10)
1. A method for monitoring operation, the method comprising:
receiving at least one piece of record information sent by a first server, wherein the record information comprises a first operation identifier, the first operation identifier is used for indicating that the first server requests a first operation executed by a second server, the record information further comprises a second data request sent by the third server to the first server, the second data request comprises a second operation identifier, the second operation identifier is used for indicating that the third server requests a second operation executed by the first server, the first data request is sent by the first server to the second server in the process of executing the second operation, the second data request further comprises application server information sent by an application server to the third server, and the application server information comprises at least one of the following items: the application server identification and the third operation identification are used for indicating that the terminal requests the third operation executed by the application server, and the second data request is generated by the third server according to the third operation;
selecting record information from the received record information, wherein a first operation identifier in the selected record information is the same as a first target operation identifier, and the first target operation identifier is used for indicating a first target operation;
determining parameter values of parameters for monitoring according to the selected record information;
and generating and outputting alarm information in response to determining that the parameter value is not in a parameter value range which is set for the monitoring parameter in advance.
2. The method of claim 1, wherein the logging information further comprises information indicating success or failure of the second server to perform the first operation, and the parameter for monitoring comprises a rate of failure of the performing; and
the determining the parameter value of the parameter for monitoring according to the selected record information includes:
counting the number of target record information from the selected record information, wherein the target record information comprises information used for indicating that a second server executing the first target operation fails to execute the first target operation;
determining an execution failure rate according to a ratio of the number of pieces of the target recording information to the number of pieces of the selected recording information.
3. The method according to claim 2, wherein the recorded information further comprises a request sending time and a result returning time, wherein the request sending time is used for indicating the time when the first server sends the first data request comprising the first operation identifier to the second server, the result returning time is used for indicating the time when the first server receives the result of executing the first operation returned by the second server, and the parameter values for monitoring comprise an average execution time length, a longest execution time length and a shortest execution time length; and
the determining the parameter value of the parameter for monitoring according to the selected record information includes:
for each piece of record information in the selected record information, determining the execution duration according to the request sending time and the result returning time in the piece of record information;
and determining the average execution time length, the longest execution time length and the shortest execution time length according to the determined execution time length.
4. The method of claim 1, further comprising:
and for each piece of record information in the at least one piece of record information, generating an identification sequence corresponding to the piece of record information according to the sequence of operation execution indicated by the first operation identification, the second operation identification and the third operation identification in the piece of record information.
5. The method of claim 4, further comprising:
receiving a query request comprising a second target operation identifier;
searching for an identification sequence comprising the second target operation identification from the generated at least one identification sequence;
obtaining an operation identifier positioned next to the second target operation identifier in the searched identifier sequence;
and outputting the acquired operation identification.
6. An apparatus for monitoring operation, the apparatus comprising:
the recording information comprises a first operation identifier, wherein the first operation identifier is used for indicating that the first server requests a first operation executed by a second server, the recording information further comprises a second data request sent by the third server to the first server, the second data request comprises a second operation identifier, the second operation identifier is used for indicating that the third server requests a second operation executed by the first server, the first data request is sent by the first server to the second server in the process of executing the second operation, the second data request further comprises application server information sent by an application server to the third server, and the application server information comprises at least one of the following items: the application server identification and the third operation identification are used for indicating that the terminal requests the third operation executed by the application server, and the second data request is generated by the third server according to the third operation;
the device comprises a selecting unit, a judging unit and a judging unit, wherein the selecting unit is used for selecting the recording information from the received recording information, a first operation identifier in the selected recording information is the same as a first target operation identifier, and the first target operation identifier is used for indicating a first target operation;
the determining unit is used for determining the parameter value of the parameter for monitoring according to the selected record information;
and the first generation unit is used for responding to the fact that the parameter value is not in a parameter value range which is set for the monitoring parameter in advance correspondingly, and generating and outputting alarm information.
7. The apparatus of claim 6, further comprising:
and the second generating unit is used for generating an identification sequence corresponding to each piece of record information in the at least one piece of record information according to the execution sequence of the operation indicated by the first operation identification, the second operation identification and the third operation identification in the piece of record information.
8. The apparatus of claim 7, further comprising:
the second receiving unit is used for receiving a query request comprising a second target operation identifier;
a searching unit, configured to search for an identification sequence including the second target operation identification from the generated at least one identification sequence;
an obtaining unit, configured to obtain, in the found identifier sequence, an operation identifier located next to the second target operation identifier;
and the output unit is used for outputting the acquired operation identifier.
9. A server, characterized in that the server comprises:
one or more processors;
a storage device for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method recited in any of claims 1-5.
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-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710384821.3A CN108933802B (en) | 2017-05-26 | 2017-05-26 | Method and apparatus for monitoring operation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710384821.3A CN108933802B (en) | 2017-05-26 | 2017-05-26 | Method and apparatus for monitoring operation |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108933802A CN108933802A (en) | 2018-12-04 |
| CN108933802B true CN108933802B (en) | 2022-03-01 |
Family
ID=64450334
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710384821.3A Active CN108933802B (en) | 2017-05-26 | 2017-05-26 | Method and apparatus for monitoring operation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108933802B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110187987B (en) * | 2019-06-05 | 2022-02-25 | 北京百度网讯科技有限公司 | Method and apparatus for processing requests |
| CN112650640B (en) * | 2019-10-12 | 2022-09-20 | 武汉斗鱼网络科技有限公司 | Program monitoring method and device, server and computer storage medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9967169B2 (en) * | 2009-09-30 | 2018-05-08 | Red Hat, Inc. | Detecting network conditions based on correlation between trend lines |
| CN102110220B (en) * | 2011-02-14 | 2013-01-23 | 宇龙计算机通信科技(深圳)有限公司 | Application program monitoring method and device |
| CN102609346B (en) * | 2012-01-16 | 2014-12-03 | 深信服网络科技（深圳）有限公司 | Monitoring method and monitoring device on basis of service operation |
| CN103617038B (en) * | 2013-11-28 | 2018-10-02 | 北京京东尚科信息技术有限公司 | A kind of service monitoring method and device of distribution application system |
| CN104866296B (en) * | 2014-02-25 | 2019-05-28 | 腾讯科技（北京）有限公司 | Data processing method and device |
| CN106506471A (en) * | 2016-10-31 | 2017-03-15 | 百度在线网络技术（北京）有限公司 | Application control method and device |
-
2017
- 2017-05-26 CN CN201710384821.3A patent/CN108933802B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108933802A (en) | 2018-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110708346B (en) | Information processing system and method | |
| CN108933695B (en) | Method and apparatus for processing information | |
| CN110377440B (en) | Information processing method and device | |
| CN111177433B (en) | Method and apparatus for parallel processing of information | |
| CN109388626A (en) | Method and apparatus for being numbered to traffic assignments | |
| CN110737655B (en) | Method and device for reporting data | |
| CN109218041B (en) | Request processing method and device for server system | |
| CN108933802B (en) | Method and apparatus for monitoring operation | |
| CN109992719B (en) | Method and apparatus for determining push priority information | |
| CN114840379A (en) | Log generation method, device, server and storage medium | |
| CN111125503B (en) | Method and apparatus for generating information | |
| CN109873731B (en) | Test method, device and system | |
| CN107315672B (en) | Method and device for monitoring server | |
| CN109218338B (en) | Information processing system, method and device | |
| CN109471713B (en) | Method and device for inquiring information | |
| CN110928594A (en) | Service development method and platform | |
| US11121912B2 (en) | Method and apparatus for processing information | |
| CN114465919B (en) | Network service testing method, system, electronic equipment and storage medium | |
| CN111131359A (en) | Method and apparatus for generating information | |
| CN108811036B (en) | Method and apparatus for displaying wireless access point information | |
| CN109978644B (en) | Information processing method, device and system | |
| CN108494982B (en) | Method and apparatus for generating information | |
| CN111831530A (en) | Test method and device | |
| CN115309612B (en) | Method and device for monitoring data | |
| CN113282471B (en) | Equipment performance testing method and device and terminal equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |