CN110611715A - System and method for collecting cloud monitoring information by service link - Google Patents
System and method for collecting cloud monitoring information by service link Download PDFInfo
- Publication number
- CN110611715A CN110611715A CN201910897011.7A CN201910897011A CN110611715A CN 110611715 A CN110611715 A CN 110611715A CN 201910897011 A CN201910897011 A CN 201910897011A CN 110611715 A CN110611715 A CN 110611715A
- Authority
- CN
- China
- Prior art keywords
- monitoring
- service
- aggregation
- information
- resource
- 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.)
- Granted
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 135
- 238000000034 method Methods 0.000 title claims abstract description 30
- 230000002776 aggregation Effects 0.000 claims abstract description 65
- 238000004220 aggregation Methods 0.000 claims abstract description 65
- 239000000523 sample Substances 0.000 claims abstract description 20
- 230000004931 aggregating effect Effects 0.000 claims abstract description 6
- 238000006116 polymerization reaction Methods 0.000 claims description 5
- 230000007613 environmental effect Effects 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to a system and a method for collecting cloud monitoring information by a service link. The system comprises a rule base, an aggregation module and a storage module, wherein the rule base stores customized identification rules or aggregation rules and provides the rules for a probe or the aggregation module; the aggregation module retrieves corresponding monitoring information according to the service link and the aggregation rule, and aggregates the service link and the monitoring information; and the storage module stores the aggregation result for query. Firstly, injecting a probe, and inserting a customized identifier into span information sent by the probe; then, defining aggregation rules for different request types, wherein the aggregation rules define the aggregation relation between service links corresponding to the requests and monitoring indexes; then retrieving monitoring information according to the service link and the aggregation rule; and finally, aggregating the service link and the monitoring information. The invention realizes the aggregation of service links and cloud resource monitoring, and can simultaneously check the service links and multidimensional monitoring information; may be used in a service link tracking system.
Description
Technical Field
The invention relates to the technical field of cloud computing monitoring, in particular to a system and a method for collecting cloud monitoring information by a service link.
Background
Microservice, distributed and asynchronous messaging are several technical features of the development of cloud computing. In recent years, the resource types and service differentiation of cloud computing integration gradually increase, and one request often needs to be completed by cooperation of multiple services and multiple components. The message generated by the request passes through a plurality of nodes, the details of one request are monitored and tracked, and a lot of manpower and time are needed; and certain requirements are required for the skills of operation and maintenance personnel, and the OpenTracing specification and each service link tracking system solve the related requirements.
Through the service link tracking system, each component through which the request passes can be known, and the method is suitable for quick positioning; the user does not have to manually check which server, respectively which service each phase of the request has reached.
However, the information of the link generated by the current service link tracking system is still rough and cannot reflect the current condition of the resource in the cloud platform; the operation and maintenance personnel still need to log in the corresponding server to check the environment information of the resources, or log in the monitoring system to find the current monitoring condition related to the resources.
Disclosure of Invention
The invention aims to provide a system and a method for collecting cloud monitoring information by a service link, which can aggregate the service link and cloud resource monitoring and simultaneously check the service link requested by a cloud platform and the multidimensional monitoring information of the request operation at the time.
The technical scheme for solving the technical problems is as follows:
the system comprises a rule base, an aggregation module and a storage module, wherein the rule base stores customized identification rules or aggregation rules and provides the rules for the probe or the aggregation module; the aggregation module retrieves corresponding monitoring information according to the service link and the aggregation rule, and aggregates the service link and the monitoring information; and the storage module stores the aggregation result for query.
The method comprises the following steps:
s1, injecting a probe, and inserting a customized identification into span information sent by the probe;
s2, defining aggregation rules for different request types, wherein the aggregation rules define the aggregation relation between service links corresponding to the requests and monitoring indexes;
s3, retrieving monitoring information according to the service link and the aggregation rule;
and S4, aggregating the service link and the monitoring information.
The customized mark in the step S1 may be injected during probe initialization, and the customized mark is loaded; alternatively, the probe is injected before the scan information is serialized, and the customized tag is read from the memory and inserted into the scan information.
The specific process of injecting and loading the customized identification during probe initialization is as follows:
1) reading a customized identification rule from a rule base;
2) analyzing a customized identification rule, and replacing replaceable variables in the rule according to a predefined value and an environmental parameter to generate a customized identification;
3) caching the customized identification in a memory;
the customized identification rule is a customizable character string containing replaceable variables, wherein the replaceable variables comprise: service type, service name, component type, component name, hostname.
The aggregation rule specifically comprises:
1) a request type;
2) the service monitoring index set defines monitoring index lists required to be retrieved by different types of services;
3) the component monitoring index set defines monitoring index lists required to be retrieved by different types of components;
4) the server monitoring index set defines a monitoring index list which needs to be retrieved by the server;
5) the resource identification rule is used for identifying resource information in the span information, and the resource information comprises a resource id and a resource type;
6) and the resource monitoring index set defines monitoring index lists required to be retrieved by different types of resources.
The step S3 specifically includes the following steps:
1) reading a corresponding aggregation rule from the rule base according to the request type of the service link;
2) traversing span information of the service link;
3) and retrieving the monitoring information from the four dimensions of the service, the component, the server and the resource according to the aggregation rule and the customized identification of the span information.
The steps of retrieving monitoring information from the service dimension are:
1) acquiring a service type and a service name according to the customized identification;
2) according to the service type, searching a monitoring index list needing to be retrieved in the service monitoring index set;
3) and retrieving the monitoring information of the service through the monitoring system according to the service type, the service name, the span recording time and the monitoring index list.
The steps of retrieving monitoring information from the component dimension are:
1) acquiring a component type and a component name according to the customized identification;
2) according to the type of the component, a monitoring index list needing to be retrieved is found in the component monitoring index set;
3) and retrieving the monitoring information of the component through the monitoring system according to the component type, the component name, the span recording time and the monitoring index list.
The step of retrieving monitoring information from the server dimension comprises:
1) acquiring a service type and a hostname according to the customized identification;
2) and retrieving the monitoring information of the server through the monitoring system according to the service type, the hostname, the span recording time and the monitoring index list.
The step of retrieving monitoring information from the resource dimension comprises:
1) identifying resource information in the span detailed information according to the resource identification rule, wherein the resource information comprises a resource id and a resource type;
2) according to the resource type, searching a monitoring index list needing to be retrieved in the resource monitoring index set;
3) and retrieving the monitoring information of the resources through the monitoring system according to the resource id, the resource type, the span recording time and the monitoring index list.
The polymerization of step S4 specifically includes the following steps:
1) creating a data structure of a specific format as an aggregation result;
2) filling the detailed information of the service link in the aggregation result, wherein the detailed information comprises a request type, a traceId and a starting time;
3) traversing span of the service link, and creating a plurality of span blocks in an aggregation result;
4) filling the span block with the detailed information of the span, including: spanId, record time, service type, service name, component type, component name, and hostname;
5) filling the retrieved monitoring information in the span block according to the sequence of the service, the component, the server and the resource;
6) and sending the aggregation result to a storage module for storage.
The invention provides the system and the method for simultaneously checking the service link requested by the cloud platform and the multidimensional monitoring information requested to run at the time by aggregating the service link and the cloud resource monitoring, so that the conditions of the current environment and the operation resources can be more objectively observed, and the fault detection and the problem analysis in the operation and maintenance process are greatly facilitated.
Drawings
The invention is further described below with reference to the accompanying drawings:
FIG. 1 is a system block diagram of the method of the present invention;
FIG. 2 is a flow chart of the method of the present invention;
FIG. 3 is an exemplary diagram of aggregation rules for the method of the present invention;
FIG. 4 is an exemplary graph of the polymerization results of the method of the present invention.
Detailed Description
The service link aggregation cloud monitoring information system structure is shown in fig. 1, and the system is composed of a rule base, an aggregation module and a storage module; the basic functions of each module are:
the rule base is mainly responsible for storing and providing customized identification rules and aggregation rules;
the aggregation module is responsible for retrieving corresponding monitoring information according to the service link and the aggregation rule and aggregating the service link and the monitoring information;
and the storage module is responsible for storing and querying the aggregation result.
As shown in fig. 2, the implementation method of the cloud monitoring information system based on the service link aggregation of the present invention includes the following basic steps:
s1, injecting a probe, and inserting a customized mark into span information sent by the probe;
s2, defining aggregation rules for different request types, wherein the aggregation rules define the aggregation relation between a service link corresponding to a certain type of request and a plurality of monitoring indexes;
s3, retrieving monitoring information according to the service link and the aggregation rule;
and S4, aggregating the service link and the monitoring information.
In step S1, inserting the customized flag may be performed during probe initialization, and the customized flag is loaded; alternatively, the probe is injected before the span information is serialized, and the customized tag is read from the memory and inserted into the span information.
Injecting when the probe is initialized, and loading a customized identification; the following specific procedure may be taken:
1) reading a customized identification rule from a rule base of the aggregation system;
2) analyzing a customized identification rule, and replacing replaceable variables in the rule according to a predefined value and an environmental parameter to generate a customized identification;
3) and caching the customized identification in a memory.
A customized identification rule is a customizable string that contains alternative variables, including but not limited to: service type, service name, component type, component name, hostname.
As shown in fig. 3, the aggregation rule in step S2 specifically includes the following six aspects:
1) a request type;
2) the service monitoring index set defines monitoring index lists required to be retrieved by different types of services;
3) the component monitoring index set defines monitoring index lists required to be retrieved by different types of components;
4) the server monitoring index set defines a monitoring index list which needs to be retrieved by the server;
5) the resource identification rule is used for identifying resource information in the span information, and the resource information comprises a resource id and a resource type;
6) and the resource monitoring index set defines monitoring index lists required to be retrieved by different types of resources.
The aforementioned step S3 of retrieving the monitoring information may be specifically divided into:
1) reading a corresponding aggregation rule from the rule base according to the request type of the service link;
2) traversing span of the service link;
3) and retrieving the monitoring information from the four dimensions of the service, the component, the server and the resource according to the aggregation rule and the customized identification of the span.
More specifically, the method of retrieving monitoring information from the service dimension is:
1) acquiring a service type and a service name according to the customized identification;
2) according to the service type, searching a monitoring index list needing to be retrieved in the service monitoring index set;
3) and retrieving the monitoring information of the service through the monitoring system according to the service type, the service name, the span recording time and the monitoring index list.
The steps of retrieving monitoring information from the component dimension are:
1) acquiring a component type and a component name according to the customized identification;
2) according to the type of the component, a monitoring index list needing to be retrieved is found in the component monitoring index set;
3) and retrieving the monitoring information of the component through the monitoring system according to the component type, the component name, the span recording time and the monitoring index list.
The specific steps for retrieving the monitoring information from the server dimension are as follows:
1) acquiring a service type and a hostname according to the customized identification;
2) and retrieving the monitoring information of the server through the monitoring system according to the service type, the hostname, the span recording time and the monitoring index list.
The implementation method for retrieving the monitoring information from the resource dimension comprises the following steps:
1) identifying resource information in the span detailed information according to the resource identification rule, wherein the resource information comprises a resource id and a resource type;
2) according to the resource type, searching a monitoring index list needing to be retrieved in the resource monitoring index set;
3) and retrieving the monitoring information of the resources through the monitoring system according to the resource id, the resource type, the span recording time and the monitoring index list.
As shown in fig. 4, the result after polymerization according to step S4 is shown; the polymerization comprises the following specific steps:
1) creating a data structure of a specific format as an aggregation result;
2) filling the detailed information of the service link in the aggregation result, wherein the detailed information comprises a request type, a traceId, a starting time and the like;
3) traversing span of the service link, and creating a plurality of span blocks in an aggregation result;
4) filling the span block with the detailed information of the span, including the span Id, the recording time, the service type, the service name, the component type, the component name, the hostname and the like;
5) filling the retrieved monitoring information in the span block according to the sequence of the service, the component, the server and the resource;
6) and sending the aggregation result to a storage module for storage.
Claims (11)
1. A system for collecting cloud monitoring information by service links is characterized in that: the system comprises a rule base, an aggregation module and a storage module, wherein the rule base stores customized identification rules or aggregation rules and provides the rules for the probe or the aggregation module; the aggregation module retrieves corresponding monitoring information according to the service link and the aggregation rule, and aggregates the service link and the monitoring information; and the storage module stores the aggregation result for query.
2. A method for collecting cloud monitoring information by a service link is characterized in that: the method comprises the following steps:
s1, injecting a probe, and inserting a customized identification into span information sent by the probe;
s2, defining aggregation rules for different request types, wherein the aggregation rules define the aggregation relation between service links corresponding to the requests and monitoring indexes;
s3, retrieving monitoring information according to the service link and the aggregation rule;
and S4, aggregating the service link and the monitoring information.
3. The method of claim 2, wherein: the customized mark in the step S1 may be injected during probe initialization, and the customized mark is loaded; alternatively, the probe is injected before the scan information is serialized, and the customized tag is read from the memory and inserted into the scan information.
4. The method of claim 3, wherein: the specific process of injecting and loading the customized identification during probe initialization is as follows:
1) reading a customized identification rule from a rule base;
2) analyzing a customized identification rule, and replacing replaceable variables in the rule according to a predefined value and an environmental parameter to generate a customized identification;
3) caching the customized identification in a memory;
the customized identification rule is a customizable character string containing replaceable variables, wherein the replaceable variables comprise: service type, service name, component type, component name, hostname.
5. The method of claim 2, wherein: the aggregation rule specifically comprises:
1) a request type;
2) the service monitoring index set defines monitoring index lists required to be retrieved by different types of services;
3) the component monitoring index set defines monitoring index lists required to be retrieved by different types of components;
4) the server monitoring index set defines a monitoring index list which needs to be retrieved by the server;
5) the resource identification rule is used for identifying resource information in the span information, and the resource information comprises a resource id and a resource type;
6) and the resource monitoring index set defines monitoring index lists required to be retrieved by different types of resources.
6. The method according to any one of claims 2 to 5, wherein: the step S3 specifically includes the following steps:
1) reading a corresponding aggregation rule from the rule base according to the request type of the service link;
2) traversing span information of the service link;
3) and retrieving the monitoring information from the four dimensions of the service, the component, the server and the resource according to the aggregation rule and the customized identification of the span information.
7. The method of claim 6, wherein: the steps of retrieving monitoring information from the service dimension are:
1) acquiring a service type and a service name according to the customized identification;
2) according to the service type, searching a monitoring index list needing to be retrieved in the service monitoring index set;
3) and retrieving the monitoring information of the service through the monitoring system according to the service type, the service name, the span recording time and the monitoring index list.
8. The method of claim 6, wherein: the steps of retrieving monitoring information from the component dimension are:
1) acquiring a component type and a component name according to the customized identification;
2) according to the type of the component, a monitoring index list needing to be retrieved is found in the component monitoring index set;
3) and retrieving the monitoring information of the component through the monitoring system according to the component type, the component name, the span recording time and the monitoring index list.
9. The method of claim 6, wherein: the step of retrieving monitoring information from the server dimension comprises:
1) acquiring a service type and a hostname according to the customized identification;
2) and retrieving the monitoring information of the server through the monitoring system according to the service type, the hostname, the span recording time and the monitoring index list.
10. The method of claim 6, wherein: the step of retrieving monitoring information from the resource dimension comprises:
1) identifying resource information in the span detailed information according to the resource identification rule, wherein the resource information comprises a resource id and a resource type;
2) according to the resource type, searching a monitoring index list needing to be retrieved in the resource monitoring index set;
3) and retrieving the monitoring information of the resources through the monitoring system according to the resource id, the resource type, the span recording time and the monitoring index list.
11. The method of claim 2, wherein: the polymerization of step S4 specifically includes the following steps:
1) creating a data structure of a specific format as an aggregation result;
2) filling the detailed information of the service link in the aggregation result, wherein the detailed information comprises a request type, a traceId and a starting time;
3) traversing span of the service link, and creating a plurality of span blocks in an aggregation result;
4) filling the span block with the detailed information of the span, including: spanId, record time, service type, service name, component type, component name, and hostname;
5) filling the retrieved monitoring information in the span block according to the sequence of the service, the component, the server and the resource;
6) and sending the aggregation result to a storage module for storage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910897011.7A CN110611715B (en) | 2019-09-23 | 2019-09-23 | System and method for collecting cloud monitoring information through service links |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910897011.7A CN110611715B (en) | 2019-09-23 | 2019-09-23 | System and method for collecting cloud monitoring information through service links |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110611715A true CN110611715A (en) | 2019-12-24 |
| CN110611715B CN110611715B (en) | 2023-11-28 |
Family
ID=68891979
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910897011.7A Active CN110611715B (en) | 2019-09-23 | 2019-09-23 | System and method for collecting cloud monitoring information through service links |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110611715B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111541590A (en) * | 2020-07-08 | 2020-08-14 | 广州市玄武无线科技股份有限公司 | Link monitoring method, alarm method, system, terminal and storage medium |
| CN112035317A (en) * | 2020-08-28 | 2020-12-04 | 北京浪潮数据技术有限公司 | Micro-service link monitoring method, device, equipment and medium |
| CN116340296A (en) * | 2023-05-30 | 2023-06-27 | 南方电网数字电网研究院有限公司 | Multi-source data fusion and unified information model construction method based on data probes |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2350673A1 (en) * | 2001-06-14 | 2002-12-15 | Tropic Networks Inc. | Extension of link aggregation protols over the network |
| CN101505270A (en) * | 2009-03-24 | 2009-08-12 | 神州数码网络(北京)有限公司 | Method for aggregated link rapid convergence of distributed switch |
| CN101521832A (en) * | 2009-03-16 | 2009-09-02 | 广州杰赛科技股份有限公司 | Monitoring system and monitoring method for signal quality of television networks |
| CN103023698A (en) * | 2012-11-30 | 2013-04-03 | 中兴通讯股份有限公司 | LACP (link aggregation control protocol) link aggregation optimization method and device based on Ethernet link-level OAM (operation, administration and maintenance) |
| US20130100847A1 (en) * | 2010-06-29 | 2013-04-25 | Telefonaktiebolaget Lm Ericsson(Publ) | Method And An Apparatus For Evaluating Network Performance |
| WO2013098830A1 (en) * | 2011-12-30 | 2013-07-04 | Yogesh Chunical Rathod | A system and method for dynamic, portable, customize, contextual, unified and integrated network(s). |
| CN105046387A (en) * | 2015-01-07 | 2015-11-11 | 泰华智慧产业集团股份有限公司 | Comprehensive analyzing subsystem of digital city monitoring center and working method thereof |
| CN106131213A (en) * | 2016-08-17 | 2016-11-16 | 深圳市金证科技股份有限公司 | A kind of service management and system |
| CN106302024A (en) * | 2016-08-23 | 2017-01-04 | 成都科来软件有限公司 | The method and device that a kind of chain index based on various dimensions monitors in real time |
| CN106452944A (en) * | 2016-08-31 | 2017-02-22 | 成都科来软件有限公司 | Method and device for obtaining business performance analysis data based on multiple dimensions |
| EP3217607A1 (en) * | 2016-03-11 | 2017-09-13 | Aruba Networks, Inc. | Configuration of communication interfaces for link aggregation |
| CN107515864A (en) * | 2016-06-15 | 2017-12-26 | 阿里巴巴集团控股有限公司 | The method and apparatus of control work flows |
| CN108075913A (en) * | 2016-11-15 | 2018-05-25 | 千寻位置网络有限公司 | A kind of monitoring method and its system of broadcasting system service quality |
| CN109560989A (en) * | 2018-12-06 | 2019-04-02 | 深圳市递四方信息科技有限公司 | A kind of link monitoring system |
| CN109617758A (en) * | 2018-11-30 | 2019-04-12 | 网宿科技股份有限公司 | Meshed network quality calculation method and device, server, computer storage medium |
| CN109639809A (en) * | 2018-12-20 | 2019-04-16 | 上海拍拍贷金融信息服务有限公司 | A kind of method and device of service data request link monitoring |
| CN109729556A (en) * | 2019-02-12 | 2019-05-07 | Oppo广东移动通信有限公司 | Link connection method and relevant apparatus |
| CN109873717A (en) * | 2019-01-18 | 2019-06-11 | 深圳壹账通智能科技有限公司 | Monitoring method, device, computer equipment and storage medium |
-
2019
- 2019-09-23 CN CN201910897011.7A patent/CN110611715B/en active Active
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2350673A1 (en) * | 2001-06-14 | 2002-12-15 | Tropic Networks Inc. | Extension of link aggregation protols over the network |
| CN101521832A (en) * | 2009-03-16 | 2009-09-02 | 广州杰赛科技股份有限公司 | Monitoring system and monitoring method for signal quality of television networks |
| CN101505270A (en) * | 2009-03-24 | 2009-08-12 | 神州数码网络(北京)有限公司 | Method for aggregated link rapid convergence of distributed switch |
| US20130100847A1 (en) * | 2010-06-29 | 2013-04-25 | Telefonaktiebolaget Lm Ericsson(Publ) | Method And An Apparatus For Evaluating Network Performance |
| WO2013098830A1 (en) * | 2011-12-30 | 2013-07-04 | Yogesh Chunical Rathod | A system and method for dynamic, portable, customize, contextual, unified and integrated network(s). |
| CN103023698A (en) * | 2012-11-30 | 2013-04-03 | 中兴通讯股份有限公司 | LACP (link aggregation control protocol) link aggregation optimization method and device based on Ethernet link-level OAM (operation, administration and maintenance) |
| CN105046387A (en) * | 2015-01-07 | 2015-11-11 | 泰华智慧产业集团股份有限公司 | Comprehensive analyzing subsystem of digital city monitoring center and working method thereof |
| EP3217607A1 (en) * | 2016-03-11 | 2017-09-13 | Aruba Networks, Inc. | Configuration of communication interfaces for link aggregation |
| CN107515864A (en) * | 2016-06-15 | 2017-12-26 | 阿里巴巴集团控股有限公司 | The method and apparatus of control work flows |
| CN106131213A (en) * | 2016-08-17 | 2016-11-16 | 深圳市金证科技股份有限公司 | A kind of service management and system |
| CN106302024A (en) * | 2016-08-23 | 2017-01-04 | 成都科来软件有限公司 | The method and device that a kind of chain index based on various dimensions monitors in real time |
| CN106452944A (en) * | 2016-08-31 | 2017-02-22 | 成都科来软件有限公司 | Method and device for obtaining business performance analysis data based on multiple dimensions |
| CN108075913A (en) * | 2016-11-15 | 2018-05-25 | 千寻位置网络有限公司 | A kind of monitoring method and its system of broadcasting system service quality |
| CN109617758A (en) * | 2018-11-30 | 2019-04-12 | 网宿科技股份有限公司 | Meshed network quality calculation method and device, server, computer storage medium |
| CN109560989A (en) * | 2018-12-06 | 2019-04-02 | 深圳市递四方信息科技有限公司 | A kind of link monitoring system |
| CN109639809A (en) * | 2018-12-20 | 2019-04-16 | 上海拍拍贷金融信息服务有限公司 | A kind of method and device of service data request link monitoring |
| CN109873717A (en) * | 2019-01-18 | 2019-06-11 | 深圳壹账通智能科技有限公司 | Monitoring method, device, computer equipment and storage medium |
| CN109729556A (en) * | 2019-02-12 | 2019-05-07 | Oppo广东移动通信有限公司 | Link connection method and relevant apparatus |
Non-Patent Citations (3)
| Title |
|---|
| JUN HUANG;SHIHAO LI;QIANG DUAN;: "Constructing Multicast Routing Tree for Inter-cloud Data Transmission:An Approximation Algorithmic Perspective", IEEE/CAA JOURNAL OF AUTOMATICA SINICA, no. 02 * |
| JUNJIE HU;GUANGYA YANG;KOEN KOK;YUSHENG XUE;HENRIK W.BINDNER;: "Transactive control:a framework for operating power systems characterized by high penetration of distributed energy resources", JOURNAL OF MODERN POWER SYSTEMS AND CLEAN ENERGY, no. 03 * |
| 王健;刘绪忠;范树凯;: "基于CLIQUE算法的互联网感知监控质差点定位研究", 山东通信技术, no. 02 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111541590A (en) * | 2020-07-08 | 2020-08-14 | 广州市玄武无线科技股份有限公司 | Link monitoring method, alarm method, system, terminal and storage medium |
| CN112035317A (en) * | 2020-08-28 | 2020-12-04 | 北京浪潮数据技术有限公司 | Micro-service link monitoring method, device, equipment and medium |
| CN112035317B (en) * | 2020-08-28 | 2022-06-17 | 北京浪潮数据技术有限公司 | Micro-service link monitoring method, device, equipment and medium |
| CN116340296A (en) * | 2023-05-30 | 2023-06-27 | 南方电网数字电网研究院有限公司 | Multi-source data fusion and unified information model construction method based on data probes |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110611715B (en) | 2023-11-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111258989B (en) | Database migration evaluation method and device, storage medium and computer equipment | |
| CN110611715A (en) | System and method for collecting cloud monitoring information by service link | |
| EP3432520B1 (en) | Efficient storage and querying of time series metrics | |
| CN104298726B (en) | A kind of BMS data-storage systems and its method based on database | |
| CN110088744B (en) | Database maintenance method and system | |
| CN107870849A (en) | The treating method and apparatus of test log | |
| US9922116B2 (en) | Managing big data for services | |
| CN114780370A (en) | Data correction method and device based on log, electronic equipment and storage medium | |
| CN114328566A (en) | Relationship graph updating method, device, medium, equipment and generating method | |
| CN113010208B (en) | Version information generation method, device, equipment and storage medium | |
| CN116719750B (en) | Software testing method and device, server equipment and storage medium | |
| CN107357557A (en) | A kind of information updating method and device | |
| CN103309929B (en) | Storage and the method and system of retrieval data | |
| CN115185778A (en) | Database monitoring method and device | |
| CN113380414A (en) | Data acquisition method and system based on big data | |
| CN117540369B (en) | Numerical behavior safety base line generation method and device for safety analysis | |
| CN111352824A (en) | Test method and device and computer equipment | |
| CN114124509B (en) | Spark-based network abnormal flow detection method and system | |
| CN118173214B (en) | Intelligent communication interaction method and system for medical information | |
| CN113032254B (en) | Test coverage condition evaluation method and device | |
| CN117541045A (en) | Resource transfer risk detection method, electronic equipment and storage medium | |
| CN117909401A (en) | Monitoring equipment management platform for smart city and management method thereof | |
| CN115934381A (en) | Dynamic call chain generation and analysis device based on graph database | |
| CN116701112A (en) | Micro-service link tracking method | |
| CN116627692A (en) | Emergency event handling method, apparatus, device, medium and program product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |