CN111124830A - Monitoring method and device for micro-service - Google Patents
Monitoring method and device for micro-service Download PDFInfo
- Publication number
- CN111124830A CN111124830A CN201911343029.9A CN201911343029A CN111124830A CN 111124830 A CN111124830 A CN 111124830A CN 201911343029 A CN201911343029 A CN 201911343029A CN 111124830 A CN111124830 A CN 111124830A
- Authority
- CN
- China
- Prior art keywords
- target
- monitoring
- sending
- data
- 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.)
- Granted
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 100
- 238000000034 method Methods 0.000 title claims abstract description 47
- 230000000007 visual effect Effects 0.000 claims abstract description 12
- 230000002159 abnormal effect Effects 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 10
- 238000012806 monitoring device Methods 0.000 claims description 5
- 238000004458 analytical method Methods 0.000 claims description 4
- 238000001514 detection method Methods 0.000 claims description 4
- 238000012423 maintenance Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 10
- 238000012800 visualization Methods 0.000 description 7
- 230000004044 response Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012549 training Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
- G06F16/1824—Distributed file systems implemented using Network-attached Storage [NAS] architecture
- G06F16/1827—Management specifically adapted to NAS
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Mathematical Physics (AREA)
- Library & Information Science (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a monitoring method and a device of micro-service, wherein the monitoring method comprises the following steps: acquiring a target log file which is automatically output to an NAS directory by all target application services; analyzing the target log file, and sending the target log data extracted after analyzing the target log file to a target message queue; monitoring target log data in a target message queue, and judging whether the target log data in the target message queue meets a first preset index; if not, the information that the target log data does not accord with the first preset index is sent to the designated address. The invention can carry out multi-dimensional monitoring on the micro-service and can provide a visual query interface.
Description
Technical Field
The invention relates to the technical field of monitoring application, in particular to a monitoring method and a monitoring device for micro-services.
Background
The traditional micro-service monitoring method is layered monitoring, common layering can be divided into a user terminal layer, a service layer, an application layer, a system layer and a machine room layer, and different monitoring methods are used in different layers. Conventional monitoring software zabbix (an enterprise-level open source solution providing distributed system monitoring and network monitoring functions based on a WEB interface) is relatively common, however, the configuration of zabbix is relatively complex, and the monitoring dimension is relatively single by taking a machine as a monitoring dimension. At present, most software industries use micro service technology architecture to perform atomic splitting on service functions to form independent applications for running. Microservice monitoring changes the most obvious over traditional monitoring, from monitoring hierarchy and machine as a central perspective to service as a central perspective. Micro-service monitoring can be currently divided into index monitoring, log monitoring and link monitoring, and an open source community also has a corresponding solution, for example, the index monitoring has promethues (open source monitoring system), the log monitoring has ELK (log analysis system), and the link monitoring has zipkin. The micro-service technology architecture adopts a multi-service multi-application mode, the traditional monitoring method has single monitoring dimension and cannot be suitable for the current micro-service architecture concept, the existing micro-service monitoring scheme has single function, cannot realize all-dimensional monitoring and visualization, cannot realize multi-dimensional monitoring on the micro-service, undoubtedly brings much inconvenience to the work of developers and operation and maintenance personnel, not only influences the working efficiency, but also cannot guarantee timely and effective solution of system faults.
Disclosure of Invention
The embodiment of the invention provides a monitoring method and a monitoring device for micro services, which aim to solve the following problems in the prior art: the existing micro-service monitoring scheme has single function, cannot realize all-dimensional monitoring, cannot realize visualization, and cannot carry out multi-dimensional monitoring on micro-services.
In order to solve the above technical problem, a first technical solution adopted in the embodiments of the present invention is as follows:
a method of monitoring microservices, comprising: acquiring a target log file which is automatically output to an NAS directory by all target application services; analyzing the target log file, and sending target log data extracted after analyzing the target log file to a target message queue; monitoring the target log data in the target message queue and judging whether the target log data in the target message queue meets a first preset index; if not, sending the information that the target log data does not accord with the first preset index to a specified address.
Optionally, after acquiring the target log file that is output to the NAS directory by all the target application services, the method further includes: acquiring node index data and container index data of a target server cluster, and sending the node index data and the container index data to the target message queue; monitoring the node index data and the container index data in the target message queue, and judging whether the node index data and/or the container index data in the target message queue meet a second preset index; and if not, sending the information that the node index data and/or the container index data in the target message queue do not accord with the second preset index to the designated address.
Optionally, after the sending the information that the target log data does not meet the first preset index to the designated address, the method includes: and generating a visual first view interface according to the monitoring result of the target log data in the target message queue, and sending the first view interface to the designated address.
Optionally, after the sending the information that the node metric data and/or the container metric data in the target message queue do not meet the second preset metric to the designated address, the method includes: and generating a visual second view interface according to the monitoring results of the node index data and the container index data in the target message queue, and sending the second view interface to the designated address.
Optionally, when the obtaining of the target log file that is output to the NAS directory by all the target application services, the method further includes: performing heartbeat detection on all the target application services, and judging whether the target application services in abnormal states exist or not; if yes, sending the information of the target application service with the abnormal state to the designated address, or generating a visual third view interface from the information of the target application service with the abnormal state, and sending the third view interface to the designated address.
Optionally, after the sending the information of the target application service in the abnormal state to the designated address, or generating a visualized third view interface from the information of the target application service in the abnormal state, and sending the third view interface to the designated address, the method further includes: and sending the information of the target application service with the abnormal state to a search server, or sending the third view interface to the search server.
Optionally, after acquiring the target log file that is output to the NAS directory by all the target application services, the method further includes: and sending all the target log files output to the NAS directory to a distributed file system server for saving and backup.
In order to solve the above technical problem, a second technical solution adopted in the embodiments of the present invention is as follows:
a monitoring device of a microservice, comprising: the file acquisition module is used for acquiring a target log file which is automatically output to the NAS directory by all target application services; the analysis uploading module is used for analyzing the target log file and sending the target log data extracted after the target log file is analyzed to a target message queue; the monitoring and judging module is used for monitoring the target log data in the target message queue and judging whether the target log data in the target message queue meets a first preset index or not; and the information sending module is used for sending the information that the target log data do not accord with the first preset index to a designated address when the target log data in the target message queue do not accord with the first preset index.
In order to solve the above technical problem, a third technical solution adopted in the embodiments of the present invention is as follows:
a computer-readable storage medium, on which a computer program is stored, which, when executed, implements the microservice monitoring method as described above.
In order to solve the above technical problem, a fourth technical solution adopted in the embodiments of the present invention is as follows:
a computer device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the processor implementing the monitoring method of a microservice as described above when executing the computer program.
The embodiment of the invention has the beneficial effects that: different from the situation in the prior art, the embodiment of the present invention obtains the target log file that is automatically output to the NAS directory by all the target application services, then analyzes the target log, sends the analyzed target log data to the target message queue, monitors the target log data in the target message queue, and determines whether the target log data in the target message queue meets the first preset index, and if not, sends the information that the target log data does not meet the first preset index to the designated address, thereby solving the following problems in the prior art: the existing micro-service monitoring scheme has single function, cannot realize all-dimensional monitoring, cannot realize visualization, and cannot carry out multi-dimensional monitoring on micro-services.
Drawings
FIG. 1 is a flowchart illustrating an implementation of an embodiment of a monitoring method for a microservice according to a first embodiment of the present invention;
FIG. 2 is a partial block diagram of a monitoring device for microservices according to a second embodiment of the present invention;
FIG. 3 is a partial structural framework diagram of an embodiment of a computer-readable storage medium according to a third embodiment of the present invention;
fig. 4 is a partial structural framework diagram of an embodiment of a computer device according to a fourth embodiment of the present invention.
Detailed Description
Example one
Referring to fig. 1, fig. 1 is a flowchart illustrating an implementation of a monitoring method for a microservice according to an embodiment of the present invention, which can be obtained by referring to fig. 1, and the monitoring method for a microservice according to the present invention includes:
step S101: and acquiring a target log file which is output to the NAS directory by all the target application services. All target application services are packaged into a docker image and are deployed in a K8S cluster, and K8S, Kubernetes, is a Google open-source container cluster management system. The target log comprises a service measurement log file, a service error log file, a daily output log file, a service response log file and a service http request log file, all log file configuration rules generate a new file when exceeding a preset value, such as 10M, and the new file is output to a shared NAS path in a designated mode and uploaded to an Ali cloud distributed file system OSS.
Among them, NAS (Network Attached Storage), which is a device connected to a Network and having a data Storage function, is also called a "Network Storage", and is a dedicated data Storage server. The data center is used for completely separating the storage equipment from the server and managing the data in a centralized manner, so that the bandwidth is released, the performance is improved, the total cost of ownership is reduced, and the investment is protected. The cost is far lower than using server storage, while the efficiency is far higher than the latter.
Step S102: and analyzing the target log file, and sending the target log data extracted after analyzing the target log file to a target message queue. The message queue is optionally Kafka, which is a high-throughput distributed publish-subscribe message system that can handle all the action flow data of the user in the website. In this step, optionally, the log is parsed by using a Logstash tool and output to the message queue Kafka. Where each message of Kafka has a corresponding type, each type being sent to a different set.
Step S103: monitoring the target log data in the target message queue, and judging whether the target log data in the target message queue meets a first preset index.
Step S104: and when the target log data in the target message queue do not accord with a first preset index, sending the information that the target log data do not accord with the first preset index to a specified address.
Step S105: and when the target log in the target message queue conforms to a first preset index, not sending the information that the target log data does not conform to the first preset index to a specified address.
In this embodiment, optionally, after acquiring the target log file that is output to the NAS directory by itself by all the target application services, the method further includes:
firstly, acquiring node index data and container index data of a target server cluster (Kubernets), and sending the node index data and the container index data to the target message queue.
Secondly, monitoring the node index data and the container index data in the target message queue, and judging whether the node index data and/or the container index data in the target message queue meet a second preset index.
Thirdly, when the node index data and/or the container index data in the target message queue do not accord with a second preset index, sending the information that the node index data and/or the container index data in the target message queue do not accord with the second preset index to the designated address.
In this embodiment, optionally, after the sending the information that the target log data does not meet the first preset index to the designated address, the method includes:
and generating a visual first view interface according to the monitoring result of the target log data in the target message queue, and sending the first view interface to the designated address. In the embodiment, data is queried through an elastic search (enterprise level search engine), and a visual view of various monitoring indexes is provided.
In this embodiment, optionally, after the sending, to the designated address, the information that the node metric data and/or the container metric data in the target message queue do not meet the second preset metric, the method includes:
and generating a visual second view interface according to the monitoring results of the node index data and the container index data in the target message queue, and sending the second view interface to the designated address.
In this embodiment, optionally, while acquiring the target log file that is output to the NAS directory by itself by all the target application services, the method further includes:
firstly, heartbeat detection is carried out on all the target application services, and whether the target application services in abnormal states exist is judged.
Firstly, when the target application service in the abnormal state exists, sending the information of the target application service in the abnormal state to the designated address, or generating a visual third view interface from the information of the target application service in the abnormal state, and sending the third view interface to the designated address.
In this embodiment, optionally, after the sending the information of the target application service in the abnormal state to the designated address, or generating a visualized third view interface from the information of the target application service in the abnormal state, and sending the third view interface to the designated address, the method further includes:
and sending the information of the target application service with the abnormal state to a search server, or sending the third view interface to the search server. Wherein the search server is an optional search server based on Lucene (full text search engine toolkit), which provides a distributed multi-user full text search engine. The Elasticsearch was developed in Java and published as open source under the Apache licensing terms, and is currently a popular enterprise-level search engine. Optionally, after the data are received by the Pass cloud platform as a log data user side, according to a preset index expression, related personnel are notified through mails and enterprise micro-communications when the index exceeds the preset index expression, and finally the data are output to the Elasticsearch.
In this embodiment, optionally, after acquiring the target log file that is output to the NAS directory by itself by all the target application services, the method further includes:
and sending all the target log files output to the NAS directory to a distributed file system server for saving and backup.
In this embodiment, optionally, the various preset indexes are as follows:
the node preset indexes can be selected as follows:
1. CPU utilization rate 90%, 2, memory utilization rate 90%, 3, disk utilization rate 85%, 4, network receiving and sending limit value 30M/s.
The preset indexes of the container can be selected as follows:
1. CPU utilization rate 90%, 2, memory utilization rate 90%, 3, network receiving and sending limit value 5M/s.
The service preset index can be selected as follows:
1. response time 1 second, 2, including Exception.
In the present embodiment, various indexes and explanations are optionally as follows:
firstly, node index specification:
1. when the Pass cloud platform monitors that the data type of Kafka is data of a node CPU, the current value is that the CPU utilization rate is 100%, and then 100% is greater than a preset index (90%), then the Pass cloud platform informs operation and maintenance personnel through mails or WeChat, the alarm is completed, and meanwhile, the data are stored in an elastic search.
2. When the Pass cloud platform monitors that the data type of Kafka is data of a node memory, the current value is the memory utilization rate of 92%, and then 92% is greater than a preset index (90%), then the Pass cloud platform informs operation and maintenance personnel through mails or WeChat, alarm is completed, and meanwhile the data are stored in an ElasticSearch.
3. When the Pass cloud platform monitors that the data type of Kafka is data of a node disk, the current value is the memory utilization rate of 90%, and then 90% > is a preset index (85%), then the Pass cloud platform informs operation and maintenance personnel through mails or WeChat, the alarm is completed, and meanwhile, the data are stored in an elastic search.
4. When the Pass cloud platform monitors that the data type of Kafka is data of a node network, the current value is 50MB/s, and then 50MB/s > a preset index (30M/s), the Pass cloud platform informs operation and maintenance personnel through mails or WeChat, the alarm is completed, and meanwhile, the data are stored in an ElasticSearch.
II, container index description:
1. when the data type of the Kafka is monitored by the Pass cloud platform as data of a container CPU, the current value is that the CPU utilization rate is 100%, and then 100% > is a preset index (90%), then the Pass cloud platform informs operation and maintenance personnel through mails or WeChat, the alarm is completed, and meanwhile the data are stored in an elastic search.
2. When the data type of the Kafka is monitored by the Pass cloud platform to be data of a container memory, the current value is 92% of the memory utilization rate, and then 92% is greater than a preset index (90%), and then the Pass cloud platform informs operation and maintenance personnel through mails or WeChat to complete alarming, and meanwhile, the data is stored in an ElasticSearch.
3. When the Pass cloud platform monitors that the data type of Kafka is data of a container network, the current value is 10MB/s, and then 10MB/s > a preset index (5M/s), the Pass cloud platform informs operation and maintenance personnel through mails or WeChat, the alarm is completed, and meanwhile, the data are stored in an ElasticSearch.
Third, log data description:
1. when the Pass cloud platform monitors that the data type of Kafka is target application service response data, the response time of the current interface A is 3 seconds, and then 3 seconds > a preset index (1 second), the Pass cloud platform informs operation and maintenance personnel through mails or micro-communication, alarm is completed, and meanwhile, the data are stored in an ElasticSearch.
2. And the Pass cloud platform monitors the data type of the Kafka as other service data, the current value comprises Exception information which indicates that Exception occurs, and then the Pass cloud platform informs operation and maintenance personnel through mails or micro-communication to complete alarm and store the data in an ElasticSearch.
Fourthly, heartbeat detection explanation:
firstly, each target application service opens an interface in advance as a heartbeat interface for the Paas cloud platform to detect in a round training manner. For example, if the service A, B and the service C exist, the Paas cloud platform requests heartbeat interfaces of the service A, B and the service C in a round-training mode, the target application service a responds normally, and the target application services B and C respond abnormally, it is indicated that the target application services B and C have problems, the pas cloud platform informs operation and maintenance personnel through mails or micro-messages, the alarm is completed, and meanwhile, data are stored in an elastic search.
The embodiment of the invention solves the following problems in the prior art by acquiring a target log file which is automatically output to an NAS directory by all target application services, analyzing the target log file, uploading target log data extracted after the target log file is analyzed to a target message queue, monitoring the target log data in the target message queue, judging whether the target log data in the target message queue meets a first preset index, and if not, sending information that the target log data does not meet the first preset index to a designated address: the existing micro-service monitoring scheme has single function, cannot realize all-dimensional monitoring, cannot realize visualization, and cannot carry out multi-dimensional monitoring on micro-services.
In addition, the invention also has the following beneficial effects: 1. hardware and software faults can be alarmed in real time, and technicians are prompted to repair the faults in time; 2. the visual multi-dimensional monitoring index and the micro-service log viewing interface are provided, so that technicians can know the current resource use condition more conveniently, the log viewing is more convenient, and the efficiency of solving and positioning problems is improved; 3. all monitoring data can be efficiently collected in real time, and uniformly written into a high-throughput message queue Kafka, so that the high-throughput message queue Kafka is convenient to rapidly store and process, and a query mechanism with rapid response can be provided; 4. the method provides multi-dimensional monitoring, such as server hardware indexes (CPU utilization rate, total memory, used memory, total disk space, used disk space, network sending flow and receiving flow), container monitoring indexes (container occupied memory, container CPU utilization rate, container network sending and receiving flow), service monitoring indexes (JVM memory condition, service response time, service request record and service throughput), can monitor hardware resources in real time and guarantee high availability of service, and provides data basis for later service optimization.
Example two
Referring to fig. 2, fig. 2 is a partial structural framework diagram of a monitoring apparatus 100 for micro services according to an embodiment of the present invention, which can be obtained by combining fig. 2, and the monitoring apparatus 100 for micro services according to the present invention includes:
the file obtaining module 110 is configured to obtain a target log file that is output to the NAS directory by all the target application services.
And the analysis uploading module 120 is configured to analyze the target log file, and upload the target log data extracted after analyzing the target log file to a target message queue.
A monitoring and determining module 130, configured to monitor the target log data in the target message queue, and determine whether the target log data in the target message queue meets a first preset indicator.
The information sending module 140 is configured to, when the target log data in the target message queue does not meet a first preset index, send information that the target log data does not meet the first preset index to a specified address.
The embodiment of the invention solves the following problems in the prior art by acquiring a target log file which is automatically output to an NAS directory by all target application services, analyzing the target log file, uploading target log data extracted after the target log file is analyzed to a target message queue, monitoring the target log data in the target message queue, judging whether the target log data in the target message queue meets a first preset index, and if not, sending information that the target log data does not meet the first preset index to a designated address: the existing micro-service monitoring scheme has single function, cannot realize all-dimensional monitoring, cannot realize visualization, and cannot carry out multi-dimensional monitoring on micro-services.
EXAMPLE III
Referring to fig. 3, a computer-readable storage medium 10 according to an embodiment of the present invention can be seen, where the computer-readable storage medium 10 includes: ROM/RAM, magnetic disks, optical disks, etc., on which a computer program 11 is stored, which computer program 11, when executed, implements the method of monitoring microservices according to one embodiment. Since the monitoring method of the microservice is already described in detail in the first embodiment, the description is not repeated here.
The monitoring method of the microservice realized by the embodiment of the invention comprises the steps of acquiring a target log file which is automatically output to an NAS directory by all target application services, analyzing the target log file, uploading target log data extracted after the target log file is analyzed to a target message queue, monitoring the target log data in the target message queue, judging whether the target log data in the target message queue meets a first preset index, and if not, sending information that the target log data does not meet the first preset index to a designated address, thereby solving the following problems in the prior art: the existing micro-service monitoring scheme has single function, cannot realize all-dimensional monitoring, cannot realize visualization, and cannot carry out multi-dimensional monitoring on micro-services.
Example four
Referring to fig. 4, a computer device 20 according to an embodiment of the present invention includes a processor 21, a memory 22, and a computer program 221 stored in the memory 22 and running on the processor 21, wherein the processor 21 implements the method for monitoring square microservices according to an embodiment when executing the computer program 221. Since the monitoring method of the microservice is already described in detail in the first embodiment, the description is not repeated here.
The monitoring method of the microservice realized by the embodiment of the invention comprises the steps of acquiring a target log file which is automatically output to an NAS directory by all target application services, analyzing the target log file, uploading target log data extracted after the target log file is analyzed to a target message queue, monitoring the target log data in the target message queue, judging whether the target log data in the target message queue meets a first preset index, and if not, sending information that the target log data does not meet the first preset index to a designated address, thereby solving the following problems in the prior art: the existing micro-service monitoring scheme has single function, cannot realize all-dimensional monitoring, cannot realize visualization, and cannot carry out multi-dimensional monitoring on micro-services.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes performed by the present specification and drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A monitoring method of micro-services is characterized by comprising the following steps:
acquiring a target log file which is automatically output to an NAS directory by all target application services;
analyzing the target log file, and sending target log data extracted after analyzing the target log file to a target message queue;
monitoring the target log data in the target message queue and judging whether the target log data in the target message queue meets a first preset index;
if not, sending the information that the target log data does not accord with the first preset index to a specified address.
2. The method for monitoring microservice according to claim 1, wherein the step of obtaining the target log file that all target application services output to the NAS directory by themselves further comprises:
acquiring node index data and container index data of a target server cluster, and sending the node index data and the container index data to the target message queue;
monitoring the node index data and the container index data in the target message queue, and judging whether the node index data and/or the container index data in the target message queue meet a second preset index;
and if not, sending the information that the node index data and/or the container index data in the target message queue do not accord with the second preset index to the designated address.
3. The microservice monitoring method of claim 1, wherein sending the information that the target log data does not meet the first predetermined criteria to a designated address comprises:
and generating a visual first view interface according to the monitoring result of the target log data in the target message queue, and sending the first view interface to the designated address.
4. The method for monitoring microservice according to claim 1, wherein the sending the information that the node indicator data and/or the container indicator data in the target message queue do not meet the second preset indicator to the designated address comprises:
and generating a visual second view interface according to the monitoring results of the node index data and the container index data in the target message queue, and sending the second view interface to the designated address.
5. The method for monitoring microservice according to claim 1, wherein the method for acquiring the target log file that is output to the NAS directory by all the target application services comprises:
performing heartbeat detection on all the target application services, and judging whether the target application services in abnormal states exist or not;
if yes, sending the information of the target application service with the abnormal state to the designated address, or generating a visual third view interface from the information of the target application service with the abnormal state, and sending the third view interface to the designated address.
6. The method for monitoring microservice according to claim 5, wherein after the sending the information of the target application service in the abnormal state to the designated address, or generating a visualized third view interface from the information of the target application service in the abnormal state, and sending the third view interface to the designated address, the method further comprises:
and sending the information of the target application service with the abnormal state to a search server, or sending the third view interface to the search server.
7. The method for monitoring microservice according to claim 1, wherein the step of obtaining the target log file that all target application services output to the NAS directory by themselves further comprises:
and sending all the target log files output to the NAS directory to a distributed file system server for saving and backup.
8. A monitoring device for microservice, comprising:
the file acquisition module is used for acquiring a target log file which is automatically output to the NAS directory by all target application services;
the analysis uploading module is used for analyzing the target log file and sending the target log data extracted after the target log file is analyzed to a target message queue;
the monitoring and judging module is used for monitoring the target log data in the target message queue and judging whether the target log data in the target message queue meets a first preset index or not;
and the information sending module is used for sending the information that the target log data do not accord with the first preset index to a designated address when the target log data in the target message queue do not accord with the first preset index.
9. A computer-readable storage medium, having stored thereon a computer program which, when executed, implements the monitoring method of microservice of any of claims 1-7.
10. A computer device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, wherein the processor implements the monitoring method of microservice according to any one of claims 1 to 7 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911343029.9A CN111124830B (en) | 2019-12-24 | 2019-12-24 | Micro-service monitoring method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911343029.9A CN111124830B (en) | 2019-12-24 | 2019-12-24 | Micro-service monitoring method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111124830A true CN111124830A (en) | 2020-05-08 |
| CN111124830B CN111124830B (en) | 2024-01-19 |
Family
ID=70501634
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911343029.9A Active CN111124830B (en) | 2019-12-24 | 2019-12-24 | Micro-service monitoring method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111124830B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111338691A (en) * | 2020-05-20 | 2020-06-26 | 南京江北新区生物医药公共服务平台有限公司 | Container cloud platform based on k8s and supporting realization of micro-services and devops system |
| CN111625419A (en) * | 2020-05-15 | 2020-09-04 | 浪潮电子信息产业股份有限公司 | Log acquisition method, system, equipment and computer readable storage medium |
| CN112291805A (en) * | 2020-10-29 | 2021-01-29 | 浪潮电子信息产业股份有限公司 | OMC system monitoring method, device, equipment and readable storage medium |
| CN112527618A (en) * | 2020-12-17 | 2021-03-19 | 中国农业银行股份有限公司 | Log collection method and log collection system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016180265A1 (en) * | 2015-05-13 | 2016-11-17 | 阿里巴巴集团控股有限公司 | Log event processing method and device |
| CN107590048A (en) * | 2017-07-31 | 2018-01-16 | 北京北信源软件股份有限公司 | A kind of micro services log-output method and device |
| CN108304704A (en) * | 2018-02-07 | 2018-07-20 | 平安普惠企业管理有限公司 | Authority control method, device, computer equipment and storage medium |
| CN109446173A (en) * | 2018-09-18 | 2019-03-08 | 平安科技（深圳）有限公司 | Daily record data processing method, device, computer equipment and storage medium |
| US20190089809A1 (en) * | 2017-09-15 | 2019-03-21 | Oracle International Corporation | Dynamic message queues for a microservice based cloud service |
| CN110309130A (en) * | 2018-03-21 | 2019-10-08 | 中国人民财产保险股份有限公司 | A kind of method and device for host performance monitor |
| US20190334789A1 (en) * | 2018-04-26 | 2019-10-31 | EMC IP Holding Company LLC | Generating Specifications for Microservices Implementations of an Application |
-
2019
- 2019-12-24 CN CN201911343029.9A patent/CN111124830B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016180265A1 (en) * | 2015-05-13 | 2016-11-17 | 阿里巴巴集团控股有限公司 | Log event processing method and device |
| CN107590048A (en) * | 2017-07-31 | 2018-01-16 | 北京北信源软件股份有限公司 | A kind of micro services log-output method and device |
| US20190089809A1 (en) * | 2017-09-15 | 2019-03-21 | Oracle International Corporation | Dynamic message queues for a microservice based cloud service |
| CN108304704A (en) * | 2018-02-07 | 2018-07-20 | 平安普惠企业管理有限公司 | Authority control method, device, computer equipment and storage medium |
| CN110309130A (en) * | 2018-03-21 | 2019-10-08 | 中国人民财产保险股份有限公司 | A kind of method and device for host performance monitor |
| US20190334789A1 (en) * | 2018-04-26 | 2019-10-31 | EMC IP Holding Company LLC | Generating Specifications for Microservices Implementations of an Application |
| CN109446173A (en) * | 2018-09-18 | 2019-03-08 | 平安科技（深圳）有限公司 | Daily record data processing method, device, computer equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 张振;刘俊艳;: "基于微服务架构的日志监控系统的设计与实现", 软件, no. 11, pages 204 - 209 * |
| 陈建娟;刘行行;: "基于Kubernetes的分布式ELK日志分析系统", 电子技术与软件工程, no. 15, pages 218 - 219 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111625419A (en) * | 2020-05-15 | 2020-09-04 | 浪潮电子信息产业股份有限公司 | Log acquisition method, system, equipment and computer readable storage medium |
| CN111338691A (en) * | 2020-05-20 | 2020-06-26 | 南京江北新区生物医药公共服务平台有限公司 | Container cloud platform based on k8s and supporting realization of micro-services and devops system |
| CN112291805A (en) * | 2020-10-29 | 2021-01-29 | 浪潮电子信息产业股份有限公司 | OMC system monitoring method, device, equipment and readable storage medium |
| CN112291805B (en) * | 2020-10-29 | 2023-11-07 | 浪潮电子信息产业股份有限公司 | OMC system monitoring method, device, equipment and readable storage medium |
| CN112527618A (en) * | 2020-12-17 | 2021-03-19 | 中国农业银行股份有限公司 | Log collection method and log collection system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111124830B (en) | 2024-01-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111124830A (en) | Monitoring method and device for micro-service | |
| CN108874640B (en) | Cluster performance evaluation method and device | |
| US9672085B2 (en) | Adaptive fault diagnosis | |
| US11457029B2 (en) | Log analysis based on user activity volume | |
| US9548886B2 (en) | Help desk ticket tracking integration with root cause analysis | |
| US10116534B2 (en) | Systems and methods for WebSphere MQ performance metrics analysis | |
| CN108521339B (en) | Feedback type node fault processing method and system based on cluster log | |
| RU2013151607A (en) | INTER-CLOUD MANAGEMENT AND TROUBLESHOOTING | |
| Picoreti et al. | Multilevel observability in cloud orchestration | |
| US20150281011A1 (en) | Graph database with links to underlying data | |
| CN104410671B (en) | A kind of snapshot grasping means and data supervising device | |
| CN112835792B (en) | Pressure testing system and method | |
| CN111382023A (en) | Code fault positioning method, device, equipment and storage medium | |
| CN111585840A (en) | Service resource monitoring method, device and equipment | |
| CN116719664B (en) | Application and cloud platform cross-layer fault analysis method and system based on micro-service deployment | |
| US10574552B2 (en) | Operation of data network | |
| Bellini et al. | A knowledge base driven solution for smart cloud management | |
| CN102546235B (en) | Performance diagnosis method and system of web-oriented application under cloud computing environment | |
| CN113504996A (en) | Load balance detection method, device, equipment and storage medium | |
| CN115525392A (en) | Container monitoring method and device, electronic equipment and storage medium | |
| KR101288535B1 (en) | Method for monitoring communication system and apparatus therefor | |
| Brim et al. | Monitoring extreme-scale Lustre toolkit | |
| US20140025788A1 (en) | Metrics for network configuration items | |
| CN112416719A (en) | Monitoring processing method, system, equipment and storage medium for database container | |
| AU2014200806B1 (en) | Adaptive fault diagnosis |
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 |