CN115766532A - Link monitoring method and device, storage medium and electronic device - Google Patents
Link monitoring method and device, storage medium and electronic device Download PDFInfo
- Publication number
- CN115766532A CN115766532A CN202211296589.5A CN202211296589A CN115766532A CN 115766532 A CN115766532 A CN 115766532A CN 202211296589 A CN202211296589 A CN 202211296589A CN 115766532 A CN115766532 A CN 115766532A
- Authority
- CN
- China
- Prior art keywords
- request
- target
- link
- identifier
- user request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides a link monitoring method, a link monitoring device, a storage medium and an electronic device, wherein the method comprises the following steps: determining generation time for generating a target identifier in an intercepted user request, wherein the user request is a request intercepted at a request entrance; determining an end time for completing execution of the user request; acquiring link data generated by a target link between the generation time and the end time, wherein the target link is formed by executing a user request; and saving the link data into a log file so as to monitor the target link through the log file. The invention solves the problems of poor monitoring link flexibility and influence on system performance in the related technology, and achieves the effects of improving the monitoring link flexibility and reducing the influence on the system performance.
Description
Technical Field
The embodiment of the invention relates to the field of computers, in particular to a link monitoring method, a link monitoring device, a link monitoring storage medium and an electronic device.
Background
In the related art, when performing link monitoring, a mode of using a probe is generally used, and a mode of using the probe needs to adapt middleware and the like, so that the requirement on the technology is high, and therefore, a certain threshold is provided for secondary development, and the secondary development is deficient in flexibility and business processing. The method is also strong in intrusion, and a corresponding packet needs to be introduced into a project to be embedded (an interceptor, a comment and a filter are used). However, this method is relatively backward in data storage and cannot be adapted to the current large data storage, especially some relatively accurate queries. And because the updating is not carried out for a long time, incompatibility caused by inconsistent versions in use is also caused. In addition, the two modes are used for collecting the link in real time, and the performance is influenced to a certain degree.
Therefore, the related technology has the problems that the monitoring link has poor flexibility and influences the system performance.
In view of the above problems in the related art, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the invention provides a link monitoring method, a link monitoring device, a storage medium and an electronic device, which at least solve the problems of poor link monitoring flexibility and influence on system performance in the related technology.
According to an embodiment of the present invention, there is provided a link monitoring method, including: determining generation time for generating a target identifier in an intercepted user request, wherein the user request is a request intercepted at a request entrance; determining an end time for completing execution of the user request; acquiring link data generated by a target link between the generation time and the end time, wherein the target link is a link formed by executing the user request; and saving the link data into a log file so as to monitor the target link through the log file.
According to another embodiment of the present invention, there is provided a link monitoring apparatus including: the system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for determining the generation time of generating a target identifier in an intercepted user request, and the user request is the request intercepted at a request entrance; a second determining module, configured to determine an end time when the execution of the user request is completed; an obtaining module, configured to obtain link data generated by a target link between the generation time and the end time, where the target link is a link formed by executing the user request; and the storage module is used for storing the link data into a log file so as to monitor the target link through the log file.
According to a further embodiment of the present invention, there is also provided a computer-readable storage medium having a computer program stored thereon, wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.
According to yet another embodiment of the present invention, there is also provided an electronic device, including a memory in which a computer program is stored and a processor configured to execute the computer program to perform the steps in any of the above method embodiments.
According to the invention, the generation time of generating the target identifier in the intercepted user request is determined, the end time of completing the execution of the user request is determined, the link data generated by the target link between the generation time and the end time is obtained, and the link data is stored in the log file so as to monitor the target link through the log file. When monitoring the target link, the link data generated between the generation time of generating the target identifier in the user request and the end time of executing the user request can be acquired, the link data is kept in the log file, the target link is monitored through the log file, secondary development is not needed, and the intrusiveness is low, so that the problems that the monitoring link is poor in flexibility and influences the system performance in the related technology can be solved, and the effects of improving the flexibility of the monitoring link and reducing the influences on the system performance are achieved.
Drawings
Fig. 1 is a block diagram of a hardware structure of a mobile terminal of a link monitoring method according to an embodiment of the present invention;
fig. 2 is a flow chart of a method of monitoring a link according to an embodiment of the invention;
fig. 3 is a block diagram of a monitoring apparatus of a link according to an embodiment of the present invention.
Detailed Description
Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings in conjunction with the embodiments.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
The method embodiments provided in the embodiments of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking an example of the method running on a mobile terminal, fig. 1 is a block diagram of a hardware structure of the mobile terminal of a link monitoring method according to an embodiment of the present invention. As shown in fig. 1, the mobile terminal may include one or more (only one shown in fig. 1) processors 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), and a memory 104 for storing data, wherein the mobile terminal may further include a transmission device 106 for communication functions and an input-output device 108. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration, and does not limit the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.
The memory 104 may be used to store a computer program, for example, a software program of an application software and a module, such as a computer program corresponding to the link monitoring method in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, so as to implement the method described above. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the mobile terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 106 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a Network adapter (NIC), which can be connected to other Network devices through a base station so as to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is used to communicate with the internet in a wireless manner.
In this embodiment, a method for monitoring a link is provided, and fig. 2 is a flowchart of the method for monitoring a link according to the embodiment of the present invention, as shown in fig. 2, the flowchart includes the following steps:
step S202, determining generation time for generating a target identifier in an intercepted user request, wherein the user request is an intercepted request at a request entrance;
step S204, determining the end time for completing the execution of the user request;
step S206, link data generated by a target link between the generation time and the ending time is obtained, wherein the target link is formed by executing the user request;
step S208, saving the link data into a log file, so as to monitor the target link through the log file.
In the above embodiment, the target link may be a link in a microservice application scenario, and the user may invoke or access a node included in the microservice through a user request. When a user inputs a user request, the user request can be intercepted at a request entrance, and a target identification can be generated in the user request. The target identifier may include a tracking identifier, a span identifier, a request identifier, a service identifier, and the like. The service invoked when executing the user request can be determined by the target identifier, and then the target link is generated according to the invoked service and the invoking sequence, that is, the invoking between different services will generate a corresponding target link.
In the above embodiment, the generation time at which the target identifier may be generated in the user request may be the time at which the user request is received. The received user request may be sent by the gateway. After the user request is executed, an end time for completing the execution of the user request may be recorded. That is, when the user request is completed and the method is exited, an end time is recorded, the time consumed by the service or the method is obtained by subtracting the generation time from the end time, and the returned link data record is also output to the log. After the user request is executed, the target link corresponding to the user request can be determined, link data generated by the target link between the generation time and the ending time is further acquired, and the link data is stored in a log file. The link information data is recorded into the request by intercepting the request at the request inlet, and the link information data is stored in the log file, so that the low-intrusion acquisition of the link data is realized, and the loss of the system performance during the project operation is reduced.
In the above embodiment, after the link data is saved, the link data may be viewed or accessed through the log file, so as to implement monitoring on the link data. When a link fails or the execution of a user request fails, the fault position can be quickly positioned by accessing the log file.
The executing subject of the above steps may be a background processor, a server, etc., but is not limited thereto.
According to the invention, the generation time of generating the target identifier in the intercepted user request is determined, the end time of completing the execution of the user request is determined, the link data generated by the target link between the generation time and the end time is obtained, and the link data is stored in the log file so as to monitor the target link through the log file. When monitoring the target link, the link data generated between the generation time of generating the target identifier in the user request and the end time of executing the user request can be acquired, the link data is kept in the log file, the target link is monitored through the log file, secondary development is not needed, and the intrusiveness is low, so that the problems that the monitoring link is poor in flexibility and influences the system performance in the related technology can be solved, and the effects of improving the flexibility of the monitoring link and reducing the influences on the system performance are achieved.
In one exemplary embodiment, prior to determining a generation time for generating the target identification in the intercepted user request, the method further comprises: intercepting the user request in a target gateway, wherein the target gateway comprises the request inlet; generating the target identification in a request header of the user request; and storing the target identification in a header file requested by the user. In this embodiment, the user may send the user request to the microservice system through the gateway, and therefore, the user request may be intercepted in the target gateway, that is, the user request may be intercepted at the request entry. After intercepting the user request, a unique call ID, i.e. a target identifier, may be generated in the request header and stored in the header. The link data can be obtained by intercepting the user request in the target gateway, namely adding the target identifier in the user request before sending the user request to the micro-service system, and then sending the user request to the micro-service system, so that the integrity of the obtained link data is ensured.
In an exemplary embodiment, generating the target identification in a request header of the user request comprises at least one of: generating a tracking identifier in a request header of the user request, wherein the target identifier comprises the tracking identifier, and the tracking identifier is used for tracking a path called by the user request; generating a span identifier in a request header of the user request, wherein the target identifier comprises the span identifier, and the span identifier is used for identifying a position where the user request is located in a call; under the condition that the user request is a request sent by a target user, generating a request identifier in a request header of the user request, wherein the target user is a user who has not sent the request, the target identifier comprises the request identifier, and the request identifier is used for identifying the target user; and under the condition that other services need to be called when the user request is executed, generating a service identifier in a request header of the user request, wherein the target identifier comprises the service identifier. In this embodiment, the tracking identifier may be a TraceId, and the TraceId may be generated after being intercepted by the gateway, and the lifetime is as follows: the request received from the gateway and the data returned to the gateway are all unique and will not be modified. The span identification may be a span id, which generates a different span id for invoking a different method. Interception can be performed using AOP. The life cycle is as follows: from the entry method to the exit method. The request identifier may be a RequestId, if the user has never sent a request before, the gateway generates a RequestId, and returns it as a front end every response, and the front end brings the RequestId on every request after obtaining the RequestId. If the gateway acquires the RequestId, it does not generate, but uses this RequestId. The life cycle is as follows: from the user request, all requests for this user are the same RequestId, until the service shuts down. The service identifier may be a ServiceId, if the user requests the B-service, the service id in the gateway is the same if the user needs to call the B-service through the gateway, and a new ServiceId is generated when the user acquires the request in the B-service. The life cycle is as follows: starting from entering the service and going out of the service.
In an exemplary embodiment, saving the link data to a log file comprises: determining a request time when the user request is received and a request parameter included in the user request; determining response time responding to the user request and target parameters returned in response to the user request; and saving the target identification, the request time, the request parameters, the response time and the target parameters into the log file. In this embodiment, in other services outside the target gateway, for example: the order service, the product service and the member service can intercept data requested by a target gateway through an interceptor, and acquire two values of a tracking identifier TraceId and a request identifier RequestId from the target gateway and generate a span identifier SpaniD. Meanwhile, the data can be written into ThreadLocal through a SET method or written into MDC by calling a PUT method, and the TraceId, the RequestId, the SpaniD, the ServiceId, the request parameter, the request time, the response time and the return parameter, namely the target parameter, are written into a log file.
In an exemplary embodiment, after saving the link data into a log file to monitor the target link through the log file, the method further comprises: screening a target log file from a first database based on the target identification; and storing the target log file into a second database. In this embodiment, the first database may be Kafka, and data such as in Kafka may be read out using Quarkus. For example, the target log file at the search site can be saved in the second database for persistent saving by searching in the first database according to the target identifier, such as three values of the request identifier RequestId, the service identifier ServiceId, and the tracking identifier TraceId. Wherein the second database may be Clickhouse.
In one exemplary embodiment, prior to screening target log files from the first database based on the target identification, the method further comprises: and storing the log file into the first database. In this embodiment, when the first database is Kafka, the log file can be read and written into Kafka in real time through FileBeat, and the data is not filtered yet, but only filtered.
In an exemplary embodiment, after saving the link data into a log file to monitor the target link through the log file, the method further comprises: receiving a query request input through a target page, wherein the query request comprises a query identifier; and searching the log file for a query log corresponding to the query identifier. In this embodiment, a login entry may be obtained by writing a page, and after the user successfully logs in, the log may be checked, or the query log corresponding to the query identifier may be searched by using the query identifier, such as the request identifier RequestId, the service identifier ServiceId, the tracking identifier TraceId, or the like. The query identifier includes a request identifier, a service identifier, a tracking identifier, a span identifier, and the like.
The following describes a link monitoring method with reference to a specific embodiment:
in a specific embodiment of the present invention, a method for monitoring a link includes the following steps:
s1, intercepting a user request in a gateway, generating a unique calling Id in a request header, and storing the unique calling Id in a header. Such as TraceId/SpaniD/Reqeustid/ServiceId.
S11, generating the TraceId after intercepting from the gateway, wherein the life cycle is as follows: the request received from the gateway and the data returned to the gateway are all unique and will not be modified.
And S12, the SpaniD generates different SpaniD for calling different methods. And intercepting by using an AOP mode. The life cycle is as follows: from the entry method to the exit method.
And S13, if the user never sends a request before, the gateway generates the RequestId, the RequestId is returned to the front end every time of response, and the front end carries the RequestId every time of request after acquiring the RequestId. If the gateway acquires the RequestId, it does not generate, but uses this RequestId. The life cycle is as follows: from the user request, until the service is powered off, all requests for this user are the same RequestId.
S14, if the user requests the service B, the service B needs to be called through the gateway, the service IDs in the gateway are the same, and when the request is acquired in the service B, a new service ID is generated. The life cycle is as follows: from the start of entering a service to the exit of this service.
And S2, when the Id is generated in all the Ids, recording the generation time and outputting the request parameters to a log.
And S3, recording an end time in the exiting method, obtaining the time consumed by the service/method by subtracting the generation time according to the end time, and outputting the returned data record to the log.
S4. In other services outside the gateway, for example: the order service, the product service and the member service intercept data requested by a gateway through an interceptor, acquire two values of TraceId/RequestId and generate SpanId from the gateway, write the data into ThreadLocal through a SET method or write the data into MDC by calling a PUT method, and write the TraceId/RequestId/SpandeId/ServiceId/request parameter/request time/response time/return parameter into a log file.
And S5, reading and writing the log file into the Kafka in real time through the FileBeat, wherein the data is not screened yet and is only filtered.
And S6, reading the data in the Kafka by using Quarkus, searching according to three values of RequestId/ServiceId/TraceId, storing the values in Clickhouse, and performing persistence.
S7: and writing a page, and after the user successfully logs in, checking the log, and searching through the RequestId/ServiceId/TraceId.
In the embodiment, the request is intercepted at the request inlet, the link information data is recorded in the request, and the link information data is stored in the log file, so that the intruding type is low, the link information data does not need to be stored, and the link information data can be printed only in a log mode, thereby reducing the influence on the system performance. In addition, the link information in the log can be read, filtered, screened and stored in the database, and then the link information of each request is obtained in a page mode, so that the integrity of the project is ensured, the link data can be obtained more flexibly, and the flexibility of monitoring the link data is improved.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
In this embodiment, a link monitoring device is further provided, and the link monitoring device is used to implement the foregoing embodiments and preferred embodiments, which have already been described and are not described again. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 3 is a block diagram of a monitoring apparatus for a link according to an embodiment of the present invention, as shown in fig. 3, the apparatus including:
a first determining module 32, configured to determine a generation time for generating a target identifier in an intercepted user request, where the user request is a request intercepted at a request entry;
a second determining module 34, configured to determine an end time for completing execution of the user request;
an obtaining module 36, configured to obtain link data generated by a target link between the generation time and the end time, where the target link is a link formed by executing the user request;
a saving module 38, configured to save the link data into a log file, so as to monitor the target link through the log file.
In an example embodiment, the apparatus may be configured to intercept the user request in a target gateway before determining a generation time for generating a target identity in the intercepted user request, wherein the target gateway includes the request entry; generating the target identification in a request header of the user request; and storing the target identification in a header file requested by the user.
In an exemplary embodiment, the apparatus may enable generating the target identifier in a request header of the user request by at least one of: generating a tracking identifier in a request header of the user request, wherein the target identifier comprises the tracking identifier, and the tracking identifier is used for tracking a path called by the user request; generating a span identifier in a request header of the user request, wherein the target identifier comprises the span identifier, and the span identifier is used for identifying a position where the user request is located in a call; under the condition that the user request is a request sent by a target user, generating a request identifier in a request header of the user request, wherein the target user is a user who has not sent the request, the target identifier comprises the request identifier, and the request identifier is used for identifying the target user; and under the condition that other services need to be called when the user request is executed, generating a service identifier in a request header of the user request, wherein the target identifier comprises the service identifier.
In an exemplary embodiment, the saving module 38 may save the link data into the log file by: determining a request time when the user request is received and a request parameter included in the user request; determining response time responding to the user request and target parameters returned in response to the user request; and saving the target identification, the request time, the request parameters, the response time and the target parameters into the log file.
In an exemplary embodiment, the apparatus may be further configured to, after saving the link data into a log file to monitor the target link through the log file, screen a target log file from a first database based on the target identification; and storing the target log file into a second database.
In an exemplary embodiment, the apparatus may be further configured to store the log file in the first database before screening a target log file from the first database based on the target identification.
In an exemplary embodiment, the apparatus may be further configured to receive a query request input through a target page after saving the link data into a log file to monitor the target link through the log file, where the query request includes a query identifier; and searching the log file for a query log corresponding to the query identifier.
It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.
An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to perform the steps in any of the above method embodiments when executed.
In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to: various media capable of storing computer programs, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
Embodiments of the present invention also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the above method embodiments.
In an exemplary embodiment, the electronic apparatus may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.
For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary embodiments, and details of this embodiment are not repeated herein.
It will be apparent to those skilled in the art that the various modules or steps of the invention described above may be implemented using a general purpose computing device, they may be centralized on a single computing device or distributed across a network of computing devices, and they may be implemented using program code executable by the computing devices, such that they may be stored in a memory device and executed by the computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into various integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for monitoring a link, comprising:
determining generation time for generating a target identifier in an intercepted user request, wherein the user request is a request intercepted at a request entrance;
determining an end time for completing execution of the user request;
acquiring link data generated by a target link between the generation time and the ending time, wherein the target link is formed by executing the user request;
and saving the link data into a log file so as to monitor the target link through the log file.
2. The method of claim 1, wherein prior to determining a generation time for generating a target identification in an intercepted user request, the method further comprises:
intercepting the user request in a target gateway, wherein the target gateway comprises the request inlet;
generating the target identification in a request header of the user request;
and storing the target identification in a header file requested by the user.
3. The method of claim 2, wherein generating the target identification in a request header of the user request comprises at least one of:
generating a tracking identifier in a request header of the user request, wherein the target identifier comprises the tracking identifier, and the tracking identifier is used for tracking a path called by the user request;
generating a span identifier in a request header of the user request, wherein the target identifier comprises the span identifier, and the span identifier is used for identifying a position where the user request is located in a call; under the condition that the user request is a request sent by a target user, generating a request identifier in a request header of the user request, wherein the target user is a user who has not sent the request, the target identifier comprises the request identifier, and the request identifier is used for identifying the target user;
and under the condition that other services need to be called when the user request is executed, generating a service identifier in a request header of the user request, wherein the target identifier comprises the service identifier.
4. The method of claim 1, wherein saving the link data to a log file comprises:
determining a request time when the user request is received and a request parameter included in the user request;
determining response time responding to the user request and target parameters returned in response to the user request;
and saving the target identification, the request time, the request parameters, the response time and the target parameters into the log file.
5. The method of claim 1, wherein after saving the link data into a log file to monitor the target link via the log file, the method further comprises:
screening a target log file from a first database based on the target identification;
and storing the target log file into a second database.
6. The method of claim 5, wherein prior to screening target log files from the first database based on the target identification, the method further comprises:
and storing the log file into the first database.
7. The method of claim 1, wherein after saving the link data into a log file to monitor the target link via the log file, the method further comprises:
receiving a query request input through a target page, wherein the query request comprises a query identifier;
and searching the log file for a query log corresponding to the query identifier.
8. A link monitoring apparatus, comprising:
the system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for determining the generation time of generating a target identifier in an intercepted user request, and the user request is the request intercepted at a request entrance;
a second determining module, configured to determine an end time when the execution of the user request is completed;
an obtaining module, configured to obtain link data generated by a target link between the generation time and the end time, where the target link is a link formed by executing the user request;
and the storage module is used for storing the link data into a log file so as to monitor the target link through the log file.
9. A computer-readable storage medium, in which a computer program is stored, wherein the computer program is arranged to perform the method of any of claims 1 to 7 when executed.
10. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and wherein the processor is arranged to execute the computer program to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211296589.5A CN115766532A (en) | 2022-10-21 | 2022-10-21 | Link monitoring method and device, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211296589.5A CN115766532A (en) | 2022-10-21 | 2022-10-21 | Link monitoring method and device, storage medium and electronic device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115766532A true CN115766532A (en) | 2023-03-07 |
Family
ID=85352669
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211296589.5A Pending CN115766532A (en) | 2022-10-21 | 2022-10-21 | Link monitoring method and device, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115766532A (en) |
-
2022
- 2022-10-21 CN CN202211296589.5A patent/CN115766532A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111611021B (en) | Log data transmission method, device, computer equipment and storage medium | |
| CN109885496B (en) | Test log management method and system | |
| CN111723313A (en) | Page jump processing method, device, equipment and storage medium | |
| CN111367760B (en) | Log collection method and device, computer equipment and storage medium | |
| CN109726091B (en) | Log management method and related device | |
| CN112737800B (en) | Service node fault positioning method, call chain generating method and server | |
| CN116204438A (en) | Test case generation method, automatic test method and related device | |
| CN111400127A (en) | Service log monitoring method and device, storage medium and computer equipment | |
| CN116244339A (en) | Method, device, terminal and medium for fusing operation service monitoring data of business center | |
| CN115705190A (en) | Method and device for determining dependence degree | |
| CN112671878B (en) | Block chain information subscription method, device, server and storage medium | |
| CN112235128B (en) | Transaction path analysis method, device, server and storage medium | |
| CN112235124B (en) | Method and device for configuring pico-cell, storage medium and electronic device | |
| CN100382506C (en) | Method for verifying network-unit server in network management system | |
| CN115827374A (en) | Application log management method and device, electronic equipment and readable storage medium | |
| CN115766532A (en) | Link monitoring method and device, storage medium and electronic device | |
| CN112329021B (en) | Method and device for checking application loopholes, electronic device and storage medium | |
| CN113452533B (en) | Charging self-inspection and self-healing method and device, computer equipment and storage medium | |
| CN112597532A (en) | Monitoring method and device for sensitive data access | |
| CN114625595B (en) | Method, device and system for rechecking dynamic configuration information of service system | |
| CN113434399B (en) | Service node log processing method and device, storage medium and electronic device | |
| CN109684158A (en) | Method for monitoring state, device, equipment and the storage medium of distributed coordination system | |
| CN110196862B (en) | Data scene construction method, device, server and system | |
| CN114928530B (en) | Link information acquisition method and related device | |
| CN112417328B (en) | Webpage monitoring method and device |
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 |