CN110351131B - Monitoring method and device for distributed link and electronic equipment - Google Patents
Monitoring method and device for distributed link and electronic equipment Download PDFInfo
- Publication number
- CN110351131B CN110351131B CN201910572683.0A CN201910572683A CN110351131B CN 110351131 B CN110351131 B CN 110351131B CN 201910572683 A CN201910572683 A CN 201910572683A CN 110351131 B CN110351131 B CN 110351131B
- Authority
- CN
- China
- Prior art keywords
- data
- application component
- distributed link
- data acquisition
- distributed
- 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
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- 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/10—Protocols in which an application is distributed across nodes in the network
Abstract
The invention discloses a monitoring method and a monitoring device for a distributed link, electronic equipment and a computer-readable storage medium, which are characterized by comprising the following steps: and arranging a data collector based on each application component in the distributed link, acquiring data of each application component in operation through the data collector, counting and analyzing the data, and feeding back the counting and analyzing results. The invention realizes the purposes of rapid positioning, comprehensive monitoring, cooperative analysis and clear display of the running condition of each application component in the distributed link in a low-invasive, transparent application and low-loss mode.
Description
Technical Field
The present invention relates to the field of computer information processing, and in particular, to a monitoring method and apparatus for a distributed link, an electronic device, and a computer-readable medium.
Background
With the expansion of internet architecture, distributed systems become increasingly complex, and more components begin to be distributed, such as microservices, messaging, distributed databases, distributed caches, distributed object storage, and cross-domain calling, and these components together form a complicated distributed network. The more services are deployed, the more complicated and complicated calling relationship is, and it is very difficult to find codes where some bottlenecks are located and analyze the abnormal conditions in the calling of multiple services from deep level. After a request passes through these services, a call failure problem occurs, and only the exception is known, but the specific exception needs to enter each service to see the log when the exception is caused by which service, so the processing efficiency is very low.
Based on the existing problems, a new technical scheme is needed, and the purposes of rapid positioning, comprehensive monitoring, collaborative analysis and clear display of the operating condition of each application component in a distributed link are realized in a low-invasive, application-transparent and low-loss mode.
Disclosure of Invention
The main objective of the present invention is to provide a monitoring method, an apparatus, an electronic device, and a computer-readable storage medium for a distributed link, which aim to achieve the purposes of rapid positioning, comprehensive monitoring, collaborative analysis, and explicit demonstration of the operating condition of each application component in the distributed link in a low-intrusive, application-transparent, and low-loss manner.
The foregoing objects are not achieved, and an aspect of the present invention provides a method for monitoring a distributed link, including:
setting a data collector based on each application component in the distributed link;
acquiring data of each application component in operation through the data acquisition unit;
carrying out statistics and analysis processing on the data;
and feeding back the statistics and analysis processing results.
According to a preferred embodiment of the present invention, the data collector organizes the data collection rule during the class loading period of each application component to obtain data during the operation of each application component.
According to a preferred embodiment of the present invention, the data collection rule only makes collection calls to the middleware formed when the application components run.
According to a preferred embodiment of the invention: and each application component in the distributed link is respectively and uniquely provided with one data acquisition unit correspondingly.
According to a preferred embodiment of the present invention, the data collector generates tag information for marking the data collector while acquiring the operation data of each application component.
According to a preferred embodiment of the present invention, the tag information further may include a tracking identifier and call log information.
According to a preferred embodiment of the present invention, the data collector outputs the acquired data and the tag information, and further performs statistics and analysis processing.
According to a preferred embodiment of the present invention, the data of each application component during operation further may include the application component survival status data, interface call information data, and the like.
According to a preferred embodiment of the present invention, by analyzing the runtime data of the application component, an alarm is given when a problem occurs during the running process of the application component, and the alarm is displayed in a visual manner.
According to a preferred embodiment of the present invention, tracking and positioning in a distributed link can be realized by matching the data with the tag information.
A second aspect of the present invention provides a monitoring apparatus for a distributed link, comprising:
the data acquisition device setting module is used for setting a data acquisition device based on each application component in the distributed link;
the data collector is used for obtaining data of each application component during operation;
the data processing module is used for counting and analyzing the data;
the summarizing storage module is used for storing the data, the statistics and the analysis processing results;
and the feedback display module is used for displaying the statistical and analysis processing result.
According to a preferred embodiment of the present invention, the data acquisition unit organizes the data acquisition rules during the class loading period of each application component to form a data capture unit, so as to obtain data during the operation of each application component.
According to a preferred embodiment of the present invention, the data fetch unit only makes collection calls to the middleware formed when the application components are running.
According to a preferred embodiment of the present invention, the data collector uniquely corresponds to an application component in the distributed link.
According to a preferred embodiment of the present invention, the data collector generates tag information for marking the data collector while acquiring the operation data of each application component.
According to a preferred embodiment of the present invention, the tag information further includes a tracking identifier and call log information.
According to a preferred embodiment of the present invention, the data collector outputs the collected data and the tag information to a data processing module; and the data processing module carries out statistics and analysis processing.
According to a preferred embodiment of the present invention, the data of each application component during operation further may include the application component survival status data, interface call information data, and the like.
According to a preferred embodiment of the present invention, the feedback display module may alarm and visually display a problem occurring during the operation of the application component, which is found by the data processing module analyzing the runtime data of the application component.
According to a preferred embodiment of the present invention, the feedback presentation module may be used to perform tracking and positioning in a distributed link based on unique matching between the data and the tag information.
A third aspect of the present invention provides an electronic apparatus, wherein the electronic apparatus comprises:
a processor; and a memory storing computer executable instructions that, when executed, cause the processor to perform the monitoring method for a distributed link described above.
A fourth aspect of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs which, when executed by a processor, implement the above-described monitoring method for a distributed link.
Drawings
In order to make the technical problems solved by the present invention, the technical means adopted and the technical effects obtained more clear, the following will describe in detail the embodiments of the present invention with reference to the accompanying drawings. It should be noted, however, that the drawings described below are only illustrations of exemplary embodiments of the invention, from which other embodiments can be derived by those skilled in the art without inventive faculty.
FIG. 1 is a flow chart of a monitoring method for a distributed link according to the present invention;
FIG. 2 is a diagram of a typical distributed link;
FIG. 3 is a schematic diagram of a data collector using the Tomcat system as an example;
FIG. 4 is a simplified illustration of the monitoring method of the present invention applied to a distributed link;
FIG. 5 is a schematic diagram of a monitoring device framework for a distributed link of the present invention;
FIG. 6 is a schematic diagram of a monitoring electronics architecture framework for distributed links of the present invention;
FIG. 7 is a schematic diagram of a computer readable storage medium of the present invention.
Detailed Description
Exemplary embodiments of the present invention will now be described more fully with reference to the accompanying drawings. The exemplary embodiments, however, may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art. The same reference numerals denote the same or similar elements, components, or parts in the drawings, and thus their repetitive description will be omitted.
Features, structures, characteristics or other details described in a particular embodiment do not preclude the fact that the features, structures, characteristics or other details may be combined in a suitable manner in one or more other embodiments in accordance with the technical idea of the invention.
In describing particular embodiments, the present invention has been described with reference to features, structures, characteristics or other details that are within the purview of one skilled in the art to provide a thorough understanding of the embodiments. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific features, structures, characteristics, or other details.
The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
It will be understood that, although the terms first, second, third, etc. may be used herein to describe various elements, components, or sections, these terms should not be construed as limiting. These phrases are used to distinguish one from another. For example, a first device may also be referred to as a second device without departing from the spirit of the present invention.
The term "and/or" and/or "includes any and all combinations of one or more of the associated listed items.
Fig. 1 is a schematic flow chart of a monitoring method for a distributed link according to the present invention, and as shown in fig. 1, the method of the present invention includes the following steps:
s101: data acquisition unit based on application components in distributed link
A typical distributed link diagram is shown in fig. 2. In a distributed link, there are several application components whose topology is in a grid-like shape. Each application component in the distributed link structure is both a service provider for other application components and a service object for other application components.
And arranging a data acquisition unit based on each application component in the distributed link, wherein the data acquisition unit organizes the data acquisition rule during the class loading period of each application component so as to acquire data during the operation of each application component. In order to realize low invasiveness and not influence the service codes of each specific application component, the data acquisition unit does not weave acquisition rules into a system loader provided by a system based on the application components, and only weaves the acquisition rules into the loading period of a user-defined class loader of the application components.
Furthermore, a data collector is arranged on each application component by utilizing java's instrumentation technology. Taking the Tomcat system as an example, as shown in fig. 3, the Tomcat system has a boot class loader, a system class loader, and a common class loader provided by the system, and does not need to organize the data collection rules during the loading of the class loader provided by the system, but to organize the corresponding data collection rules during the loading of the specific web application class loader, in order to achieve low intrusiveness to the application components.
Xml specifically configures and generates parameters of a listener of the data collector, the listener utilizes a Tomcat type loading organizer to organize collection rules into byte codes loaded by the original supply components, and a transform method is called to convert and form new byte codes loaded by the supply components. And the Web application class loader loads the converted new bytecode to realize data acquisition during the operation of the Web application component.
Furthermore, each application component is uniquely corresponding to one data collector each time, that is, one data collector is only specially used for a specific call of one application component, and only one data collector is used for data collection of one specific call of one application component.
S102: the data collector obtains the data of each application component in operation
The data acquisition unit organizes data acquisition rules in the byte codes required to be called by the application components, and the application components automatically acquire the relevant data of the application components in operation after loading new byte codes.
As described in step S101, each application component is uniquely configured to correspond to one data collector each time. The data acquisition rule generates tag information that identifies the data acquisition device while collecting data.
The tag information may specifically be a trace log, including a unique tag global id (traceid) in a call, trace information span id for tracing each calling node (method) in a call of a complete call chain, and a call log. The call log is formatted trace information for describing a call condition of the method, and the call condition may specifically include information such as a start time of the call, a call type, a protocol type, an ip and a port of a caller, a service name of the request, and the like.
The whole call chain can be concatenated by global IDs, one global ID represents one request; the span ID is used for recording calling parent-child relationship, each service can record global ID and span ID, and all position relationships of a complete calling chain can be completely recorded once through the span ID and the span ID, so that accurate positioning in a distributed link is realized.
Furthermore, the specific data collected by the data collector is collected and called for the middleware formed in the running of each application component, and the data formed in the running of the inside of each application component is not influenced.
S103: the data are processed by statistics and analysis
And the data collector outputs the collected data of the application component in operation and the formed label information, and further performs statistics and analysis processing.
The label information called by each application component corresponds to the data formed by the current application component uniquely, and through the statistics and analysis processing of the label information, the survival condition of the application component, the response time of the calling service, the calling type, the protocol type, the calling time, the calling party IP and other aspects can be clearly positioned and mastered
S104: feeding back the statistical and analytical processing results
By analyzing the runtime data of the application components, the runtime conditions of the components can be clearly displayed for development and users in a visual mode; and alarming when a problem occurs in the operation process of the application component so as to remind developers and managers of correcting in time. In addition, through the unique corresponding relation of the label information and the data formed by the application components, the problem (slow interface and error interface) can be quickly positioned and solved by the aid of developers in the minute-level problem query.
As shown in fig. 4, based on the above method, a full platform distributed link monitoring can be implemented, which may specifically include URL and port monitoring, Jvm monitoring, local call link and remote call link monitoring, Dubbo service survival monitoring, and other custom monitoring.
Wherein, URL and port monitoring mainly monitors URL interface and port survivability;
jvm monitoring can collect data, provide optimization basis and save cost;
the local call link and the remote call link monitor are used for tracking the remote call link and the local call link and monitoring, alarming and displaying indexes such as corresponding time, times, availability and the like of the call units in the links;
the Dubbo service survival monitoring can monitor for Dubbo service node changes;
other custom monitoring can be used to implement monitoring alarm and information viewing in a scene that satisfies conditions in a program.
Those skilled in the art will appreciate that all or part of the steps to implement the above-described embodiments are implemented as programs (computer programs) executed by a computer data processing apparatus. When the computer program is executed, the method provided by the invention can be realized. Furthermore, the computer program may be stored in a computer readable storage medium, which may be a readable storage medium such as a magnetic disk, an optical disk, a ROM, a RAM, or a storage array composed of a plurality of storage media, such as a magnetic disk or a magnetic tape storage array. The storage medium is not limited to centralized storage, but may be distributed storage, such as cloud storage based on cloud computing.
Embodiments of the apparatus of the present invention are described below, which may be used to perform method embodiments of the present invention. The details described in the device embodiments of the invention should be regarded as complementary to the above-described method embodiments; reference is made to the above-described method embodiments for details not disclosed in the apparatus embodiments of the invention.
Fig. 5 is a schematic diagram of a monitoring device framework for a distributed link of the present invention. As shown in fig. 5, the monitoring device of the present invention includes:
the listener 501 is configured to generate a data collection 502 based on each invocation of each application component in the distributed link, and the data collection 502 organizes the person data capturing unit 5021 during class loading of each application component to obtain data of each application component during running. In order to realize low invasiveness and not influence the service codes of each specific application component, the data acquisition unit does not weave acquisition rules into a system loader provided by a system based on the application components, and only weaves the acquisition rules into the loading period of a user-defined class loader of the application components.
Furthermore, a data collector is arranged on each application component by utilizing java's instrumentation technology. Taking the Tomcat system as an example, the Tomcat system has a boot class loader, a system class loader, and a common class loader provided by the system, and in order to achieve low intrusiveness to the application components, it is not necessary to organize the data fetch unit 5021 during the loading of the class loader provided by the system, and to organize the corresponding data fetch unit 5021 during the loading of the specific web application class loader.
Xml specifically configures to generate parameters of the listener 501 of the data collector 502, and the listener 501 uses a Tomcat type loading organizer to organize collection rules into the bytecode loaded by the original provisioning component, and calls a transform method to convert into a new bytecode used by the provisioning component loading. And the Web application class loader loads the converted new bytecode to realize data acquisition during the operation of the Web application component.
Furthermore, each application component is uniquely corresponding to one data collector each time, that is, one data collector is only specially used for a specific call of one application component, and only one data collector is used for data collection of one specific call of one application component.
The data acquisition unit 502 organizes the data capture unit 5021 in the bytecode that the application component needs to call, and the application component automatically acquires the relevant data during the operation of the application component after loading the new bytecode, and it should be particularly noted that the relevant data during the operation is the middleware that is formed during the operation of each application component and can be exchanged and recorded, and does not need to bring much influence to the operation of the component.
As described above, each application component is uniquely associated with one data collector per deployment. The data acquisition rule generates tag information that identifies the data acquisition device while collecting data.
The tag information may specifically be a trace log, including a unique tag global id (traceid) in a call, trace information span id for tracing each calling node (method) in a call of a complete call chain, and a call log. The call log is formatted trace information for describing a call condition of the method, and the call condition may specifically include information such as a start time of the call, a call type, a protocol type, an ip and a port of a caller, a service name of the request, and the like.
The whole call chain can be concatenated by global IDs, one global ID represents one request; the span ID is used for recording calling parent-child relationship, each service can record global ID and span ID, and all position relationships of a complete calling chain can be completely recorded once through the span ID and the span ID, so that accurate positioning in a distributed link is realized.
Further, the specific data collected by the data collector 502 is collected and called for the middleware formed during the operation of each application component, without affecting the data formed during the internal operation of each application component.
The data collector 502 outputs the collected data of the application component during operation and the formed tag information to the data processing module 502, and further performs statistics and analysis processing. Further, the data processing module may include a statistics unit 5031, a subtask processing unit 5032; wherein the statistic unit 5031 can be used for carrying out statistics on the received data, and the subtask processing system 5032 can be used for carrying out analysis and processing on the received data as required.
The label information called by each application component corresponds to the data formed by the current application component uniquely, and the survival condition of the application component, the response time of calling service, the calling type, the protocol type, the calling time, the IP of the calling party and other aspects can be clearly positioned and mastered through the statistics and analysis processing of the label information.
And the summarizing and storing module 504 is used for storing the data acquired by the data processing module 502 and the statistical and analytical processing results of the data processing module 503. The summary storage module 504 may be a key-value database, a distributed file storage database, a distributed time sequence and index database, etc., and may be searched using a distributed multi-user capability search engine such as an ElasticSearch type.
The feedback display module 504 can clearly display the operation conditions of all the components to development and use personnel in a visual mode; and alarming when a problem occurs in the operation process of the application component so as to remind developers and managers of correcting in time. In addition, through the unique corresponding relation of the label information and the data formed by the application components, the problem (slow interface and error interface) can be quickly positioned and solved by the aid of developers in the minute-level problem query.
Those skilled in the art will appreciate that the modules in the above-described embodiments of the apparatus may be distributed as described in the apparatus, and may be correspondingly modified and distributed in one or more apparatuses other than the above-described embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
In the following, embodiments of the electronic device of the present invention are described, which may be regarded as specific physical implementations for the above-described embodiments of the method and apparatus of the present invention. Details described in the embodiments of the electronic device of the invention should be considered supplementary to the embodiments of the method or apparatus described above; for details which are not disclosed in embodiments of the electronic device of the invention, reference may be made to the above-described embodiments of the method or the apparatus.
Fig. 6 is a block diagram of an exemplary embodiment of an electronic device according to the present invention. An electronic device 600 according to this embodiment of the invention is described below with reference to fig. 6. The electronic device 600 shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 7, the electronic device 600 is embodied in the form of a general purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 that connects the various system components (including the storage unit 620 and the processing unit 610), a display unit 640, and the like.
Wherein the storage unit stores program code executable by the processing unit 610 to cause the processing unit 610 to perform steps according to various exemplary embodiments of the present invention described in the above-mentioned electronic prescription flow processing method section of the present specification. For example, the processing unit 610 may perform the steps as shown in fig. 1.
The storage unit 620 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)6201 and/or a cache memory unit 6202, and may further include a read-only memory unit (ROM) 6203.
The memory unit 620 may also include a program/utility 6204 having a set (at least one) of program modules 6205, such program modules 6205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 600, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 600 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 650. Also, the electronic device 600 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via the network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 via the bus 630. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments of the present invention described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiment of the present invention can be embodied in the form of a software product, which can be stored in a computer-readable storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to make a computing device (which can be a personal computer, a server, or a network device, etc.) execute the above-mentioned method according to the present invention. The computer program, when executed by a data processing apparatus, enables the computer readable medium to carry out the above-described methods of the invention.
The computer program may be stored on one or more computer readable media. The computer readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, 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.
The computer readable storage medium may include a propagated data signal with 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 readable storage medium may also be any readable medium that is not a 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 readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
In summary, the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that some or all of the functionality of some or all of the components in embodiments in accordance with the invention may be implemented in practice using a general purpose data processing device such as a microprocessor or a Digital Signal Processor (DSP). The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
While the foregoing embodiments have described the objects, aspects and advantages of the present invention in further detail, it should be understood that the present invention is not inherently related to any particular computer, virtual machine or electronic device, and various general-purpose machines may be used to implement the present invention. The invention is not to be considered as limited to the specific embodiments thereof, but is to be understood as being modified in all respects, all changes and equivalents that come within the spirit and scope of the invention.
Claims (10)
1. A monitoring method for a distributed link, comprising:
setting a data collector based on each application component in the distributed link;
weaving a data acquisition rule in the loading period of the custom class loader of each application component through the data acquisition unit to acquire data of each application component during operation;
carrying out statistics and analysis processing on the data;
and feeding back the statistics and analysis processing results.
2. The method according to claim 1, wherein the run-in data collection rules specifically comprise: and weaving the data acquisition rule into the original byte code for loading the application component, and converting to form a new byte code for loading the application component.
3. The method of claim 2, wherein: and the data acquisition rule only collects and calls the middleware formed when each application component runs.
4. The method according to any one of claims 1-3, wherein: and each application component in the distributed link calls each time and is uniquely and correspondingly provided with one data acquisition unit.
5. The method according to any one of claims 1-4, wherein: and the data collector acquires the running data of each application component and generates label information for marking the data collector.
6. The method of claim 5, wherein: the tag information further includes a tracking identifier and call log information.
7. The method according to claim 5 or 6, characterized in that: and outputting the data acquired by the data acquisition unit and the label information, and performing further statistics and analysis processing.
8. A monitoring apparatus for a distributed link, comprising:
the monitor is used for setting a data collector based on each application component in the distributed link;
the data acquisition unit is used for weaving data acquisition rules in the loading period of the custom class loader of each application component to acquire data of each application component during operation;
the data processing module is used for counting and analyzing the data;
the summarizing storage module is used for storing the data, the statistics and the analysis processing results;
and the feedback display module is used for displaying the statistical and analysis processing result.
9. An electronic device, wherein the electronic device comprises:
a processor; and the number of the first and second groups,
a memory storing computer-executable instructions that, when executed, cause the processor to perform the method of any of claims 1-7.
10. A computer readable storage medium, wherein the computer readable storage medium stores one or more programs which, when executed by a processor, implement the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910572683.0A CN110351131B (en) | 2019-06-28 | 2019-06-28 | Monitoring method and device for distributed link and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910572683.0A CN110351131B (en) | 2019-06-28 | 2019-06-28 | Monitoring method and device for distributed link and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110351131A CN110351131A (en) | 2019-10-18 |
| CN110351131B true CN110351131B (en) | 2022-04-05 |
Family
ID=68176885
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910572683.0A Active CN110351131B (en) | 2019-06-28 | 2019-06-28 | Monitoring method and device for distributed link and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110351131B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112187511A (en) * | 2020-08-28 | 2021-01-05 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for positioning micro-service fusing abnormity |
| CN112559280B (en) * | 2020-12-04 | 2023-08-22 | 国网安徽省电力有限公司信息通信分公司 | Data full-link monitoring method based on data center station |
| CN114979224A (en) * | 2022-04-13 | 2022-08-30 | 上海电力设计院有限公司 | Photovoltaic monitoring system, method, equipment and medium based on 5G multi-anchor point |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108183927A (en) * | 2017-11-22 | 2018-06-19 | 链家网（北京）科技有限公司 | The monitoring method and system that a kind of distributed system link calls |
| EP3382551A1 (en) * | 2017-03-29 | 2018-10-03 | Google LLC | Distributed hardware tracing |
| CN109560989A (en) * | 2018-12-06 | 2019-04-02 | 深圳市递四方信息科技有限公司 | A kind of link monitoring system |
-
2019
- 2019-06-28 CN CN201910572683.0A patent/CN110351131B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3382551A1 (en) * | 2017-03-29 | 2018-10-03 | Google LLC | Distributed hardware tracing |
| CN108183927A (en) * | 2017-11-22 | 2018-06-19 | 链家网（北京）科技有限公司 | The monitoring method and system that a kind of distributed system link calls |
| CN109560989A (en) * | 2018-12-06 | 2019-04-02 | 深圳市递四方信息科技有限公司 | A kind of link monitoring system |
Non-Patent Citations (2)
| Title |
|---|
| 分布式链路追踪，https://zoyi14.smartapps.cn/pages/note/index?_swebFromHost=baiduboxapp&origin=share&slug=07cf4093536a&_swebfr=1;Daniel_adu;《简书》;20180706;全文 * |
| 基于分布式微服务全链路实时监控系统设计与实现;刘嘉裕;《中国优秀硕士学位论文全文数据库(信息科技辑)》;20190131;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110351131A (en) | 2019-10-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200401386A1 (en) | Reconfiguring application software into microservice architecture | |
| CN110351131B (en) | Monitoring method and device for distributed link and electronic equipment | |
| CN109344170B (en) | Stream data processing method, system, electronic device and readable storage medium | |
| Asadi et al. | A heuristic-based approach to identify concepts in execution traces | |
| US9697104B2 (en) | End-to end tracing and logging | |
| CN109408105A (en) | Acquisition method, device, computing device and the storage medium of user behavior data | |
| CN109599153B (en) | Medical data tracking method and device, storage medium and electronic equipment | |
| CN110196790A (en) | The method and apparatus of abnormal monitoring | |
| Turaga et al. | Design principles for developing stream processing applications | |
| CN111078729A (en) | Medical data tracing method, device, system, storage medium and electronic equipment | |
| CN114172949A (en) | Micro-service link monitoring and tracking method and system | |
| CN112579406B (en) | Log call chain generation method and device | |
| Romero et al. | Integration of DevOps practices on a noise monitor system with CircleCI and Terraform | |
| CN111143304A (en) | Micro-service system abnormal log analysis method based on request link | |
| CN113626288B (en) | Fault processing method, system, device, storage medium and electronic equipment | |
| CN112162954B (en) | User operation log generation and path positioning method, device, equipment and medium | |
| CN110297748A (en) | The method, apparatus and computer readable storage medium of error are called in a kind of positioning | |
| Suri et al. | Investigating the OO characteristics of software using CKJM metrics | |
| CN113806225A (en) | Method and device for identifying service abnormal node and electronic equipment | |
| CN114428706A (en) | Interface monitoring method and device, storage medium and electronic equipment | |
| Schreiber et al. | Analyzing software engineering processes with provenance-based knowledge graphs | |
| Birngruber et al. | Total recall: holistic metrics for broad systems performance and user experience visibility in a data-intensive computing environment | |
| CN113010483A (en) | Mass log management method and system | |
| CN111338900A (en) | Method and device for monitoring running state of software system | |
| CN112988560A (en) | Method and device for testing system robustness |
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 |