CN112118153B - Grpc and spring mvc-based link monitoring method and system - Google Patents
Grpc and spring mvc-based link monitoring method and system Download PDFInfo
- Publication number
- CN112118153B CN112118153B CN202010925295.9A CN202010925295A CN112118153B CN 112118153 B CN112118153 B CN 112118153B CN 202010925295 A CN202010925295 A CN 202010925295A CN 112118153 B CN112118153 B CN 112118153B
- Authority
- CN
- China
- Prior art keywords
- probe
- service
- link
- server
- log data
- 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
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000012544 monitoring process Methods 0.000 title claims abstract description 27
- 239000000523 sample Substances 0.000 claims abstract description 152
- 230000004044 response Effects 0.000 abstract description 7
- 230000000694 effects Effects 0.000 abstract description 5
- 230000009545 invasion Effects 0.000 abstract description 5
- 238000013480 data collection Methods 0.000 abstract description 3
- 238000004458 analytical method Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000006872 improvement Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
-
- 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/0677—Localisation of faults
-
- 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/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to the technical field of servers, and provides a link monitoring method and a system based on grpc and spring mvc, wherein the method comprises the following steps: printing link log data on the received request through a spring interceptor probe introduced into the service; respectively printing link log data through a server filter probe and a client filter probe which are arranged in a framework service grpc; the method comprises the steps that link log data respectively printed by a spring interceptor probe, a server-side filter probe and a client-side filter probe are collected by using a filter plug-in preset in a server, and the collected link log data are pushed to a corresponding database in real time, so that the effect of rapidly positioning the reason of one-time request response failure in a service scene is realized, the invasion to service codes is small, the deployment is simple, and the data collection and display efficiency is high.
Description
Technical Field
The invention belongs to the technical field of servers, and particularly relates to a grpc and spring mvc-based link monitoring method and system.
Background
The microservice architecture is an architectural model that advocates dividing a single application into a set of small services that are coordinated and coordinated to provide ultimate value to the user. Each service runs in its own independent process, and the services communicate with each other by adopting a lightweight communication mechanism (usually, HTTP-based RESTful API).
With the popularity of microservice architectures, services are split according to different dimensions, often requiring multiple services to be involved in a single request. Internet applications are built on different sets of software modules, possibly developed by different teams, possibly implemented using different programming languages, possibly distributed over thousands of servers, spanning multiple different data centers. Therefore, tools are needed to help understand system behavior and to analyze performance problems so that when a fault occurs, the problem can be quickly located and solved. However, at present, there is no well-formed mechanism for monitoring the full link of the server, locating and finding the problem of a certain service data, and efficiently querying the link data.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a link monitoring method based on grpc and spring mvc, aiming at solving the problems that no set of well-formed mechanism is available in the prior art to monitor the whole link of a server, locate and find a certain service data and efficiently query the link data.
The technical scheme provided by the invention is as follows: a grpc and spring mvc based link monitoring method, the method comprising the steps of:
printing link log data on the received request through a spring interceptor probe introduced into the service;
respectively printing link log data through a server filter probe and a client filter probe which are arranged in a framework service grpc;
and collecting link log data respectively printed by the spring interceptor probe, the server-side filter probe and the client-side filter probe by using a filter plug-in preset in the server, and pushing the collected link log data to a corresponding database in real time.
As an improved scheme, the step of printing the link log data of the received request by a spring interceptor probe introduced into the service further comprises the following steps:
and introducing the spring interceptor probe into the service, and setting the introduced spring interceptor probe to be executed in a first order.
As an improved solution, the step of printing the link log data through the filter probes arranged at the service end and the client end of the framework service grpc further includes the following steps:
before a framework service grpc client initiates a call operation, a client filter probe and a server filter probe are introduced into the framework service grpc.
As an improved scheme, before the step of collecting link log data respectively printed by the spring interceptor probe, the server filter probe and the client filter probe by using a filter plug-in preset in a server, and pushing the collected link log data to a corresponding database in real time, the method further comprises the following steps:
installing the filter plug-in all servers, wherein the filter plug-in is a logstack plug-in, and the format of a log read by the logstack plug-in is 'flmc': '[ log time ]': '[ event type ]': '[ call time ]': '[ link ID ]': '[ spanId ]': '[ partensSpanid ]:' [ spanName ] ': extended information ]';
and modifying a path in the configuration file of the server to be a log record needing to be collected on the current server.
As an improvement, the method further comprises the steps of:
and when the request information is service information in service, calling a preset custom expansion information probe to acquire service data in a link associated with the service information.
As an improved scheme, when the request information is service information in service, the step of calling a preset custom extension information probe to collect service data in a link associated with the service information further includes the following steps:
and setting a user-defined extended information probe in the server in advance.
As an improved scheme, when the request information is service information in service, the step of calling a preset custom extension information probe to collect service data in a link associated with the service information further includes the following steps:
analyzing the link log data printed by the spring interceptor probe, the server filter probe and the client filter probe and the service data acquired by the user-defined extended information probe, and establishing association between the link log data and the service data.
Another object of the present invention is to provide a grpc and spring mvc based link monitoring system, which includes:
the first link log data printing module is used for printing the link log data of the received request through a spring interceptor probe introduced into service;
the second link log data printing module is used for respectively printing link log data through a server-side filter probe and a client-side filter probe which are arranged on the frame service grpc;
the link log data acquisition module is used for acquiring link log data respectively printed by the spring interceptor probe, the server-side filter probe and the client-side filter probe by using a filter plug-in preset in the server;
and the link log data pushing module is used for pushing the link log data acquired by the link log data acquisition module to a corresponding database in real time.
As an improvement, the system further comprises:
the spring interceptor probe creating module is used for introducing the spring interceptor probe into the service and setting the introduced spring interceptor probe to be executed in a first order;
the filter probe creating module is used for introducing a client filter probe and a server filter probe into the framework service grpc before the framework service grpc client initiates a calling operation;
the filter plug-in creating module is used for installing the filter plug-ins in all the servers, the filter plug-ins are logstack plug-ins, the format of the log read by the logstack plug-ins is 'flmc': log time ': event type': call time ': link ID': spanId ': parentsid': parentspinald ': extended information';
and the user-defined extended information probe setting module is used for setting the user-defined extended information probe in the server in advance.
As an improvement, the system further comprises:
the service data acquisition module is used for calling a preset custom extension information probe to acquire service data in a link associated with the service information when the request information is the service information in the service;
and the incidence relation establishing module is used for analyzing the link log data printed by the spring interceptor probe, the server-side filter probe and the client-side filter probe and the service data acquired by the user-defined extended information probe and establishing the incidence relation between the link log data and the service data.
In the embodiment of the invention, the received request is printed with link log data through a spring interceptor probe introduced into the service; respectively printing link log data through a server filter probe and a client filter probe which are arranged in a framework service grpc; the method comprises the steps that link log data respectively printed by a spring interceptor probe, a server-side filter probe and a client-side filter probe are collected by using a filter plug-in preset in a server, and the collected link log data are pushed to a corresponding database in real time, so that the effect of rapidly positioning the reason of one-time request response failure in a service scene is realized, the invasion to service codes is small, the deployment is simple, and the data collection and display efficiency is high.
Drawings
In order to more clearly illustrate the detailed description of the invention or the technical solutions in the prior art, the drawings used in the detailed description or the prior art description will be briefly described below. Throughout the drawings, like elements or portions are generally identified by like reference numerals. In the drawings, elements or portions are not necessarily drawn to scale.
FIG. 1 is a flowchart of an implementation of a link monitoring method based on grpc and spring mvc according to the present invention;
FIG. 2 is a block diagram of a grpc and spring mvc based link monitoring system provided by the present invention.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The following examples are merely for illustrating the technical solutions of the present invention more clearly, and therefore are only examples, and the protection scope of the present invention is not limited thereby.
Fig. 1 is a flowchart of an implementation of a link monitoring method based on grpc and spring mvc, which specifically includes the following steps:
in step S101, printing link log data on the received request by a spring interceptor probe introduced into the service;
the method comprises the steps that when link log data are printed, data isolation among threads is achieved through readload storage, wherein the ThreadLocal is a storage class inside one thread and can store data in a designated thread, and only the designated thread can obtain the stored data after the data are stored.
In step S102, link log data is printed by a server filter probe and a client filter probe respectively, which are provided in the framework service grpc;
in step S103, link log data respectively printed by the spring interceptor probe, the server filter probe, and the client filter probe are collected by using a filter plug-in preset in the server, and the collected link log data are pushed to a corresponding database in real time.
In the embodiment, the embodiment of the invention is mainly applied to a spring + grpc micro-service application scene, different services are mutually called in a grpc mode, all service calling detailed records in a certain request processing process include response time and error information of each service calling, and the service link is also supported to be associated with service key information, so that the effect of rapidly positioning the reason of one-time request response failure in a service scene is realized, the invasion to service codes is small, the deployment is simple, and the data acquisition and display efficiency is high.
Wherein, the grpc is a high-performance, open-source and universal RPC framework designed for mobile and HTTP/2, and is designed based on HTTP/2 standard, which brings features such as bidirectional flow, flow control, header compression, multiple multiplexing requests on a single TCP connection, and the like. These characteristics make it perform better on mobile devices, saving more power and space, in grpc, the client application can directly invoke the methods of the server applications deployed on other machines, like the methods of the local objects. The grpc reduces the difficulty of building distributed applications and services. Like other RPC systems, the core of a grpc is also a service definition, defining the entries and return values that can be called methods remotely. At the server side, the server applies the implementation method and starts a grpc server to process the client side call. At the client, the client has a component called stub (called the client in many languages) that provides a method that is consistent with the server.
spring mvc belongs to the SsppringFrameWork follow-up product, and is fused in spring WebFlow. The spring framework provides a fully functional MVC module that builds Web applications. The MVC architecture in which the spring can be inserted is used, and a built-in spring Web framework or a Web framework such as struts can be selected.
Thus, the embodiment of the present invention shown in fig. 1 is implemented in the following context: service calling is realized between the micro-services in a grpc mode, and the service realization mode adopts spring mvc.
The embodiment of the invention provides two basic probe tools, strictly defines the format of related log data, prints the grpc service call related logs in real time, configures a logstack log acquisition tool, and pushes the service logs into es. The method provides a full-link monitoring display tool, and multi-dimensional different indexes for displaying full-link monitoring data specifically include:
(1) Introducing the spring interceptor probe into the service, and setting the introduced spring interceptor probe to be executed in a first order;
the Spring interceptor probe adopts a Spring interceptor mode, judges whether a link identification traceId field exists in the requested header information in a pre-processing method preHandle of the interceptor, if so, uses the traceId in the requested header information as the current link ID, and simultaneously generates the corresponding spanId, if the parentspanId exists in the requested header information, the precetspanId is used as the parentspanId of the Spring interceptor probe, and if not, the parentspanId of the whole link. After being generated, the TraceId, the span Id and the parentSpanId are all stored in the thread local corresponding to the current thread, sr logs are printed, and ss logs are printed in the afterCompletion method. It should be noted that, because the controller of the spring mvc is in the multithreading mode, there is a phenomenon of thread reuse, and after a certain request is completed, the storage information of the current thread needs to be cleared in the aft completion method;
(2) Before a framework service grpc client side initiates a calling operation, a client side filter probe and a server side filter probe are introduced into the framework service grpc;
the filter probe is divided into a client side and a server side, the client side filter probe is used for collecting two logs of a client side initiating request cs and a client side obtaining return information cr of the server side, and the server side filter probe is used for collecting two types of requests sr received by the server side and feedback clients ss processed by the server. The client filter probe is essentially a grpc filter, acquires the traceId and the parentsSpaniD in the current thread in a start method in the client filter, generates the own spanId at the same time, prints out the cs log, needs to operate the header information of the request before the request is sent, and puts the traceId, the parentsSpaniD and the current spanId into the header of the request. In the onClose method of the client, cr log is printed, and the traceId, the spanId and the parentsspanid of the current client are printed at the same time. The server filter probe firstly acquires traceId, parentsSpanid and client spanId in the header transmitted from the client, generates the own spanId of the server and simultaneously prints an sr log. Printing an ss log before the server sends an http response, and recording the time of the server for completing the request;
in this embodiment, threadLocal is a storage class inside a thread, and can store data in a designated thread, and after data is stored, only the designated thread can obtain the stored data; the Span represents a context corresponding to the Span, the Span and the Span context basically have a one-to-one correspondence, and the context stores some information needing to cross a boundary; trace is similar to a set of spans in a tree structure, representing a complete Trace, starting with the request to the server and ending with the server returning a response, there is a unique identifying traceId tracking the elapsed time of each rpc call.
(3) Installing the filter plug-in all servers, wherein the filter plug-in is a logstack plug-in, and the log reading format of the logstack plug-in is 'flmc': [ log time ] ':' [ event type ] ':' [ call time ] ':' [ link ID ] ':' [ spanId ] ':': paretsspanId ] ':': spanName ] ': extended information';
modifying a path in a configuration file of the server into a log record needing to be collected on the current server;
the output target of the configuration log is an es database, the logstack plug-in unit is randomly started, and the configuration log can be collected all the time as long as the link monitoring log is output.
In the embodiment of the invention, the link log collection method is realized by a spring interceptor probe, a client filter probe and a server filter probe of a grpc, the two basic probes can automatically generate information of a link and print link log data, and the accurate and efficient collection of the link log is realized by configuring a collection rule of logstack. And the data is stored in the nosql database es, so that the high efficiency of data query can be realized.
When the link log data is collected, the data in the database es may be tracked and analyzed, specifically including call chain tracking, time-consuming analysis, call path analysis, performance analysis, and the like, which is not described herein again.
In the embodiment of the present invention, in addition to the two basic probe tools, the following probe is also required, specifically:
a user-defined extended information probe is set in a server in advance, the extended information adopted by the probe is the IP of the current server, and if relevant service information needs to be added into the extended information, all links relevant to the current mobile phone number can be inquired according to the service information such as a certain mobile phone number.
In the embodiment, when the request information is service information in service, a preset custom extension information probe is called to collect service data in a link associated with the service information;
and analyzing the link log data printed by the spring interceptor probe, the server filter probe and the client filter probe and the service data acquired by the custom extended information probe, and establishing association between the link log data and the service data.
In this embodiment, an independent log type biz is defined, the TraceId, span id and parentSpanId in the header of the current thread or request are collected in the biz log, the user-defined data is supported to be printed according to the json format, and the user can print the required information in a manner similar to { "telephone": 18722223333"," orderNo ": 8888-www-222" }, so as to realize the effect of associating the service data with the link.
The embodiment of the invention can collect and display the link monitoring data, can associate the service data with the link data, can reduce the invasion to a service system, keep the transparency to a user, reduce the burden of developers, reduce the access threshold and the difficulty, and reduce the loss of performance as much as possible by a log data collecting mode. Meanwhile, link monitoring data can be displayed almost in real time, related personnel can be helped to understand system behaviors, and correct and objective data reference is provided for flow, architecture and code optimization, capacity expansion and reduction and service current limiting and degradation.
Fig. 2 shows a block diagram of a grpc and spring mvc-based link monitoring system provided in the present invention, and for convenience of illustration, only the parts related to the embodiment of the present invention are shown in the diagram.
The grpc and spring mvc-based link monitoring system comprises:
a first link log data printing module 11, configured to print link log data of a received request through a spring interceptor probe introduced into a service;
the second link log data printing module 12 is configured to print link log data through a server filter probe and a client filter probe that are arranged in the framework service grpc, respectively;
a link log data acquisition module 13, configured to acquire link log data respectively printed by the spring interceptor probe, the server-side filter probe, and the client-side filter probe by using a filter plug-in preset in the server;
the link log data pushing module 14 is configured to push the link log data acquired by the link log data acquiring module to a corresponding database in real time;
wherein the system further comprises:
a spring interceptor probe creating module 15, configured to introduce the spring interceptor probe into the service, and set the introduced spring interceptor probe to be executed in a first order;
a filter probe creating module 16, configured to introduce a client filter probe and a server filter probe into the framework service grpc before the framework service grpc client initiates a call operation;
a filter plug-in creating module 17, configured to install the filter plug-ins in all servers, where the filter plug-ins are logstack plug-ins, where the format of the log read by the logstack plug-ins is "flmc": "[ log time ]": "[ event type ]": "[ call time ]": "[ link ID ]": "[ spanId ]": "[ parentsspanid ]": "[ spanName ]": "[ extended information ]", and a path in a configuration file of a modification server is a log record to be collected on the current server;
and the custom extended information probe setting module 18 is used for setting a custom extended information probe in the server in advance.
In the embodiment of the present invention, the service data acquisition module 19 is configured to, when the request information is service information in a service, invoke a preset custom extension information probe to acquire service data in a link associated with the service information;
and the association relationship establishing module 20 is configured to analyze link log data printed by the spring interceptor probe, the server filter probe and the client filter probe and service data acquired by the custom extended information probe, and establish an association between the link log data and the service data.
The functions of the modules are described in the above embodiments, and are not described herein again.
In the embodiment of the invention, the received request is printed with link log data through a spring interceptor probe introduced into the service; respectively printing link log data through a server filter probe and a client filter probe which are arranged in a framework service grpc; the method comprises the steps that link log data respectively printed by a spring interceptor probe, a server-side filter probe and a client-side filter probe are collected by using a filter plug-in preset in a server, and the collected link log data are pushed to a corresponding database in real time, so that the effect of rapidly positioning the reason of one-time request response failure in a service scene is realized, the invasion to service codes is small, the deployment is simple, and the data collection and display efficiency is high.
The above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present invention, and they should be construed as being included in the following claims and description.
Claims (9)
1. A method for monitoring a link based on grpc and spring mvc, comprising the steps of:
printing link log data on the received request through a spring interceptor probe introduced into the service;
respectively printing link log data through a server filter probe and a client filter probe which are arranged in a framework service grpc;
collecting link log data respectively printed by the spring interceptor probe, the server-side filter probe and the client-side filter probe by using a filter plug-in preset in a server, and pushing the collected link log data to a corresponding database in real time;
the method comprises the following steps that the link log data respectively printed by the spring interceptor probe, the server-side filter probe and the client-side filter probe are collected by using a filter plug-in preset in the server, and the collected link log data are pushed to a corresponding database in real time:
installing the filter plug-in all servers, wherein the filter plug-in is a logstack plug-in, and the format of a log read by the logstack plug-in is 'flmc': '[ log time ]': '[ event type ]': '[ call time ]': '[ link ID ]': '[ spanId ]': '[ partensSpanid ]:' [ spanName ] ': extended information ]';
and modifying the path in the configuration file of the server into the log record needing to be collected on the current server.
2. The grpc and spring mvc-based link monitoring method according to claim 1, wherein the step of printing the received request for link log data by a spring interceptor probe introduced into the service further comprises the following steps before:
and introducing the spring interceptor probe into the service, and setting the introduced spring interceptor probe to be executed in a first order.
3. The grpc and spring mvc-based link monitoring method according to claim 1, wherein the step of printing link log data through filter probes provided at the service end and the client end of a framework service grpc further comprises the following steps before:
before the framework service grpc client initiates a call operation, a client filter probe and a server filter probe are introduced in the framework service grpc.
4. The grpc and spring mvc-based link monitoring method of claim 1, further comprising the steps of:
and when the request information is service information in service, calling a preset custom extension information probe to acquire service data in a link associated with the service information.
5. The grpc and spring mvc-based link monitoring method according to claim 4, wherein the step of invoking a preset custom extension information probe to collect the service data in the link associated with the service information when the request information is the service information further comprises the following steps:
and setting a user-defined extended information probe in the server in advance.
6. The grpc and spring mvc-based link monitoring method according to claim 4, wherein the step of invoking a preset custom extension information probe to collect the service data in the link associated with the service information when the request information is the service information further comprises the following steps:
analyzing the link log data printed by the spring interceptor probe, the server filter probe and the client filter probe and the service data acquired by the user-defined extended information probe, and establishing association between the link log data and the service data.
7. A grpc and spring mvc-based link monitoring system, comprising:
the first link log data printing module is used for printing the link log data of the received request through a spring interceptor probe introduced into service;
the second link log data printing module is used for respectively printing link log data through a server-side filter probe and a client-side filter probe which are arranged on the framework service grpc;
the link log data acquisition module is used for acquiring link log data respectively printed by the spring interceptor probe, the server-side filter probe and the client-side filter probe by using a filter plug-in preset in the server;
the link log data pushing module is used for pushing the link log data acquired by the link log data acquisition module to a corresponding database in real time;
the filter plug-in creating module is used for installing the filter plug-ins in all the servers, the filter plug-ins are logstack plug-ins, the format of the log read by the logstack plug-ins is 'flmc': log time ': event type': call time ': link ID': spanId ': parentsid': parentspinald ': extended information';
and the custom extended information probe setting module is used for setting the custom extended information probe in the server in advance.
8. The grpc and spring mvc-based link monitoring system of claim 7, further comprising:
the spring interceptor probe creating module is used for introducing the spring interceptor probe into the service and setting the introduced spring interceptor probe to be executed in a first order;
and the filter probe creating module is used for introducing a client filter probe and a server filter probe into the framework service grpc before the framework service grpc client initiates a calling operation.
9. The grpc and spring mvc-based link monitoring system of claim 7, further comprising:
the service data acquisition module is used for calling a preset custom extension information probe to acquire service data in a link associated with the service information when the request information is the service information in the service;
and the incidence relation establishing module is used for analyzing the link log data printed by the spring interceptor probe, the server-side filter probe and the client-side filter probe and the service data acquired by the user-defined extended information probe and establishing the incidence relation between the link log data and the service data.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010925295.9A CN112118153B (en) | 2020-09-06 | 2020-09-06 | Grpc and spring mvc-based link monitoring method and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010925295.9A CN112118153B (en) | 2020-09-06 | 2020-09-06 | Grpc and spring mvc-based link monitoring method and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN112118153A CN112118153A (en) | 2020-12-22 |
CN112118153B true CN112118153B (en) | 2022-12-27 |
Family
ID=73802396
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010925295.9A Active CN112118153B (en) | 2020-09-06 | 2020-09-06 | Grpc and spring mvc-based link monitoring method and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN112118153B (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111431773B (en) * | 2020-05-18 | 2022-01-28 | 江苏电力信息技术有限公司 | OpenTracing-based link tracking method |
CN114357044A (en) * | 2021-12-28 | 2022-04-15 | 南威软件股份有限公司 | Big data full life cycle management method, system and application based on-duty tracking |
CN114785878A (en) * | 2022-04-24 | 2022-07-22 | 北京印象笔记科技有限公司 | Information extraction method and device, electronic equipment and computer readable storage medium |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109802842A (en) * | 2017-11-16 | 2019-05-24 | 华为软件技术有限公司 | The generation method and relevant device of applied topology |
CN110191000A (en) * | 2019-06-10 | 2019-08-30 | 中汇信息技术(上海)有限公司 | A kind of data processing method, message tracing monitoring method and distributed system |
CN111431773A (en) * | 2020-05-18 | 2020-07-17 | 江苏电力信息技术有限公司 | OpenTracing-based link tracking method |
CN111541590A (en) * | 2020-07-08 | 2020-08-14 | 广州市玄武无线科技股份有限公司 | Link monitoring method, alarm method, system, terminal and storage medium |
CN111585840A (en) * | 2020-04-29 | 2020-08-25 | 北京申信联华科技有限公司 | Service resource monitoring method, device and equipment |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180083985A1 (en) * | 2016-09-20 | 2018-03-22 | ShieldX Networks, Inc. | Systems and methods for network security event filtering and translation |
US10574513B2 (en) * | 2017-06-16 | 2020-02-25 | Cisco Technology, Inc. | Handling controller and node failure scenarios during data collection |
-
2020
- 2020-09-06 CN CN202010925295.9A patent/CN112118153B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109802842A (en) * | 2017-11-16 | 2019-05-24 | 华为软件技术有限公司 | The generation method and relevant device of applied topology |
CN110191000A (en) * | 2019-06-10 | 2019-08-30 | 中汇信息技术(上海)有限公司 | A kind of data processing method, message tracing monitoring method and distributed system |
CN111585840A (en) * | 2020-04-29 | 2020-08-25 | 北京申信联华科技有限公司 | Service resource monitoring method, device and equipment |
CN111431773A (en) * | 2020-05-18 | 2020-07-17 | 江苏电力信息技术有限公司 | OpenTracing-based link tracking method |
CN111541590A (en) * | 2020-07-08 | 2020-08-14 | 广州市玄武无线科技股份有限公司 | Link monitoring method, alarm method, system, terminal and storage medium |
Also Published As
Publication number | Publication date |
---|---|
CN112118153A (en) | 2020-12-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN112118153B (en) | Grpc and spring mvc-based link monitoring method and system | |
US20220107917A1 (en) | Generating target application packages for groups of computing devices | |
US10460255B2 (en) | Machine learning in edge analytics | |
CN112035317B (en) | Micro-service link monitoring method, device, equipment and medium | |
CN108509392B (en) | Multi-mechanism account checking method, system, computer equipment and storage medium | |
CN110932918B (en) | Log data acquisition method and device and storage medium | |
CN107688611B (en) | Saltstack-based Redis key value management system and method | |
KR20180132287A (en) | Method for automatic monitoring end to end performance of end-user and apparatus for using the same | |
CN112506755B (en) | Log acquisition method, device, computer equipment and storage medium | |
CN102769625A (en) | Client-side Cookie information acquisition method and device | |
CN112637331B (en) | Spacecraft state data processing method and device | |
CN105450449A (en) | File operation methods and devices | |
US20150088958A1 (en) | Information Processing System and Distributed Processing Method | |
CN111385157B (en) | Server abnormity detection method and device | |
US8037359B2 (en) | Operation management system having a process execution apparatus, information management apparatus, and process analyzing apparatus, process analyzing apparatus, recording medium in which process analysis program is recorded, and process analysis method | |
CN115250233B (en) | Gray scale routing control method, gray scale routing assembly and computer equipment | |
CN110765089A (en) | Distributed equipment and log recording method, device and storage medium thereof | |
KR20210000041A (en) | Method and apparatus for analyzing log data in real time | |
CN109981342A (en) | A kind of method and system of batch processing network device operation order | |
CN109634931B (en) | Log uploading method and device | |
CN105988917B (en) | Abnormal information acquisition method and device | |
US20110066939A1 (en) | Troubleshooting support method, and troubleshooting support apparatus | |
CN113381907A (en) | Log collection method and device, electronic equipment and storage medium | |
CN113282358A (en) | File transmission analysis method and device of bastion machine | |
US8775528B2 (en) | Computer readable recording medium storing linking keyword automatically extracting program, linking keyword automatically extracting method and apparatus |
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 |