CN112543127A - Monitoring method and device of micro-service architecture - Google Patents
Monitoring method and device of micro-service architecture Download PDFInfo
- Publication number
- CN112543127A CN112543127A CN201910899307.2A CN201910899307A CN112543127A CN 112543127 A CN112543127 A CN 112543127A CN 201910899307 A CN201910899307 A CN 201910899307A CN 112543127 A CN112543127 A CN 112543127A
- Authority
- CN
- China
- Prior art keywords
- basic data
- event
- preset
- monitoring
- message queue
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- 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
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 method and a monitoring device of a micro-service architecture, and relates to the technical field of micro-service monitoring. The monitoring method of the micro-service architecture comprises the following steps: acquiring basic data, wherein the basic data comprises log data and system index data of a micro-service system; processing the basic data to obtain a basic data cluster; acquiring an event message queue according to the basic data cluster and a preset event format; and acquiring alarm information according to the event message queue. According to the technical scheme, the monitoring indexes of two dimensions of the log and the system index can be processed simultaneously, the method is closer to the actual operation and maintenance requirements of the micro service, has an alarm convergence mechanism, and has service self-recovery capability.
Description
Technical Field
The present invention relates to the field of micro-service monitoring technologies, and in particular, to a monitoring method and apparatus for a micro-service architecture.
Background
With the rapid development of internet technology in recent years, the website scale and the corresponding application architecture become more and more large and complex, the traditional vertical application architecture is not careful, and the distributed service architecture gradually starts to be widely applied.
In the prior art, a management console of a dubbo framework in the prior art can visually see each service state and has very strong automatic telescopic capability, but because the dubbo framework is more focused on development rather than operation and maintenance, each service index cannot be effectively monitored, and meanwhile, the functions of time early warning and self recovery extended from the monitored index cannot be completed; in the prior art, zabbix is a very mature monitoring scheme, can conveniently process system monitoring indexes, but cannot complete log collection and early warning, and meanwhile, alarm convergence and service self-recovery still need to be developed and realized by self.
Disclosure of Invention
The embodiment of the invention provides a monitoring method and a monitoring device of a micro service architecture, which are used for solving the problem that the monitoring function of the existing micro service architecture is incomplete.
In order to solve the foregoing technical problem, an embodiment of the present invention provides a monitoring method for a micro service architecture, including:
acquiring basic data, wherein the basic data comprises log data and system index data of a micro-service system;
processing the basic data to obtain a basic data cluster;
acquiring an event message queue according to the basic data cluster and a preset event format;
and acquiring alarm information according to the event message queue.
Further, the processing the basic data to obtain a basic data cluster includes:
storing the basic data according to a preset data format to obtain a basic data message queue, wherein the data format comprises a plurality of fields corresponding to the basic data;
and according to the index fields in the data format, respectively corresponding the basic data message queues to indexes corresponding to the basic data clusters.
Further, the obtaining an event message queue according to the basic data cluster and a preset event format includes:
detecting whether the monitoring time of a preset monitoring interval period is reached;
when the monitoring time of a preset monitoring interval period is reached, matching basic data in the basic data cluster according to a preset event model;
and if the matching is successful, obtaining the event message queue according to a preset event format, wherein the event format comprises a plurality of fields corresponding to the basic data cluster.
Further, the obtaining of the alarm information according to the event message queue includes:
detecting whether the monitoring time of a preset monitoring interval period is reached;
when the monitoring time of a preset monitoring interval period is reached, matching the event message queue according to a preset alarm model;
and if the matching is successful, acquiring alarm information according to the matching result, and sending the alarm information to the user terminal.
Further, after the acquiring the event message queue, the method further includes:
and sending a self-recovery instruction according to the event message queue.
Further, the sending a self-recovery instruction according to the event message queue includes:
detecting whether the monitoring time of a preset monitoring interval period is reached;
when the monitoring time of a preset monitoring interval period is reached, matching the event message queue according to a preset self-recovery model;
and if the matching is successful, sending a self-recovery instruction to a service port corresponding to the event in the event message queue which is successfully matched.
Further, after the acquiring the event message queue, the method further includes:
and according to the index fields in the event format, respectively corresponding the event message queues to indexes corresponding to the event data clusters.
An embodiment of the present invention further provides a monitoring apparatus for a micro service architecture, including:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring basic data, and the basic data comprises log data and system index data of the micro-service system;
the first processing module is used for processing the basic data to obtain a basic data cluster;
the second processing module is used for acquiring an event message queue according to the basic data cluster and a preset event format;
and the second acquisition module is used for acquiring the alarm information according to the event message queue.
Further, the first processing module includes:
the storage unit is used for storing the basic data according to a preset data format to obtain a basic data message queue, wherein the data format comprises a plurality of fields corresponding to the basic data;
and the first processing unit is used for respectively corresponding the basic data message queues to indexes corresponding to the basic data clusters according to the index fields in the data format.
Further, the second processing module includes:
the first detection unit is used for detecting whether the monitoring time of a preset monitoring interval period is reached;
the first matching unit is used for matching basic data in the basic data cluster according to a preset event model when the monitoring time of a preset monitoring interval period is reached;
and the second processing unit is used for obtaining the event message queue according to a preset event format if the matching is successful, wherein the event format comprises a plurality of fields corresponding to the basic data cluster.
Further, the second obtaining module includes:
the second detection unit is used for detecting whether the monitoring time of a preset monitoring interval period is reached;
the second matching unit is used for matching the event message queue according to a preset alarm model when the monitoring time of a preset monitoring interval period is reached;
and the acquisition unit is used for acquiring the alarm information according to the matching result and sending the alarm information to the user terminal if the matching is successful.
Further, the apparatus further comprises:
and the sending module is used for sending a self-recovery instruction according to the event message queue.
Further, the sending module includes:
the third detection unit is used for detecting whether the monitoring time of the preset monitoring interval period is reached;
the third matching unit is used for matching the event message queue according to a preset self-recovery model when the monitoring time of a preset monitoring interval period is reached;
and the sending unit is used for sending a self-recovery instruction to the service port corresponding to the event in the event message queue which is successfully matched if the matching is successful.
Further, the apparatus further comprises:
and the third acquisition module is used for respectively corresponding the event message queues to indexes corresponding to the event data clusters according to the index fields in the event formats. The invention has the beneficial effects that:
according to the scheme, the monitoring indexes of two dimensions of the log and the system index can be processed simultaneously, the method is closer to the actual operation and maintenance requirements of the micro service, has an alarm convergence mechanism, and has service self-recovery capability.
Drawings
FIG. 1 is a flow chart illustrating a monitoring method for a microservice architecture according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a microservice architecture according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a monitoring apparatus of a microservice architecture according to an embodiment of the present invention.
Description of reference numerals:
21-a proxy server; 22-a first switching server; 23-an event server; 24-an alert server; 25-a second exchange server; 26-secure server.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in detail with reference to the accompanying drawings and specific embodiments.
The invention provides a monitoring method and a monitoring device of a micro service architecture, aiming at the problem that the monitoring function of the existing micro service architecture is incomplete.
As shown in fig. 1, an embodiment of the present invention provides a monitoring method for a micro service architecture, including:
and 11, acquiring basic data, wherein the basic data comprises log data and system index data of the micro-service system.
And step 12, processing the basic data to obtain a basic data cluster.
And step 13, acquiring an event message queue according to the basic data cluster and a preset event format.
And step 14, acquiring alarm information according to the event message queue.
The embodiment of the invention can simultaneously process the monitoring indexes of two dimensions of the log and the system index, is closer to the actual operation and maintenance requirements of the micro service, has an alarm convergence mechanism and has the service self-recovery capability.
As shown in fig. 2, an embodiment of the present invention provides a micro service architecture, including: a proxy server 21, a first switching server 22, an event server 23, an alarm server 24, a second switching server 25 and a security server 26.
Specifically, the proxy server 21 is used for collecting basic data and packaging the basic data for calling, so that preliminary screening of the basic data is realized, and the relevant basic data is conveniently used in subsequent event analysis.
It should be noted that the basic data includes log data and system index data, where the log data includes ERROR logs and access logs, the system index data includes service survival status, jmx index and jvm index, jmx index includes heap memory usage, non-heap memory usage, thread usage and waiting queue usage, and jvm index includes gc time, gc times, age generation usage, and permanent generation/meta space usage ratio. Specifically, the service survival status is used for service survival detection, the jmx and jvm indexes are used for measuring whether the performance of the server is abnormal or not, and the log data is used for measuring the business logic condition. The service survival state is judged by requesting the server to fix the return value of the survival detection page, the service survival storage value is judged to be 1 if the server returns to TRUE within 5 seconds, and the service is judged to be absent if the server does not return to TRUE within 5 seconds and is stored to be 0 if the server returns to TRUE within 5 seconds. JMX indexes follow JMX standard, and the corresponding indexes are obtained by carrying out secondary packaging on the cmdline-jmxclient tool. jvm the index uses the jstat command to get the corresponding index. And reading the ERROR level log in the service standard output log by the ERROR log. The access log directly reads the access log of the service.
Preferably, the proxy server 21 may be written in Python language, and the runtime exists as a separate process in the Linux system.
In particular, considering that the amount of the basic data is very large, congestion may be caused if the basic data is directly written into the basic data cluster, so that a higher load of the proxy server or even a false death of the proxy server may have a great influence on the microservice, and therefore, a basic data message queue needs to be introduced for decoupling. Therefore, the step 12 of processing the basic data to obtain a basic data cluster includes:
storing the basic data according to a preset data format to obtain a basic data message queue, wherein the data format comprises a plurality of fields corresponding to the basic data;
and according to the index fields in the data format, respectively corresponding the basic data message queues to indexes corresponding to the basic data clusters.
Specifically, the index field can be used for storing a service system, a gateway and the like of the basic data, and the setting of the index field realizes the fragmentation of the basic data, so that the query is more convenient and faster without traversing all the basic data.
It should be noted that the acquired basic data are assembled according to a preset fixed data format, so as to facilitate subsequent standardization processing. Specifically, the data formats are divided into two types, which are respectively used for recombining log data and system index data, wherein fields of the data format used for assembling the log data include: recording time, data type, service IP, service port, log type, request url, status code, log content, execution time and index; fields of a data format for assembling system metric data include: recording time, data type, service IP, service port, service name, monitoring item value and index. The proxy server writes the basic data into the basic data message queue by calling the kafka producer method in the python kafka module.
It should be further noted that, after the processing by the proxy server 21, the basic data is written into the basic data message queue, and the first switching server 22 is required to correspond the basic data message queue to the basic data cluster according to the index field in the next step. Preferably, the first switching server 22 may be written in Python language, and the runtime exists in an independent process in the Linux system, and the implementation manner is to call a kafka provider method in the Python kafka module, and write the kafka provider method into corresponding indexes of the basic data cluster according to different indexes in the basic data, where the basic data cluster uses an elastic search component.
Specifically, the step 13 includes:
detecting whether the monitoring time of a preset monitoring interval period is reached;
when the monitoring time of a preset monitoring interval period is reached, matching basic data in the basic data cluster according to a preset event model;
and if the matching is successful, obtaining the event message queue according to a preset event format, wherein the event format comprises a plurality of fields corresponding to the basic data cluster.
The event server 23 extracts data from the basic data cluster at regular time, generates an event, and stores the event in the event message queue. Preferably, the event server 23 may be written in Python language, and exists in the Linux system as an independent process during running, and mainly uses a cell structure, and after a cell starts a task, matches basic data, which is indexed correspondingly in a basic data cluster, according to a preset event model, specifically, the event model is a Query expression (Query DSL) of an encapsulated elastic search, and when the Query DSL is hit, it means that the event model is successfully matched, at this time, an event is generated, and if the Query DSL is not hit, the flow is directly ended. After matching is successful, according to a preset fixed event format, assembling the generated events into event data and writing the event data into an event message queue, specifically, fields of the event format include: record time, data type, service IP, service port, service name, event information, index.
After the event message queue is obtained, the embodiment of the invention mainly completes three functions by using event data, specifically, the warning server 24 reads the event to complete early warning matching, the second exchange server 25 reads the event to complete writing into the event data cluster so as to be used by other systems to look up the event, and the safety server 26 reads the event to complete service self-recovery matching.
The following is a description of three functions:
alarm server
The acquiring alarm information according to the event message queue includes:
detecting whether the monitoring time of a preset monitoring interval period is reached;
when the monitoring time of a preset monitoring interval period is reached, matching the event message queue according to a preset alarm model;
and if the matching is successful, acquiring alarm information according to the matching result, and sending the alarm information to the user terminal.
It should be noted that the alarm server 24 obtains event data from the event message queue, matches the alarm model at regular time, and preferably performs matching every one minute, specifically, the early warning model is a Query expression (Query DSL) of an encapsulated elastic search, and when the Query DSL hits, it means that the alarm model matches successfully, and at this time, generates alarm information and sends the alarm information to the user terminal, and preferably, sends the alarm information in a short message manner, and if the alarm information does not hit, the flow is directly ended. The embodiment of the invention finally outputs short alarm information by matching and integrating a plurality of pieces of event data, thereby effectively realizing an alarm convergence mechanism. Preferably, the alarm server may be written in Python language, and the runtime exists in an independent process in the Linux system.
Second, the second exchange server of the security server
After the step 13, the method further comprises:
and sending a self-recovery instruction according to the event message queue.
Specifically, the sending a self-recovery instruction according to the event message queue includes:
detecting whether the monitoring time of a preset monitoring interval period is reached;
when the monitoring time of a preset monitoring interval period is reached, matching the event message queue according to a preset self-recovery model;
and if the matching is successful, sending a self-recovery instruction to a service port corresponding to the event in the event message queue which is successfully matched.
It should be noted that, the security server 26 obtains event data from the event message queue, and matches the self-recovery model at regular time, specifically, the self-recovery model is a Query expression (Query DSL) of an encapsulated elastic search, when the Query DSL hits, it means that the self-recovery model matches successfully, at this time, a self-recovery action is triggered, generally, the self-recovery action is to invoke a corresponding service restart, and if the Query DSL misses, the flow is directly ended. Preferably, the secure server 26 may be written in Python language, and the runtime exists as a separate process in the Linux system.
Third, second exchange server
After the step 13, the method further comprises:
and according to the index fields in the event format, respectively corresponding the event message queues to indexes corresponding to the event data clusters.
It should be noted that the second switching server 25 corresponds the event message queue to the event data cluster according to the index field. Preferably, the second switching server 25 may be written in Python language, and the runtime exists in an independent process in the Linux system, and the implementation manner is to call a kafka provider method in the Python kafka module, and write the kafka provider method into corresponding indexes of the event data cluster according to different indexes in the event data, where the event data cluster uses an elastic search component.
As shown in fig. 3, an embodiment of the present invention further provides a monitoring apparatus for a microservice architecture, including:
the first obtaining module 31 is configured to obtain basic data, where the basic data includes log data and system index data of a microservice system;
a first processing module 32, configured to process the basic data to obtain a basic data cluster;
the second processing module 33 is configured to obtain an event message queue according to the basic data cluster and a preset event format;
and a second obtaining module 34, configured to obtain alarm information according to the event message queue.
Specifically, the first processing module 32 includes:
the storage unit is used for storing the basic data according to a preset data format to obtain a basic data message queue, wherein the data format comprises a plurality of fields corresponding to the basic data;
and the first processing unit is used for respectively corresponding the basic data message queues to indexes corresponding to the basic data clusters according to the index fields in the data format.
Specifically, the second processing module 33 includes:
the first detection unit is used for detecting whether the monitoring time of a preset monitoring interval period is reached;
the first matching unit is used for matching basic data in the basic data cluster according to a preset event model when the monitoring time of a preset monitoring interval period is reached;
and the second processing unit is used for obtaining the event message queue according to a preset event format if the matching is successful, wherein the event format comprises a plurality of fields corresponding to the basic data cluster.
Specifically, the second obtaining module 34 includes:
the second detection unit is used for detecting whether the monitoring time of a preset monitoring interval period is reached;
the second matching unit is used for matching the event message queue according to a preset alarm model when the monitoring time of a preset monitoring interval period is reached;
and the acquisition unit is used for acquiring the alarm information according to the matching result and sending the alarm information to the user terminal if the matching is successful.
Specifically, the apparatus further comprises:
and the sending module is used for sending a self-recovery instruction according to the event message queue.
Specifically, the sending module includes:
the third detection unit is used for detecting whether the monitoring time of the preset monitoring interval period is reached;
the third matching unit is used for matching the event message queue according to a preset self-recovery model when the monitoring time of a preset monitoring interval period is reached;
and the sending unit is used for sending a self-recovery instruction to the service port corresponding to the event in the event message queue which is successfully matched if the matching is successful.
Specifically, the apparatus further comprises:
and the third acquisition module is used for respectively corresponding the event message queues to indexes corresponding to the event data clusters according to the index fields in the event formats.
The embodiment of the invention can simultaneously process the monitoring indexes of two dimensions of the log and the system index, is closer to the actual operation and maintenance requirements of the micro service, has an alarm convergence mechanism and has the service self-recovery capability.
While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims.
Claims (14)
1. A monitoring method of a micro service architecture is characterized by comprising the following steps:
acquiring basic data, wherein the basic data comprises log data and system index data of a micro-service system;
processing the basic data to obtain a basic data cluster;
acquiring an event message queue according to the basic data cluster and a preset event format;
and acquiring alarm information according to the event message queue.
2. The monitoring method of micro service architecture according to claim 1, wherein the processing the basic data to obtain a basic data cluster comprises:
storing the basic data according to a preset data format to obtain a basic data message queue, wherein the data format comprises a plurality of fields corresponding to the basic data;
and according to the index fields in the data format, respectively corresponding the basic data message queues to indexes corresponding to the basic data clusters.
3. The monitoring method of the micro-service architecture according to claim 1, wherein the obtaining an event message queue according to the basic data cluster and a preset event format includes:
detecting whether the monitoring time of a preset monitoring interval period is reached;
when the monitoring time of a preset monitoring interval period is reached, matching basic data in the basic data cluster according to a preset event model;
and if the matching is successful, obtaining the event message queue according to a preset event format, wherein the event format comprises a plurality of fields corresponding to the basic data cluster.
4. The monitoring method of micro service architecture according to claim 1, wherein the obtaining alarm information according to the event message queue comprises:
detecting whether the monitoring time of a preset monitoring interval period is reached;
when the monitoring time of a preset monitoring interval period is reached, matching the event message queue according to a preset alarm model;
and if the matching is successful, acquiring alarm information according to the matching result, and sending the alarm information to the user terminal.
5. The monitoring method of micro service architecture according to claim 1, wherein after the event message queue is obtained, the method further comprises:
and sending a self-recovery instruction according to the event message queue.
6. The monitoring method of micro service architecture according to claim 5, wherein the sending self-recovery instructions according to the event message queue comprises:
detecting whether the monitoring time of a preset monitoring interval period is reached;
when the monitoring time of a preset monitoring interval period is reached, matching the event message queue according to a preset self-recovery model;
and if the matching is successful, sending a self-recovery instruction to a service port corresponding to the event in the event message queue which is successfully matched.
7. The monitoring method of micro service architecture according to claim 1, wherein after the event message queue is obtained, the method further comprises:
and according to the index fields in the event format, respectively corresponding the event message queues to indexes corresponding to the event data clusters.
8. A monitoring apparatus of a microservice architecture, comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring basic data, and the basic data comprises log data and system index data of the micro-service system;
the first processing module is used for processing the basic data to obtain a basic data cluster;
the second processing module is used for acquiring an event message queue according to the basic data cluster and a preset event format;
and the second acquisition module is used for acquiring the alarm information according to the event message queue.
9. The monitoring apparatus of micro service architecture according to claim 8, wherein the first processing module comprises:
the storage unit is used for storing the basic data according to a preset data format to obtain a basic data message queue, wherein the data format comprises a plurality of fields corresponding to the basic data;
and the first processing unit is used for respectively corresponding the basic data message queues to indexes corresponding to the basic data clusters according to the index fields in the data format.
10. The monitoring apparatus of micro service architecture according to claim 8, wherein the second processing module comprises:
the first detection unit is used for detecting whether the monitoring time of a preset monitoring interval period is reached;
the first matching unit is used for matching basic data in the basic data cluster according to a preset event model when the monitoring time of a preset monitoring interval period is reached;
and the second processing unit is used for obtaining the event message queue according to a preset event format if the matching is successful, wherein the event format comprises a plurality of fields corresponding to the basic data cluster.
11. The monitoring apparatus of micro service architecture according to claim 8, wherein the second obtaining module comprises:
the second detection unit is used for detecting whether the monitoring time of a preset monitoring interval period is reached;
the second matching unit is used for matching the event message queue according to a preset alarm model when the monitoring time of a preset monitoring interval period is reached;
and the acquisition unit is used for acquiring the alarm information according to the matching result and sending the alarm information to the user terminal if the matching is successful.
12. The microservice architecture monitoring device of claim 8, wherein the device further comprises:
and the sending module is used for sending a self-recovery instruction according to the event message queue.
13. The monitoring apparatus of micro service architecture according to claim 12, wherein the sending module comprises:
the third detection unit is used for detecting whether the monitoring time of the preset monitoring interval period is reached;
the third matching unit is used for matching the event message queue according to a preset self-recovery model when the monitoring time of a preset monitoring interval period is reached;
and the sending unit is used for sending a self-recovery instruction to the service port corresponding to the event in the event message queue which is successfully matched if the matching is successful.
14. The microservice architecture monitoring device of claim 8, wherein the device further comprises:
and the third acquisition module is used for respectively corresponding the event message queues to indexes corresponding to the event data clusters according to the index fields in the event formats.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910899307.2A CN112543127A (en) | 2019-09-23 | 2019-09-23 | Monitoring method and device of micro-service architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910899307.2A CN112543127A (en) | 2019-09-23 | 2019-09-23 | Monitoring method and device of micro-service architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112543127A true CN112543127A (en) | 2021-03-23 |
Family
ID=75012967
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910899307.2A Pending CN112543127A (en) | 2019-09-23 | 2019-09-23 | Monitoring method and device of micro-service architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112543127A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113157523A (en) * | 2021-04-21 | 2021-07-23 | 平安付科技服务有限公司 | Service monitoring method and device, computer equipment and storage medium |
| CN114979132A (en) * | 2022-04-13 | 2022-08-30 | 京东科技信息技术有限公司 | Cluster component state detection method and device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107682351A (en) * | 2017-10-20 | 2018-02-09 | 携程旅游网络技术（上海）有限公司 | Method, system, equipment and the storage medium of network security monitoring |
| CN108259522A (en) * | 2016-12-28 | 2018-07-06 | 中兴通讯股份有限公司 | A kind of bullet contracting method and device of PaaS platform containerization application |
| US20180373745A1 (en) * | 2017-06-26 | 2018-12-27 | International Business Machines Corporation | Import, export, and copy management for tiered object storage |
| CN109726272A (en) * | 2018-12-20 | 2019-05-07 | 杭州数梦工场科技有限公司 | Audit regulation recommended method and device |
| CN109861995A (en) * | 2019-01-17 | 2019-06-07 | 安徽谛听信息科技有限公司 | A kind of safe big data intelligent analysis method of cyberspace, computer-readable medium |
| CN109885562A (en) * | 2019-01-17 | 2019-06-14 | 安徽谛听信息科技有限公司 | A kind of big data intelligent analysis system based on cyberspace safety |
| CN109961204A (en) * | 2017-12-26 | 2019-07-02 | 中国移动通信集团浙江有限公司 | Quality of service analysis method and system under a kind of micro services framework |
| CN110245158A (en) * | 2019-06-10 | 2019-09-17 | 上海理想信息产业（集团）有限公司 | A kind of multi-source heterogeneous generating date system and method based on Flink stream calculation technology |
-
2019
- 2019-09-23 CN CN201910899307.2A patent/CN112543127A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108259522A (en) * | 2016-12-28 | 2018-07-06 | 中兴通讯股份有限公司 | A kind of bullet contracting method and device of PaaS platform containerization application |
| US20180373745A1 (en) * | 2017-06-26 | 2018-12-27 | International Business Machines Corporation | Import, export, and copy management for tiered object storage |
| CN107682351A (en) * | 2017-10-20 | 2018-02-09 | 携程旅游网络技术（上海）有限公司 | Method, system, equipment and the storage medium of network security monitoring |
| CN109961204A (en) * | 2017-12-26 | 2019-07-02 | 中国移动通信集团浙江有限公司 | Quality of service analysis method and system under a kind of micro services framework |
| CN109726272A (en) * | 2018-12-20 | 2019-05-07 | 杭州数梦工场科技有限公司 | Audit regulation recommended method and device |
| CN109861995A (en) * | 2019-01-17 | 2019-06-07 | 安徽谛听信息科技有限公司 | A kind of safe big data intelligent analysis method of cyberspace, computer-readable medium |
| CN109885562A (en) * | 2019-01-17 | 2019-06-14 | 安徽谛听信息科技有限公司 | A kind of big data intelligent analysis system based on cyberspace safety |
| CN110245158A (en) * | 2019-06-10 | 2019-09-17 | 上海理想信息产业（集团）有限公司 | A kind of multi-source heterogeneous generating date system and method based on Flink stream calculation technology |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113157523A (en) * | 2021-04-21 | 2021-07-23 | 平安付科技服务有限公司 | Service monitoring method and device, computer equipment and storage medium |
| CN114979132A (en) * | 2022-04-13 | 2022-08-30 | 京东科技信息技术有限公司 | Cluster component state detection method and device |
| CN114979132B (en) * | 2022-04-13 | 2024-05-17 | 京东科技信息技术有限公司 | Cluster component state detection method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107992398B (en) | Monitoring method and monitoring system of service system | |
| CN109284269B (en) | Abnormal log analysis method and device, storage medium and server | |
| US20180365085A1 (en) | Method and apparatus for monitoring client applications | |
| CN101997925A (en) | Server monitoring method with early warning function and system thereof | |
| CN111046011B (en) | Log collection method, system, device, electronic equipment and readable storage medium | |
| CN111881011A (en) | Log management method, platform, server and storage medium | |
| CN110688280B (en) | Management system, method, equipment and storage medium for alarm event | |
| CN109885453B (en) | Big data platform monitoring system based on stream data processing | |
| CN108228322B (en) | Distributed link tracking and analyzing method, server and global scheduler | |
| CN111046022A (en) | Database auditing method based on big data technology | |
| CN112543127A (en) | Monitoring method and device of micro-service architecture | |
| CN110990365A (en) | Data synchronization method, device, server and storage medium | |
| CN115016973A (en) | Method, device, equipment and medium for reproducing program crash event | |
| CN112235262A (en) | Message analysis method and device, electronic equipment and computer readable storage medium | |
| CN105303430B (en) | Transaction index acquisition method and device | |
| CN114090529A (en) | Log management method, device, system and storage medium | |
| CN110636116B (en) | Multidimensional data acquisition system and method | |
| CN109189652A (en) | A kind of acquisition method and system of close network terminal behavior data | |
| CN112506954A (en) | Database auditing method and device | |
| CN116881100A (en) | Log detection method, log alarm method, system, equipment and storage medium | |
| CN110717130B (en) | Dotting method, dotting device, dotting terminal and storage medium | |
| CN113297245A (en) | Method and device for acquiring execution information | |
| CN111784176A (en) | Data processing method, device, server and medium | |
| CN111552618A (en) | Method and device for collecting logs | |
| CN115525392A (en) | Container monitoring method and device, electronic equipment and storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210323 |