CN113918426A - Method, system and equipment for realizing Redis access full link tracking - Google Patents
Method, system and equipment for realizing Redis access full link tracking Download PDFInfo
- Publication number
- CN113918426A CN113918426A CN202111494532.1A CN202111494532A CN113918426A CN 113918426 A CN113918426 A CN 113918426A CN 202111494532 A CN202111494532 A CN 202111494532A CN 113918426 A CN113918426 A CN 113918426A
- Authority
- CN
- China
- Prior art keywords
- log
- interface
- executable interface
- executable
- abnormal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- Databases & Information Systems (AREA)
- Mathematical Physics (AREA)
- Data Mining & Analysis (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a method, a system and equipment for realizing Redis access full link tracking, mainly relates to the technical field of link tracking, and is used for solving the technical problems that the conventional link tracking method is slow and can not timely perform exception capture. The method comprises the following steps: creating an executable interface through a Redis node; when the executable interface is triggered, calling a preset diagnostic log acquisition algorithm, an operation log detection algorithm and a buried point event to the executable interface; when the executable interface is executed, acquiring a diagnostic log corresponding to the executable interface through an acquisition diagnostic log algorithm; monitoring whether the diagnosis log is an abnormal log or not through an operation log detection algorithm; and when the diagnostic log is monitored to be an abnormal log, triggering a buried point event to upload an abnormal log capturing notice, and further determining that the executable interface is abnormal. By the method, the link tracking object can be automatically selected, and the technical effects of quickly tracking and timely capturing the abnormal log are achieved.
Description
Technical Field
The present application relates to the field of link tracking technologies, and in particular, to a method, a system, and a device for implementing Redis access full link tracking.
Background
With the continuous development of the internet and computer application technology, the daily calling data of a huge network service system can be in the billion level. In order to ensure the effective operation of the network service system, it is necessary to perform link tracking on each call data.
At present, the method for performing link tracking on call data mainly comprises the following steps: and (4) embedding points by adopting a log operation mode, and summarizing and recording one log every time a request is received. In the case of outbound, all outbound states need to be recorded in the memory, and finally, a log is spliced and output. And link series connection is carried out through the security node number.
However, the logs that need to be processed by the conventional link tracking method are very complex, so that the link tracking function is slow and abnormal acquisition cannot be performed in time.
Disclosure of Invention
In view of the above disadvantages in the prior art, the present invention provides a method, system and device for implementing Redis access full link tracking, so as to solve the above technical problems.
In a first aspect, an embodiment of the present application provides a method for implementing Redis access full link tracking, where the method includes: creating an executable interface through a Redis node; when the executable interface is triggered, calling a preset diagnostic log acquisition algorithm and an operation log detection algorithm to the executable interface; wherein, the operation log detection algorithm comprises a buried point event; when the executable interface is executed, acquiring a diagnostic log corresponding to the executable interface through an acquisition diagnostic log algorithm; monitoring whether the diagnosis log is an abnormal log or not through an operation log detection algorithm; and when the diagnostic log is monitored to be an abnormal log, determining that the executable interface is abnormal through an abnormal log capturing notice uploaded by the buried point event.
In an implementation manner of the present application, creating an executable interface through a Redis node specifically includes: acquiring a preset standard Redis node interface or an extended Redis node interface; the executable interface is created by calling a standard Redis node interface or an extended Redis node interface.
In one implementation of the present application, a first name is defined in an executable interface; the method comprises the steps of obtaining a diagnosis log class, wherein the obtained diagnosis log class at least comprises a second name of the diagnosis log claimed by a diagnosis log algorithm, a program written in the diagnosis log and a third name of the diagnosis log written by the program; wherein the first name, the second name and the third name are consistent.
In one implementation of the present application, a point burying event is used to report a status notification of an executable interface in real time; wherein the status notification includes a create log notification, a normal log notification, and an abnormal log capture notification.
In an implementation manner of the present application, a serialization component is preset in the executable interface, and the serialization component includes any one or more of the following items: a serialization subinterface and an deserialization subinterface; executing the executable interface, specifically including: the executable interface is executed by executing the serialization component.
In a second aspect, an embodiment of the present application provides a system for implementing Redis access full link tracking, where the system includes: the creating module is used for creating an executable interface through a Redis node; the calling module is used for calling a preset diagnostic log obtaining algorithm, an operation log detection algorithm and a buried point event to the executable interface when the executable interface is triggered; the acquisition module is used for acquiring a diagnosis log corresponding to the executable interface by acquiring a diagnosis log algorithm when the executable interface is executed; the monitoring module is used for monitoring whether the diagnosis log is an abnormal log or not through an operation log detection algorithm; and the receiving module is used for receiving the abnormal log capturing notice uploaded by the embedded point event when the diagnostic log is monitored to be an abnormal log.
In a third aspect, an embodiment of the present application provides a device for implementing Redis access full link tracing, where the device includes a processor, a memory, and an execution instruction stored on the memory, and the execution instruction is configured to, when executed by the processor, enable the device to perform any one of the above methods for implementing Redis access full link tracing.
As can be appreciated by those skilled in the art, the present invention has at least the following beneficial effects: the executable interface for monitoring is established by the Redis node, purposeful monitoring of execution data is realized, resource loss caused by traditional monitoring of all execution data is avoided, and the technical effect of accurate monitoring is realized. The technical effect of acquiring the diagnostic log corresponding to the executable interface in real time or at regular time is realized by acquiring the diagnostic log algorithm, the technical effect of consuming and monitoring the diagnostic log is realized by operating the log detection algorithm, the technical effect of checking the upper diagnostic log in real time or at regular time is learned by the buried point event, and the abnormal log capturing notice is quickly uploaded.
Drawings
Some embodiments of the disclosure are described below with reference to the accompanying drawings, in which:
fig. 1 is a flowchart of a method for implementing Redis access full link tracking according to an embodiment of the present disclosure.
Fig. 2 is a schematic diagram of an internal structure of a system for implementing Redis access full link tracking according to an embodiment of the present application.
Fig. 3 is a schematic diagram of an internal structure of a device for implementing Redis access full link tracking according to an embodiment of the present application.
Detailed Description
It should be understood by those skilled in the art that the embodiments described below are only preferred embodiments of the present disclosure, and do not mean that the present disclosure can be implemented only by the preferred embodiments, which are merely for explaining the technical principles of the present disclosure and are not intended to limit the scope of the present disclosure. All other embodiments that can be derived by one of ordinary skill in the art from the preferred embodiments provided by the disclosure without undue experimentation will still fall within the scope of the disclosure.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The execution subject of the method for realizing Redis access full link tracking, which is proposed in the embodiment of the application, is the server.
The technical solutions proposed in the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 1 is a method for implementing Redis access full link tracking according to an embodiment of the present disclosure. As shown in fig. 1, the full link tracking method provided in the embodiment of the present application mainly includes the following steps:
and step 101, creating an executable interface through a Redis node.
It should be noted that the Redis node may include a standard Dictionary service and/or an extended Dictionary service, for example, a Redis node (Remote Dictionary Server). The executable interface is any possible operational interface capable of running. Illustratively, the serialization component is preset in the executable interface, and any one or more of the following components are included in the serialization component: a serialization subinterface and an deserialization subinterface.
Creating an executable interface through a Redis node may specifically be: acquiring a preset standard Redis node interface or an extended Redis node interface; the executable interface is created by calling a standard Redis node interface or an extended Redis node interface.
It should be noted that, the specific process of creating the executable interface through the interface may be implemented by an existing method or device, and this application is not limited to this.
And 102, calling a preset diagnostic log obtaining algorithm and an operation log detection algorithm to the executable interface when the executable interface is triggered.
It should be noted that, a first name is defined in the executable interface; the first name may be a preset name or a name set by an operator. The obtaining diagnostic log algorithm is an algorithm capable of generating a diagnostic log, and illustratively, the obtaining diagnostic log algorithm includes at least a second name of the diagnostic log claimed by the obtaining diagnostic log algorithm, a program written in the diagnostic log, and a third name of the diagnostic log written by the program; wherein the first name, the second name and the third name are consistent. It should be noted that the meaning of the diagnostics log claimed by the algorithm for obtaining the diagnostics log is: the get diagnostics log algorithm generates diagnostics logs through the monitored executable interface. It can be understood by those skilled in the art that, for the purpose of implementing the specified execution operation/data monitoring, the (executable interface) name unification operation is required to be performed on the monitored target during the running process of the program, so as to avoid that the operation of generating the diagnostic log cannot be performed. The operation log detection algorithm is an algorithm capable of detecting whether the content in the diagnosis log is abnormal, and the operation of detecting whether the diagnosis log is abnormal can be realized by inputting the range of abnormal data in advance. The operation log detection algorithm comprises a buried point event, and the buried point event can be used for reporting the state notification of the executable interface in real time; wherein the status notification includes a create log notification, a normal log notification, and an abnormal log capture notification.
Further, the condition that an executable interface is triggered is the detection that the executable interface is run by any interface or algorithm. The specific method and process for calling the algorithm to the executable interface can be implemented by the existing method or equipment, and the application does not limit the method and the equipment excessively.
And 103, when the executable interface is executed, acquiring a diagnosis log corresponding to the executable interface by the diagnosis log acquiring algorithm.
It should be noted that the serialization component is preset in the executable interface, and the serialization component includes any one or more of the following items: a serialization subinterface and an deserialization subinterface. The executing the executable interface may specifically include: the executable interface is executed by executing the serialization component.
The obtaining of the diagnostic log algorithm obtains the diagnostic log corresponding to the executable interface, and may specifically be that a preset write operation exists in the diagnostic log algorithm, an operation of reading the executable interface through the preset write operation is obtained, and then an execution operation of the executable interface is automatically written into the diagnostic log. It can be known that the diagnostic log further includes an execution operation of the executable interface, and after the execution operation is obtained, it is beneficial to quickly diagnose/consume whether the executable interface is abnormal.
And step 104, monitoring whether the diagnosis log is an abnormal log or not through an operation log detection algorithm.
Specifically, an abnormal condition database is preset in the operation log detection algorithm, the abnormal condition database includes all conditions satisfying the abnormal log, the operation log detection algorithm imports the diagnosis log into the abnormal condition database after acquiring the diagnosis log, and when any condition satisfying the abnormal log exists in the diagnosis log, the operation log detection algorithm judges that the diagnosis log is the abnormal log.
And 105, when the diagnostic log is monitored to be an abnormal log, determining that the executable interface is abnormal through an abnormal log capturing notice uploaded by the buried point event.
It should be noted that the embedded point event can be used to report the state notification of the executable interface in real time; wherein the status notification includes a create log notification, a normal log notification, and an abnormal log capture notification.
Specifically, the embedded point event obtains a judgment result generated by an operation log detection algorithm in real time according to the diagnosis log, and when the judgment result is not an abnormal log, the embedded point event uploads normal information to the server (it needs to be noted that the normal information can be presented through normal log notification); when the judgment result is an abnormal log, the buried point event uploads abnormal information to the server (it should be noted that the normal information can be presented by capturing a notification through the abnormal log). After receiving the abnormal log capture notification, the server can know that the executable interface has an abnormality.
Based on the foregoing description, those skilled in the art can understand that the present invention has at least the following advantages: the executable interface for monitoring is established by the Redis node, purposeful monitoring of execution data is realized, resource loss caused by traditional monitoring of all execution data is avoided, and the technical effect of accurate monitoring is realized. The technical effect of acquiring the diagnostic log corresponding to the executable interface in real time or at regular time is realized by acquiring the diagnostic log algorithm, the technical effect of consuming and monitoring the diagnostic log is realized by operating the log detection algorithm, the technical effect of checking the upper diagnostic log in real time or at regular time is learned by the buried point event, and the abnormal log capturing notice is quickly uploaded.
In addition, an embodiment of the present application further provides a system for implementing Redis access full link tracking, as shown in fig. 2, the system includes: a creation module 201, a calling module 202, an acquisition module 203, a monitoring module 204, and a determination module 205.
A creating module 201, configured to create an executable interface through a Redis node;
the calling module 202 is configured to call a preset diagnostic log obtaining algorithm and an operation log detection algorithm to the executable interface when the executable interface is triggered; wherein, the operation log detection algorithm comprises a buried point event;
the obtaining module 203 is configured to obtain a diagnostic log corresponding to the executable interface through a diagnostic log obtaining algorithm when the executable interface is executed;
the monitoring module 204 is configured to monitor whether the diagnostic log is an abnormal log through an operation log detection algorithm;
the determining module 205 is configured to, when it is monitored that the diagnostic log is an abnormal log, determine that the executable interface is abnormal through an abnormal log capture notification uploaded by the buried point event.
Besides, the embodiment of the present application further provides a device for implementing Redis access full link trace, as shown in fig. 3, on which executable instructions are stored, and when the executable instructions are executed, a method for implementing Redis access full link trace as described above is implemented. Specifically, the server sends an execution instruction to the memory through the bus, and when the memory receives the execution instruction, sends an execution signal to the processor through the bus so as to activate the processor.
It should be noted that, the processor is configured to create an executable interface through the Redis node; when the executable interface is triggered, calling a preset diagnostic log acquisition algorithm and an operation log detection algorithm to the executable interface; wherein, the operation log detection algorithm comprises a buried point event; when the executable interface is executed, acquiring a diagnostic log corresponding to the executable interface through an acquisition diagnostic log algorithm; monitoring whether the diagnosis log is an abnormal log or not through an operation log detection algorithm; and when the diagnostic log is monitored to be an abnormal log, determining that the executable interface is abnormal through an abnormal log capturing notice uploaded by the buried point event.
So far, the technical solutions of the present disclosure have been described in connection with the foregoing embodiments, but it is easily understood by those skilled in the art that the scope of the present disclosure is not limited to only these specific embodiments. The technical solutions in the above embodiments can be split and combined, and equivalent changes or substitutions can be made on related technical features by those skilled in the art without departing from the technical principles of the present disclosure, and any changes, equivalents, improvements, and the like made within the technical concept and/or technical principles of the present disclosure will fall within the protection scope of the present disclosure.
Claims (7)
1. A method for enabling Redis access full link trace, the method comprising:
creating an executable interface through a Redis node;
when the executable interface is triggered, calling a preset diagnostic log acquisition algorithm and an operation log detection algorithm to the executable interface; wherein the operation log detection algorithm comprises a buried point event;
when the executable interface is executed, acquiring a diagnostic log corresponding to the executable interface through the diagnostic log acquiring algorithm;
monitoring whether the diagnosis log is an abnormal log or not through an operation log detection algorithm;
and when the diagnostic log is monitored to be the abnormal log, triggering the buried point event to upload an abnormal log capturing notice, and further determining that the executable interface is abnormal.
2. The method for implementing Redis access full link tracing according to claim 1, wherein the creating an executable interface through a Redis node specifically comprises:
acquiring a preset standard Redis node interface or an extended Redis node interface;
and creating an executable interface by calling the standard Redis node interface or the extended Redis node interface.
3. The method for Redis access full Link Trace implementation according to claim 1,
defining a first name in the executable interface;
the obtaining of the diagnostic log class comprises at least a second name of the diagnostic log claimed by the obtaining of the diagnostic log algorithm, a program written in the log, and a third name of the log written by the program;
wherein the first name, the second name and the third name are consistent.
4. The method for Redis access full Link Trace implementation according to claim 1,
the embedded point event is used for reporting the state notification of the executable interface in real time; wherein the status notification includes a create log notification, a normal log notification, and an abnormal log capture notification.
5. The method for Redis access full Link Trace implementation according to claim 1,
the method comprises the following steps that a serialization component is preset in an executable interface, and the serialization component comprises any one or more of the following items: a serialization subinterface and an deserialization subinterface;
executing the executable interface, specifically including:
the executable interface is executed by executing the serialization component.
6. A system for implementing Redis access full link tracing, the system comprising:
the creating module is used for creating an executable interface through a Redis node;
the calling module is used for calling a preset diagnostic log obtaining algorithm and an operation log detection algorithm to the executable interface when the executable interface is triggered; wherein the operation log detection algorithm comprises a buried point event;
the acquisition module is used for acquiring a diagnostic log corresponding to the executable interface through the diagnostic log acquisition algorithm when the executable interface is executed;
the monitoring module is used for monitoring whether the diagnosis log is an abnormal log or not through the operation log detection algorithm;
and the determining module is used for triggering the abnormal log capturing notice uploaded by the buried point event when the diagnostic log is monitored to be the abnormal log, and further determining that the executable interface is abnormal.
7. An apparatus for enabling Redis Access full Link tracing, the apparatus comprising:
a processor;
and a memory having executable code stored thereon, which when executed, causes the processor to perform a method of implementing Redis Access full Link Trace as claimed in any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111494532.1A CN113918426A (en) | 2021-12-09 | 2021-12-09 | Method, system and equipment for realizing Redis access full link tracking |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111494532.1A CN113918426A (en) | 2021-12-09 | 2021-12-09 | Method, system and equipment for realizing Redis access full link tracking |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113918426A true CN113918426A (en) | 2022-01-11 |
Family
ID=79248784
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111494532.1A Pending CN113918426A (en) | 2021-12-09 | 2021-12-09 | Method, system and equipment for realizing Redis access full link tracking |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113918426A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109104302A (en) * | 2018-07-18 | 2018-12-28 | 杭州鑫合汇互联网金融服务有限公司 | A kind of full link tracing monitoring method |
| CN110245035A (en) * | 2019-05-20 | 2019-09-17 | 平安普惠企业管理有限公司 | A kind of link trace method and device |
| CN111752799A (en) * | 2020-06-24 | 2020-10-09 | 中国建设银行股份有限公司 | Service link tracking method, device, equipment and storage medium |
| CN112181927A (en) * | 2019-07-04 | 2021-01-05 | 北京航天长峰科技工业集团有限公司 | Log auditing method under micro-service architecture |
| CN112256530A (en) * | 2020-10-27 | 2021-01-22 | 广州助蜂网络科技有限公司 | Log service method capable of tracking link and system thereof |
| CN112395180A (en) * | 2020-12-10 | 2021-02-23 | 南威软件股份有限公司 | Method for realizing service log full link tracking |
| CN112910945A (en) * | 2020-12-08 | 2021-06-04 | 江苏苏宁云计算有限公司 | Request link tracking method and service request processing method |
| CN113312241A (en) * | 2021-06-29 | 2021-08-27 | 中国农业银行股份有限公司 | Abnormal alarm method, access log generation method and operation and maintenance system |
-
2021
- 2021-12-09 CN CN202111494532.1A patent/CN113918426A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109104302A (en) * | 2018-07-18 | 2018-12-28 | 杭州鑫合汇互联网金融服务有限公司 | A kind of full link tracing monitoring method |
| CN110245035A (en) * | 2019-05-20 | 2019-09-17 | 平安普惠企业管理有限公司 | A kind of link trace method and device |
| CN112181927A (en) * | 2019-07-04 | 2021-01-05 | 北京航天长峰科技工业集团有限公司 | Log auditing method under micro-service architecture |
| CN111752799A (en) * | 2020-06-24 | 2020-10-09 | 中国建设银行股份有限公司 | Service link tracking method, device, equipment and storage medium |
| CN112256530A (en) * | 2020-10-27 | 2021-01-22 | 广州助蜂网络科技有限公司 | Log service method capable of tracking link and system thereof |
| CN112910945A (en) * | 2020-12-08 | 2021-06-04 | 江苏苏宁云计算有限公司 | Request link tracking method and service request processing method |
| CN112395180A (en) * | 2020-12-10 | 2021-02-23 | 南威软件股份有限公司 | Method for realizing service log full link tracking |
| CN113312241A (en) * | 2021-06-29 | 2021-08-27 | 中国农业银行股份有限公司 | Abnormal alarm method, access log generation method and operation and maintenance system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111817891A (en) | Network fault processing method and device, storage medium and electronic equipment | |
| CN108038039B (en) | Method for recording log and micro-service system | |
| CN111382023B (en) | Code fault positioning method, device, equipment and storage medium | |
| CN113708986B (en) | Server monitoring apparatus, method and computer-readable storage medium | |
| CN111881014A (en) | System test method, device, storage medium and electronic equipment | |
| CN110245077A (en) | A kind of response method and equipment of program exception | |
| CN112035354A (en) | Method, device and equipment for positioning risk code and storage medium | |
| CN115952081A (en) | Software testing method, device, storage medium and equipment | |
| CN109597389B (en) | Test system of embedded control system | |
| CN105825641A (en) | Service alarm method and apparatus | |
| CN112100035A (en) | Page abnormity detection method, system and related device | |
| CN113918426A (en) | Method, system and equipment for realizing Redis access full link tracking | |
| CN114817035B (en) | Software testing method, device, equipment and medium | |
| CN116230067A (en) | Automatic testing method, system, equipment and medium for solid state disk | |
| CN115757107A (en) | Embedded point detection method, device, server and storage medium | |
| CN114780412A (en) | Page testing method, system, device and medium | |
| CN111737158B (en) | Abnormal assertion processing method and device, electronic equipment and storage medium | |
| CN113360360A (en) | Service system fault detection method and device, electronic equipment and storage medium | |
| CN113468029A (en) | Log management method and device, electronic equipment and readable storage medium | |
| CN114579342A (en) | Fault detection method and device, electronic equipment and storage medium | |
| CN112131110A (en) | Multisource heterogeneous data probe method and device of smart phone system | |
| CN113342596A (en) | Distributed monitoring method, system and device for equipment indexes | |
| CN113901460A (en) | Method and device for detecting illegal file of cloud disk, computer equipment and storage medium | |
| CN105827447A (en) | Service alarm method and apparatus | |
| CN111639249A (en) | Automatic monitoring method, device and equipment for user feedback error reporting |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220111 |
|
| RJ01 | Rejection of invention patent application after publication |