CN105591821B - Monitoring system and service system - Google Patents
Monitoring system and service system Download PDFInfo
- Publication number
- CN105591821B CN105591821B CN201610007083.6A CN201610007083A CN105591821B CN 105591821 B CN105591821 B CN 105591821B CN 201610007083 A CN201610007083 A CN 201610007083A CN 105591821 B CN105591821 B CN 105591821B
- Authority
- CN
- China
- Prior art keywords
- interface
- service
- log
- call
- calling
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- 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
-
- 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a monitoring system, comprising: the calling chain model storage unit is used for storing one or more service calling chain models, and each service calling chain model records a called interface according to the upstream and downstream relation of the called interface in each service system related to a corresponding service flow; and the log storage unit is used for storing an interface call log of an interface in the service call chain model. The invention also provides a service system, comprising: a calling chain model segment storage unit for storing one or more service calling chain model segments related to the service system, wherein each service calling chain model segment is a part of a corresponding service calling chain model, which records a called interface of the service system; the log generating unit is used for generating an interface calling log when an interface of the service system is called; and the log uploading unit is used for uploading the interface calling log of the interface contained in the service calling chain model fragment to the monitoring system.
Description
Technical Field
The present invention relates generally to computer systems, and more particularly to business systems and monitoring systems that monitor the business systems.
Background
With the use of computer systems in more and more complex application fields, one business process often spans multiple business systems at the same time. For example, a purchase business process of a consumer on an e-commerce platform may involve a merchandise display business system, an order business system, a payment business system, an inventory management business system, a logistics business system, etc., each business system corresponding to a business involved in the business process. In order to realize comprehensive and efficient monitoring of the business process, a plurality of systems need to be spanned, the data of the whole business call chain is tracked, the comprehensive analysis and the early warning are carried out in time, and the online problems of all business systems are positioned efficiently and accurately.
In the prior art, a unified monitoring system is used for solving the problem, a log collector is installed on each service system server, a client of the monitoring system is embedded in each service system, and an interface calling log is generated and stored locally when an interface of the service system is called. And the log collector on each service system server uploads the local logs to the monitoring center at regular time. And the monitoring center analyzes the log data in real time and makes corresponding threshold early warning. Such system monitoring has no overall concept and cannot monitor call chains between multiple systems spanned by each business process. Due to the configuration loss on the monitoring platform, as long as the client generates the log, the log collector can push the log to the monitoring center, and bandwidth resources and storage resources are wasted. After a problem occurs in a service system, the alarming service system is not necessarily a service system which really generates an error, and in many cases, problems are generated in other dependent service systems, and are exposed in the service system, so that the problem positioning speed is slow because other service systems which the service system depends on are checked one by one manually.
Disclosure of Invention
One aspect of the present invention provides a monitoring system comprising: the calling chain model storage unit is used for storing one or more service calling chain models, and each service calling chain model records a called interface according to the upstream and downstream relation of the called interface in each service system related to a corresponding service flow; and the log storage unit is used for storing an interface call log of an interface in the service call chain model.
Another aspect of the present invention provides a business system, including: a calling chain model fragment storage unit for storing one or more service calling chain model fragments related to the service system, wherein each service calling chain model records the called interface according to the upstream and downstream relationship of the called interface in each service system related to a corresponding service flow, and each service calling chain model fragment is a part of the corresponding service calling chain model, which records the called interface of the service system; the log generating unit is used for generating an interface calling log when an interface of the service system is called; and the log uploading unit is used for uploading the interface calling log of the interface contained in the service calling chain model fragment to the monitoring system.
Drawings
For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
fig. 1 schematically shows a block diagram of a monitoring system and a business system according to an embodiment of the invention.
Fig. 2 schematically shows a traffic monitoring flow diagram according to an embodiment of the invention.
Detailed Description
Other aspects, advantages and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention.
In the present invention, the terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation; the term "or" is inclusive, meaning and/or.
In this specification, the various embodiments described below which are meant to illustrate the principles of this invention are illustrative only and should not be construed in any way to limit the scope of the invention. The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. The following description includes various specific details to aid understanding, but such details are to be regarded as illustrative only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Moreover, descriptions of well-known functions and constructions are omitted for clarity and conciseness. Moreover, throughout the drawings, the same reference numerals are used for similar functions and operations.
Fig. 1 schematically shows a block diagram of a monitoring system 100 and a business system 200 according to an embodiment of the invention.
As shown in fig. 1, the monitoring system 100 includes a call chain model storage unit 110 and a log storage unit 120.
The call chain model storage unit 110 stores one or more service call chain models, and each service call chain model records a called interface according to an upstream-downstream relationship of the called interface in each service system involved in a corresponding service flow. For example, the call chain model storage unit 110 may store a call chain model of a shopping business process, in which called interfaces in each business system (including, for example, a commodity exhibition business system, an order business system, a payment business system, an inventory management business system, a logistics business system, etc.) involved in the shopping business process are recorded in an upstream-downstream relationship. Thus, based on the call chain model of the shopping business process, it is known which interfaces in each business system involved are called.
The log storage unit 120 stores an interface call log of an interface in the service call chain model.
According to an embodiment of the present invention, the monitoring system 100 may further include a call chain model access unit 130. The system person in charge can add, delete, or modify the call chain model stored in the call chain model storage unit 110 via the call chain model access unit 130. When a call chain model is added, deleted, or modified, the monitoring system 100 transmits a corresponding change message reflecting the addition, deletion, or modification to the business system 200 via the call chain model access unit 130. When the business system 200 starts up, the business system 200 can acquire a business call chain model segment related to its own interface via the call chain model access unit 130. Since one service call chain model may involve several service systems, each service system only needs to acquire the fragment in which its own called interface is recorded, and does not need to acquire the fragments of other service systems. Of course, each business system may also obtain and store the entire business invocation model associated with that business system. According to the embodiment of the present invention, the service system 200 may obtain the service call chain model segment related to its own interface according to any one of the following ways: the monitoring system 100 periodically pushes, call back mechanisms, polling of various business systems, or distributed application coordination services ("zookeeper").
According to an embodiment of the present invention, the monitoring system 100 may further include a log access unit 140 that stores a log of interface calls from the service system in a log storage unit. According to the embodiment of the present invention, the interface call log may include a unique call log key representing the service flow generated in the corresponding service call chain when the interface is called, and the call log key is the same for all called interfaces in the service chain. According to an embodiment of the present invention, the call log key may be generated by the first business system in the call chain and sequentially passed to the business systems in the call chain. According to an embodiment of the present invention, the interface call log may further include identification information of the service call chain model that generated the call, for example, a service call chain model ID, and the model identification information may be used to distinguish different service call chain models. The log access unit 140 stores the interface call logs (i.e., the interface call logs from the service system in the same call chain model and belonging to the same service process) with the same service call chain model and the same call log key as an interface call log group in the log storage unit 120, and performs subsequent report, query and/or alarm operations based on the interface call log group. According to the embodiment of the invention, the interface call log comprises the entry of the interface, the return value, the call chain model identification information related to the call and the unique call log key representing the business process when the interface is called. When the interface is abnormal in calling, the interface calling log also comprises the abnormal information of the interface.
According to an embodiment of the present invention, the monitoring system 100 may further include a service monitoring unit 150, which obtains the log stored in the log storage unit 120 through the log access unit 140. The service monitoring unit 150 performs at least one of the following operations based on the interface call log group: the interface calling log group is used as report information and is periodically pushed to a system principal; when the abnormal information exists in the interface calling log, the interface calling abnormality and all the interface calling logs on the whole calling chain are pushed to a system responsible person; or when receiving a query request for the interface call log, presenting the query result in a mode of determining an interface call log group by two conditions of call chain model identification information containing the corresponding interface and the call log key of the interface, or presenting the query result in a paging mode according to different call chain models containing the corresponding interface.
The business system 200 includes a call chain model fragment storage unit 210, a log generation unit 220, and a log upload unit 230.
The call chain model fragment storage unit 210 stores one or more service call chain model fragments related to the service system 200, where each service call chain model records a called interface in each service system involved in a corresponding service process according to an upstream-downstream relationship of the called interface, and each service call chain model fragment is a part of the corresponding service call chain model in which the called interface of the service system is recorded. According to embodiments of the invention, business system 200 may also obtain or store the entire call chain model associated with itself.
Log generating section 220 generates an interface call log when an interface of business system 200 is called. For example, when an interface of business system 200 is called, log generation section 220 determines whether or not the interface is described in a certain call chain model or a call chain model segment, and if so, generates an interface call log for the interface. According to an embodiment of the present invention, the interface call log includes an entry of the interface, a return value, call chain model identification information (e.g., call chain model ID) associated with the call, and a unique call log key representing the business process when the interface is called. When the interface is abnormal in calling, the interface calling log also comprises the abnormal information of the interface.
The log uploading unit 230 uploads the interface call log of the interface included in the service call chain model fragment to the monitoring system. According to the embodiment of the present invention, whether the called interface is recorded in a certain call chain model or a call chain model segment may be determined by the log generating unit 220 or the log uploading unit 230. If the log generating unit 220 makes this determination, the log uploading unit 230 does not make this determination any more, but directly uploads the interface call log. On the other hand, the log generation unit 220 may not perform this determination, but may generate interface call logs for all called interfaces, and the log upload unit 230 may upload only the interface call logs of the interfaces described in a certain call chain model or call chain model segment. In this case, the log uploading unit 230 may be responsible for adding a call chain model ID and a call log key to the interface call log.
According to the embodiment of the present invention, the service system 200 may further include a call chain model fragment access unit 240, which obtains the one or more service call chain model fragments related to the interface of the service system from the monitoring system and stores the one or more service call chain model fragments in the call chain model fragment storage unit when the service system is started. The call chain model fragment access unit 240 may request the monitoring system 100 to send only the service call chain model fragment related to itself, or may intercept the service call chain model fragment related to itself after pulling the entire model locally. When the call chain model segment access unit 240 receives a call chain model change message from the monitoring system 100 after the service system 200 is started, the corresponding call chain model segment in the call chain model segment storage unit 210 is updated according to the call chain model change message related to the present system. According to the embodiment of the present invention, the service system 200 obtains the service call chain model segment related to its own interface according to any one of the following ways: the monitoring system 100 periodically pushes, call back mechanisms, polling of various business systems, or distributed application coordination services.
According to an embodiment of the present invention, message transmission between the monitoring system 100 and the service system 200 may be performed through the message middleware 300.
Fig. 2 schematically shows a traffic monitoring flow diagram according to an embodiment of the invention. As shown in fig. 2, a call chain model is preconfigured in the monitoring system 100. After the business system 200 is started, the call chain model fragment related to the business system is acquired from the monitoring system 100 and stored. When there is an update to the call chain model in monitoring system 100, a change message reflecting the update is sent to business system 200. Business system 200 updates its own call chain model fragment accordingly. The calling chain model can be changed in a centralized way at the monitoring system 100 and is informed to each business system 200 in time, so that the synchronism and the real-time performance of the whole system are ensured.
When an interface of business system 200 is called, an interface call log that calls an interface in the chain model is sent to monitoring system 100. In this way, business system 200 does not have to collect and upload interface call logs for interfaces not included in the call chain model, reducing network and storage resource overhead.
The monitoring system carries out regular pushing of report information, daily real-time pushing of interface calling, query response of interface calling conditions and the like based on the interface calling log. According to the embodiment of the invention, the interface call logs of the same business process belonging to the same call chain model are stored as a group. Therefore, when any interface is abnormal, the interface call logs of all interfaces on the whole call chain model can be provided together, so that a system leader can have global control capability on all service systems related to the whole service process, and information is centralized and fully prepared. Meanwhile, because the interface call logs of all interfaces on the whole call chain model are provided together, detailed information (such as entry parameters, return values, exceptions and the like) of all interfaces on the whole call chain can be searched no matter which service system the exception is exposed from, and the system on which each system depends does not need to be searched one by one, so that the system generating the exception can be quickly and accurately positioned.
According to an embodiment of the present invention, message transmission between the monitoring system 100 and the service system 200 may be performed through the message middleware 300.
The monitoring system 100, the business system 200, the message middleware 300, and the units therein according to the embodiments of the present invention may be implemented by an electronic device with computing capability executing software containing computer instructions. The computing-capable electronic device may be, but is not limited to, a general-purpose processor, a digital signal processor, a special-purpose processor, a reconfigurable processor, and the like. Execution of such instructions causes the electronic device to be configured to perform the operations described above in accordance with the present invention. The above devices and/or components may be implemented in one electronic device, or may be implemented in different electronic devices. Such software may be stored in a computer readable storage medium. The computer readable storage medium stores one or more programs (software modules) comprising instructions which, when executed by one or more processors in the electronic device, cause the electronic device to perform the methods of the present invention.
Such software may be stored in the form of volatile memory or non-volatile storage (such as storage devices like ROM), whether erasable or rewritable, or in the form of memory (e.g. RAM, memory chips, devices or integrated circuits), or on optically or magnetically readable media (such as CD, DVD, magnetic disks or tapes, etc.). It should be appreciated that the storage devices and storage media are embodiments of machine-readable storage suitable for storing one or more programs that include instructions, which when executed, implement embodiments of the present invention. Embodiments provide a program and a machine-readable storage device storing such a program, the program comprising code for implementing an apparatus or method as claimed in any one of the claims of the invention. Further, these programs may be delivered electronically via any medium (e.g., communication signals carried via a wired connection or a wireless connection), and embodiments suitably include these programs.
The devices and/or components of monitoring system 100, business system 200, messaging middleware 300, and the various elements therein, may also be implemented using hardware or firmware, such as Field Programmable Gate Arrays (FPGAs), Programmable Logic Arrays (PLAs), systems on a chip, systems on a substrate, systems on a package, Application Specific Integrated Circuits (ASICs), or in any other suitable manner for integrating or packaging circuits, or in any suitable combination of software, hardware, and firmware implementations. When implemented in these manners, the software, hardware, and/or firmware used is programmed or designed to perform the corresponding above-described methods, steps, and/or functions according to the present invention. One skilled in the art can implement one or more of these systems and modules, or one or more portions thereof, using different implementations as appropriate to the actual needs. All of these implementations fall within the scope of the present invention.
While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents. Accordingly, the scope of the present invention should not be limited to the above-described embodiments, but should be defined not only by the appended claims, but also by equivalents thereof.
Claims (15)
1. A monitoring system, comprising:
the calling chain model storage unit is used for storing one or more service calling chain models, and each service calling chain model records a called interface according to the upstream and downstream relation of the called interface in each service system related to a corresponding service flow;
the log storage unit is used for storing an interface calling log of an interface in the service calling chain model;
the log access unit is used for storing the interface call log from the service system in the log storage unit; and
a call chain model access unit via which the system principal adds, deletes, or modifies the call chain model stored in the call chain model storage unit,
wherein:
when the service system is started, the service system acquires a service call chain model segment related to a self interface through the call chain model access unit; and
when a call chain model is added, deleted, or modified, the monitoring system sends a corresponding update message to the business system via the call chain model access unit.
2. A monitoring system according to claim 1, wherein the service system obtains the service call chain model fragment related to its own interface according to any one of the following ways: the monitoring system periodically pushes, calls back a mechanism, polls each business system, or coordinates services for distributed applications.
3. The monitoring system of claim 1, wherein:
the interface call log contains: when the interface is called, generating a unique calling log key representing the business process in a corresponding business calling chain, wherein the calling log key is the same for all called interfaces in the business calling chain; generating model identification information of the called service calling chain;
the log access unit stores the interface call logs with the same model identification information and the same call log key into a group in the log storage unit, and performs subsequent report, query and/or alarm operation based on the interface call log group.
4. The monitoring system of claim 3, further comprising:
the service monitoring unit executes at least one of the following operations based on the interface call log group:
the interface calling log group is used as report information and is periodically pushed to a system principal;
when the abnormal information exists in the interface calling log, the interface calling abnormality and all the interface calling logs on the whole calling chain are pushed to a system responsible person;
when receiving a query request for the interface call log, presenting a query result in a mode of determining an interface call log group by two conditions of call chain model identification information containing a corresponding interface and a call log key of the interface, or presenting the query result in a paging mode according to different call chain models containing the corresponding interface.
5. The monitoring system of claim 1, wherein:
the interface call log comprises the entry of the interface, a return value, call chain model identification information related to the call and a unique call log key representing the business process when the interface is called; and
when the interface is abnormal in calling, the interface calling log also comprises the abnormal information of the interface.
6. A business system comprising:
a calling chain model fragment storage unit for storing one or more service calling chain model fragments related to the service system, wherein each service calling chain model records the called interface according to the upstream and downstream relationship of the called interface in each service system related to a corresponding service flow, and each service calling chain model fragment is a part of the corresponding service calling chain model, which records the called interface of the service system;
the log generating unit is used for generating an interface calling log when an interface of the service system is called; and
and the log uploading unit is used for uploading the interface calling log of the interface contained in the service calling chain model fragment to the monitoring system.
7. The business system of claim 6 further comprising:
and the calling chain model fragment access unit is used for acquiring the one or more service calling chain model fragments related to the interface of the service system from the monitoring system when the service system is started and storing the one or more service calling chain model fragments in the calling chain model fragment storage unit.
8. The business system of claim 7 wherein:
when the calling chain model segment access unit receives a calling chain model change message from the monitoring system after the service system is started, the corresponding calling chain model segment in the calling chain model segment storage unit is updated according to the calling chain model change message related to the system.
9. The business system of claim 7, wherein the business call chain model segment related to the self interface is obtained according to any one of the following modes: the monitoring system periodically pushes, calls back a mechanism, polls each business system, or coordinates services for distributed applications.
10. The business system of claim 6 wherein:
the log generation unit generates an interface call log only for the interfaces included in the service call chain model.
11. The business system of claim 6 wherein:
the interface call log comprises the entry and return values of the interface, call chain model identification information related to the call, a unique call log key representing the service flow and model identification information of the service call chain generating the call when the interface is called; and
when the interface is abnormal in calling, the interface calling log also comprises the abnormal information of the interface.
12. The system of claim 6, wherein:
the call chain model fragment storage unit stores one or more service call chain model fragments related to the service system.
13. A service monitoring method based on the monitoring system of any one of claims 1 to 5 and the service system of any one of claims 6 to 12, comprising:
and when the interface of the service system is called, sending the interface calling log of the interface in the service calling chain model segment to the monitoring system.
14. A computer device, comprising:
one or more processors;
storage means for storing executable instructions that, when executed by the processor, implement the method of claim 13.
15. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, implement the method of claim 13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610007083.6A CN105591821B (en) | 2016-01-06 | 2016-01-06 | Monitoring system and service system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610007083.6A CN105591821B (en) | 2016-01-06 | 2016-01-06 | Monitoring system and service system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105591821A CN105591821A (en) | 2016-05-18 |
| CN105591821B true CN105591821B (en) | 2020-06-30 |
Family
ID=55931080
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610007083.6A Active CN105591821B (en) | 2016-01-06 | 2016-01-06 | Monitoring system and service system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105591821B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106487596B (en) * | 2016-10-26 | 2019-12-13 | 宜人恒业科技发展（北京）有限公司 | Distributed service tracking implementation method |
| CN106777010B (en) * | 2016-12-07 | 2020-01-10 | 广东威创视讯科技股份有限公司 | Log providing method and device and log obtaining method, device and system |
| CN107276842B (en) * | 2017-05-10 | 2020-10-09 | 北京金山安全软件有限公司 | Interface test method and device and electronic equipment |
| CN107301197B (en) * | 2017-05-12 | 2020-12-01 | 上海瀚银信息技术有限公司 | Service data tracking processing system and method |
| CN107688899A (en) * | 2017-08-22 | 2018-02-13 | 北京潘达互娱科技有限公司 | Business process monitoring method and device |
| CN108933695B (en) * | 2018-06-25 | 2021-05-25 | 百度在线网络技术（北京）有限公司 | Method and apparatus for processing information |
| CN108984404A (en) * | 2018-07-11 | 2018-12-11 | 江苏满运软件科技有限公司 | A kind of exception information processing method and system, a kind of computer product |
| CN109298990B (en) * | 2018-10-17 | 2023-04-14 | 平安科技（深圳）有限公司 | Log storage method and device, computer equipment and storage medium |
| CN109582650B (en) * | 2018-11-09 | 2021-05-25 | 金色熊猫有限公司 | Module calling amount processing method and device, electronic equipment and storage medium |
| CN110224870B (en) * | 2019-06-19 | 2023-03-24 | 腾讯云计算（北京）有限责任公司 | Interface monitoring method and device, computing equipment and storage medium |
| CN112433757A (en) * | 2020-11-27 | 2021-03-02 | 中国建设银行股份有限公司 | Method and device for determining interface calling relationship |
| CN112887123A (en) * | 2021-01-06 | 2021-06-01 | 新浪网技术(中国)有限公司 | Service alarm method, system and device based on call chain |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101364289A (en) * | 2008-09-24 | 2009-02-11 | 中国移动通信集团福建有限公司 | Generalized flowsheet platform for corporation |
| CN101848477A (en) * | 2009-03-24 | 2010-09-29 | 亚信科技（中国）有限公司 | Method and system for diagnosing fault |
| CN104156300A (en) * | 2013-05-14 | 2014-11-19 | 利德科技发展有限公司 | Log management system and log management method |
| CN105183620A (en) * | 2015-08-07 | 2015-12-23 | 北京思特奇信息技术股份有限公司 | Method and system for tracking service running state |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106656536B (en) * | 2015-11-03 | 2020-02-18 | 阿里巴巴集团控股有限公司 | Method and equipment for processing service calling information |
-
2016
- 2016-01-06 CN CN201610007083.6A patent/CN105591821B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101364289A (en) * | 2008-09-24 | 2009-02-11 | 中国移动通信集团福建有限公司 | Generalized flowsheet platform for corporation |
| CN101848477A (en) * | 2009-03-24 | 2010-09-29 | 亚信科技（中国）有限公司 | Method and system for diagnosing fault |
| CN104156300A (en) * | 2013-05-14 | 2014-11-19 | 利德科技发展有限公司 | Log management system and log management method |
| CN105183620A (en) * | 2015-08-07 | 2015-12-23 | 北京思特奇信息技术股份有限公司 | Method and system for tracking service running state |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105591821A (en) | 2016-05-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105591821B (en) | Monitoring system and service system | |
| CN110661659B (en) | Alarm method, device and system and electronic equipment | |
| EP3373516B1 (en) | Method and device for processing service calling information | |
| US10498857B2 (en) | System interaction monitoring and component scaling | |
| RU2610288C2 (en) | Providing capabilities of configured technological process | |
| US9800455B1 (en) | Log monitoring system | |
| US11940974B2 (en) | Database lock | |
| US20150193723A1 (en) | Automatic floor-level retail operation decisions using video analytics | |
| CN108763482B (en) | Method and device for scheduling data analysis process and server cluster | |
| CN115600767A (en) | Material monitoring method and device, computer equipment and readable storage medium | |
| CN114490272A (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| US20100274601A1 (en) | Supply chain perameter optimization and anomaly identification in product offerings | |
| US10713328B2 (en) | Automated tagging application for maintaining up-to-date web analytics | |
| CN112087320B (en) | Abnormality positioning method and device, electronic equipment and readable storage medium | |
| US9594622B2 (en) | Contacting remote support (call home) and reporting a catastrophic event with supporting documentation | |
| CN105607983A (en) | Data exception monitoring method and apparatus | |
| CN116149824A (en) | Task re-running processing method, device, equipment and storage medium | |
| CN113421109A (en) | Service checking method, device, electronic equipment and storage medium | |
| US10977603B2 (en) | Content based message routing for supply chain information sharing | |
| CN112596974A (en) | Full link monitoring method, device, equipment and storage medium | |
| US9286112B2 (en) | Determining and dispatching processing agent for transaction processing | |
| CN111833161A (en) | Inventory reconciliation method, device and storage medium | |
| CN117692499A (en) | Distributed monitoring management method, system, equipment and medium for operation and maintenance service | |
| CN112529438B (en) | Workflow processing method and device for distributed scheduling system, computer equipment and storage medium | |
| CN113129027B (en) | Object management method, device, computing equipment and storage medium based on blockchain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |