WO2022088803A1 - 基于云环境的系统信息分析方法、装置、电子设备及介质 - Google Patents
基于云环境的系统信息分析方法、装置、电子设备及介质 Download PDFInfo
- Publication number
- WO2022088803A1 WO2022088803A1 PCT/CN2021/109392 CN2021109392W WO2022088803A1 WO 2022088803 A1 WO2022088803 A1 WO 2022088803A1 CN 2021109392 W CN2021109392 W CN 2021109392W WO 2022088803 A1 WO2022088803 A1 WO 2022088803A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- monitoring
- information
- collection
- request
- monitoring information
- Prior art date
Links
- 238000004458 analytical method Methods 0.000 title claims abstract description 96
- 238000012544 monitoring process Methods 0.000 claims abstract description 723
- 238000000034 method Methods 0.000 claims abstract description 44
- 238000012545 processing Methods 0.000 claims abstract description 30
- 230000008569 process Effects 0.000 claims description 13
- 238000012423 maintenance Methods 0.000 description 24
- 230000006870 function Effects 0.000 description 16
- 230000003993 interaction Effects 0.000 description 15
- 230000005540 biological transmission Effects 0.000 description 12
- 230000002159 abnormal effect Effects 0.000 description 10
- 230000007246 mechanism Effects 0.000 description 6
- 238000009825 accumulation Methods 0.000 description 5
- 238000004364 calculation method Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 230000000717 retained effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010365 information processing 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
- 238000007619 statistical method Methods 0.000 description 1
- 238000006467 substitution reaction Methods 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/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Definitions
- the present application relates to the technical field of big data, and in particular, to a method, apparatus, electronic device and medium for analyzing system information based on a cloud environment.
- a first aspect of the present application provides a system information analysis method based on a cloud environment, which is applied to a first server, and the method includes:
- the analysis result of the second server is obtained by analyzing according to the third monitoring information and the device identifier.
- a second aspect of the present application provides an electronic device, the electronic device comprising a memory and a processor, the memory for storing at least one computer-readable instruction, the processor for executing the at least one computer-readable instruction to Implement the following steps:
- the analysis result of the second server is obtained by analyzing according to the third monitoring information and the device identifier.
- a third aspect of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores at least one computer-readable instruction, and when the at least one computer-readable instruction is executed by a processor, implements the following steps:
- the analysis result of the second server is obtained by analyzing according to the third monitoring information and the device identifier.
- a fourth aspect of the present application provides a system information analysis device based on a cloud environment, which runs in the first server, and the device includes:
- a receiving module configured to receive the monitoring request sent by the second server and parse the monitoring request to obtain the monitoring identification, device identification and collection type;
- an obtaining module configured to obtain the first monitoring information of the monitoring request according to the collection type
- a sending module configured to send the first monitoring information of the monitoring request to a message queue corresponding to the monitoring identifier
- a processing module configured to receive the second monitoring information of the monitoring request transmitted by the message queue, and process the second monitoring information of the monitoring request to obtain third monitoring information
- An analysis module configured to perform analysis according to the third monitoring information and the device identifier to obtain an analysis result of the second server.
- the cloud-based system information analysis method, device, electronic device and medium described in this application on the one hand, obtain the analysis result of each second server by analyzing the third monitoring information of different dimensions, which improves the performance of the system.
- the accuracy rate of the analysis result after monitoring on the other hand, by adopting the second monitoring information of the monitoring request transmitted in the form of a message queue, it is possible to avoid the accumulation of excessive second monitoring information and cause the slow transmission of the second monitoring information, and improve the second monitoring information.
- the transmission efficiency and correct rate of monitoring information finally, by determining different acquisition methods of the first monitoring information according to different collection types, the collection types can be deployed according to different scenarios, that is, according to the hardware equipment of the second server Some or all of the information is collected in the configuration situation or in different business scenarios, which improves the efficiency and diversity of monitoring, thereby improving the accuracy of monitoring and analysis results.
- FIG. 1 is a flowchart of a preferred embodiment of a method for analyzing system information based on a cloud environment disclosed in the present application.
- FIG. 2 is a functional block diagram of a preferred embodiment of a system information analysis device based on a cloud environment disclosed in the present application.
- FIG. 3 is a schematic structural diagram of an electronic device implementing a preferred embodiment of the cloud environment-based system information analysis method of the present application.
- FIG. 1 is a flowchart of a method for analyzing system information based on a cloud environment provided by Embodiment 1 of the present application.
- the cloud-based system information analysis method can be applied to electronic devices.
- the method provided by the method of the present application can be directly integrated on the electronic device.
- the method for analyzing system information based on a cloud environment specifically includes the following steps. According to different requirements, the order of the steps in the flowchart can be changed, and some can be omitted.
- the cloud-based system information analysis method described in this application can be applied to a first server, wherein the first server is connected to a plurality of second servers, and the first server can be a monitoring platform for monitoring the cloud
- the running status of all the second servers in the environment that are communicatively connected to the first server specifically, the first server is used to monitor the running status of the application programs in each second server, wherein each second server Multiple application programs can be run simultaneously, and when each application program is running, a corresponding monitoring request is sent to the first server, and the first server performs monitoring according to the monitoring request sent by the application program of the second server.
- S11 Receive a monitoring request sent by the second server and parse the monitoring request to obtain a monitoring identifier, a device identifier, and a collection type.
- the first server needs to monitor multiple monitoring requests sent by multiple second servers.
- the monitoring requests are used to monitor different application programs in each second server.
- Each second server can run multiple application programs, and send a monitoring request for each application program.
- the collection type is used to determine the first monitoring information specifically collected by the monitoring request.
- the first monitoring information includes, but is not limited to, the request interface name corresponding to the monitoring request, the request Time, requesting user, requesting service application name, requesting parameters, requesting result, requesting running time, requesting interaction system, and requesting frequency.
- the analysis of the monitoring request to obtain the collection type includes:
- the collection information identifier does not exist in the monitoring request, it is determined that the collection type of the monitoring request is the full information collection type.
- the collection information identifier is used to uniquely identify the type of the first monitoring information collected by the monitoring request during monitoring, and the collection type is determined by judging whether there is a collection information identifier in the monitoring request.
- the collection type is determined to be a partial information collection type, that is, only the first monitoring information corresponding to the monitored collection information identifier is collected; if there is no collection information identifier in the monitoring request, it is determined to be full information collection.
- Type that is, to collect all monitored first monitoring information.
- different collection types indicate different ways of acquiring the first monitoring information.
- the obtaining the first monitoring information of the monitoring request according to the collection type includes:
- the collection type of the monitoring request is a partial information collection type, identifying each collection information identifier in the monitoring request, and performing information collection according to each collection information identifier to obtain first monitoring information;
- the collection type of the monitoring request is the full information collection type
- all information is collected according to a preset collection rule to obtain the first monitoring information.
- the collected information identifier is used to indicate the collected corresponding first monitoring information, and the first monitoring information corresponding to the monitoring request can be obtained according to the collected information identifier.
- the collection types can be deployed according to different scenarios, for example, according to the hardware device configuration of the second server or different Some or all of the information is collected in business scenarios, which improves the efficiency and diversity of monitoring.
- S13 Send the first monitoring information of the monitoring request to a message queue corresponding to the monitoring identifier.
- the monitoring identifier represents the monitoring type requested by the second server for monitoring, and different monitoring types correspond to different monitoring identifiers.
- the monitoring types include, but are not limited to, query, update, interaction, and customization.
- the sending the first monitoring information of the monitoring request to the message queue corresponding to the monitoring identifier includes:
- the monitoring information corresponding to each monitoring type is basically the same, the first monitoring information of the same monitoring type is stored in the same message queue, and the first monitoring information is classified and retained until the monitoring The request monitoring is completed, the phenomenon of the first monitoring information being lost is avoided, and the integrity of the first monitoring information is improved.
- the method further includes:
- the collection time of the first monitoring information is greater than the preset collection time threshold, the collection of the first monitoring information is stopped, and a new thread is started to collect the first monitoring information.
- the The compensation mechanism may be asynchronous sending or local storage, and through the compensation mechanism, manual compensation can be performed after the monitoring returns to normal, and the first monitoring information can be collected.
- the preset information collection time threshold may be preset, for example, may be preset to 30 seconds or 1 minute.
- S14 Receive the second monitoring information of the monitoring request transmitted by the message queue, and process the second monitoring information of the monitoring request to obtain third monitoring information.
- the second monitoring information is obtained by sorting and classifying the first monitoring information of the monitoring request in the message queue, and then the second monitoring information is transmitted through the message queue.
- the The first monitoring information corresponding to the same monitoring type is stored in the message queue
- the first server can obtain the second monitoring information after sorting and classifying the first monitoring information from the message queue
- the message The queue can save the second monitoring information of the monitoring request until the monitoring of the monitoring request is completed or the time stored in the message queue exceeds the preset storage time threshold, and the second monitoring information corresponding to the monitoring request is deleted.
- the monitoring information improves the correctness and integrity of the second monitoring information.
- the processing of the second monitoring information of the monitoring request to obtain the third monitoring information includes:
- the structured data is used as third monitoring information.
- the third-party search engine may be ES (ElasticSearch: distributed search engine).
- the distributed search engine processes the second monitoring information of the monitoring request, wherein the processing The process includes converting the second monitoring information into structured data, wherein the structured data may be preset according to historical monitoring information corresponding to each monitoring type.
- the monitoring information is converted into structured data in the third-party search engine.
- a plurality of key fields are extracted from the second monitoring information, and each key field is converted into structured data according to a preset format.
- the request time in the second monitoring information transmitted by the message queue is: 1998/1506, and the request time is converted into structured data according to a preset format: 1998-09-06.
- S15 Perform analysis according to the third monitoring information and the device identifier to obtain an analysis result of the second server.
- the third monitoring information of the monitoring request when the third monitoring information of the monitoring request is obtained, the third monitoring information corresponding to the multiple application programs running on the second server is obtained according to the device identifier of the monitoring request.
- the third monitoring information is obtained from different dimensions, and the analysis result of the second server is obtained by analyzing the third monitoring information of different dimensions, which improves the accuracy of the monitored analysis result.
- the first server is connected to multiple second servers, the multiple second servers can send monitoring requests to the first server at the same time, and each second server can send multiple monitoring requests at the same time request, specifically, when the first server receives multiple monitoring requests, the phenomenon of slow operation may occur.
- different methods are used for system information analyze.
- the method further includes:
- the multiple monitoring requests sent by the second server M are: monitoring the traffic consumed by the application programs A, B and C, the total amount of monitoring requests is equal to the preset total amount threshold 3,
- the first monitoring information obtained by monitoring the traffic consumed by the application is processed separately, and the monitoring request sent by the second server is obtained as follows: the A application consumes 20G of traffic; the B application consumes 5G of traffic, and the C application consumes 5G of traffic
- the flow rate is 8G
- the device identifier of the second server M is obtained as Q, and the predetermined flow rate corresponding to the Q is 100G.
- the analysis result obtained by the second server M is: The traffic is 33G, not exceeding 100G, and the second server M is running normally.
- each monitoring request sent by at least one second server when the total amount is less than the preset total amount threshold, analyze each monitoring request sent by at least one second server to obtain the monitoring identifier, device identifier and collection type of each monitoring request; according to the The collection type of each monitoring request obtains the first monitoring information of each monitoring request; sends the first monitoring information of each monitoring request to the message queue corresponding to the monitoring identifier; receives the message queue transmission
- the second monitoring information of each monitoring request is processed, and the third monitoring information is obtained by processing the second monitoring information of each monitoring request; and the analysis result of the at least one second server.
- the threshold of the total amount of monitoring requests is preset according to the proportion of the resources occupied by the server of the collected monitoring information.
- the total amount of the monitoring requests is greater than or equal to the preset total amount threshold, It is determined that the resource occupancy ratio of the collected monitoring information exceeds the operating requirements of the server.
- the monitoring information does not need to be classified and collected, and the first monitoring information is directly sent to a third-party search engine for processing to obtain the third monitoring information. Guaranteed monitoring efficiency.
- the method further includes:
- the analysis results are displayed to the monitoring interface in a preset display manner.
- the display mode can be preset according to the preference of the maintainer, and the analysis results can include, but are not limited to, the traffic used by each server, the update data, interaction data, and access frequency of each application, through Displaying the analysis result monitoring interface according to a preset display mode can assist maintenance personnel to quickly determine the running status of each application program and improve monitoring efficiency.
- an alarm is triggered to promptly remind maintenance personnel to monitor the abnormality in danger, and the maintenance personnel can quickly locate the abnormal data according to the data displayed in the monitoring interface. Monitoring and maintenance at the location reduces maintenance costs and improves the timeliness of maintenance.
- the monitoring request sent by the second server is to query the traffic used by the server, and if the obtained analysis result is that the traffic used by the second server exceeds the predetermined traffic of the second server, the excess traffic will be monitored. Perform charging, display the used traffic, excess traffic and charging on the monitoring interface, and send the analysis result to the second server; when the monitoring request sent by the second server is interaction, if the obtained analysis result When the interaction frequency sent for the second server exceeds the preset interaction frequency of the second server, the interaction operation of the second server is closed.
- maintenance personnel can be assisted in monitoring the operation of each second server, and when monitoring is abnormal, maintenance is performed according to the data displayed on the monitoring interface in a timely manner, which improves the timeliness of maintenance. performance and monitoring efficiency.
- the method for analyzing system information based on a cloud environment described in this embodiment obtains a monitoring identifier, a device identifier and a collection type by receiving a monitoring request sent by a second server and parsing the monitoring request; according to the collection type obtaining the first monitoring information of the monitoring request; sending the first monitoring information of the monitoring request to a message queue corresponding to the monitoring identifier; receiving the second monitoring information of the monitoring request transmitted by the message queue, and processing the second monitoring information of the monitoring request to obtain third monitoring information; and performing analysis according to the third monitoring information and the device identifier to obtain the analysis result of the second server.
- the analysis result of each second server is obtained by analyzing the third monitoring information of different dimensions, which improves the accuracy of the analysis result after monitoring;
- the second monitoring information of the monitoring request can avoid the accumulation of excessive second monitoring information and cause slow transmission of the second monitoring information, and improve the transmission efficiency and accuracy of the second monitoring information; finally, by determining different first monitoring information according to different collection types. 1.
- the collection type can be deployed according to different scenarios, that is, some or all of the information can be collected according to the hardware configuration of the second server or different business scenarios, which improves the monitoring efficiency and efficiency. diversity, thereby improving the accuracy of monitoring analysis results.
- the maintenance personnel can be assisted in monitoring the operation of each second server.
- maintenance can be carried out according to the data displayed in the monitoring interface in a timely manner, which improves the timeliness of maintenance and monitoring. efficiency.
- FIG. 2 is a structural diagram of an apparatus for analyzing system information based on a cloud environment provided in Embodiment 2 of the present application.
- the cloud-based system information analysis apparatus 20 may include a plurality of functional modules composed of program code segments.
- the program codes of each program segment in the system information analysis apparatus 20 based on cloud environment can be stored in the memory of the electronic device and executed by the at least one processor to execute (see description in FIG. 1 for details) cloud-based The function of the system information analysis of the environment.
- the system information analysis device 20 based on the cloud environment runs on the first server, and can be divided into multiple functional modules according to the functions performed by the system information analysis device 20 .
- the functional modules may include: a receiving module 201 , an obtaining module 202 , a sending module 203 , a processing module 204 , an analysis module 205 , a calculation module 206 and a judgment module 207 .
- a module referred to in this application refers to a series of computer-readable instruction segments that can be executed by at least one processor and can perform fixed functions, and are stored in a memory. In this embodiment, the functions of each module will be described in detail in subsequent embodiments.
- the apparatus for analyzing system information based on a cloud environment described in this embodiment may run in a first server, wherein the first server is connected to a plurality of second servers, and the first server may be a monitoring platform for Monitoring the running status of all second servers in the cloud environment that are communicatively connected to the first server, specifically, the first server is used to monitor the running status of applications in each second server, wherein each No.
- the second server can run multiple application programs at the same time, and when each application program is running, a corresponding monitoring request is sent to the first server, and the first server performs monitoring according to the monitoring request sent by the application program of the second server.
- the receiving module 201 is configured to receive a monitoring request sent by a second server and parse the monitoring request to obtain a monitoring identifier, a device identifier and a collection type.
- the first server needs to monitor multiple monitoring requests sent by multiple second servers.
- the monitoring requests are used to monitor different application programs in each second server.
- each second server can run multiple application programs, and send a monitoring request for each application program.
- the collection type is used to determine the first monitoring information specifically collected by the monitoring request.
- the first monitoring information includes, but is not limited to, the request interface name corresponding to the monitoring request, the request Time, requesting user, requesting service application name, requesting parameters, requesting result, requesting running time, requesting interaction system, and requesting frequency.
- the receiving module 201 parses the monitoring request to obtain a collection type including:
- the collection information identifier does not exist in the monitoring request, it is determined that the collection type of the monitoring request is the full information collection type.
- the collection information identifier is used to uniquely identify the type of the first monitoring information collected by the monitoring request during monitoring, and the collection type is determined by judging whether there is a collection information identifier in the monitoring request.
- the collection type is determined to be a partial information collection type, that is, only the first monitoring information corresponding to the monitored collection information identifier is collected; if there is no collection information identifier in the monitoring request, it is determined to be full information collection.
- Type that is, to collect all monitored first monitoring information.
- the obtaining module 202 is configured to obtain the first monitoring information of the monitoring request according to the collection type.
- different collection types indicate different ways of acquiring the first monitoring information.
- the obtaining module 202 obtaining the first monitoring information of the monitoring request according to the collection type includes:
- the collection type of the monitoring request is a partial information collection type, identifying each collection information identifier in the monitoring request, and performing information collection according to each collection information identifier to obtain first monitoring information;
- the collection type of the monitoring request is the full information collection type
- all information is collected according to a preset collection rule to obtain the first monitoring information.
- the collected information identifier is used to indicate the collected corresponding first monitoring information, and the first monitoring information corresponding to the monitoring request can be obtained according to the collected information identifier.
- the collection types can be deployed according to different scenarios, for example, according to the hardware device configuration of the second server or different Some or all of the information is collected in business scenarios, which improves the efficiency and diversity of monitoring.
- the sending module 203 is configured to send the first monitoring information of the monitoring request to a message queue corresponding to the monitoring identifier.
- the monitoring identifier represents the monitoring type requested by the second server for monitoring, and different monitoring types correspond to different monitoring identifiers.
- the monitoring types include, but are not limited to, query, update, interaction, and customization.
- the sending module 203 sending the first monitoring information of the monitoring request to the message queue corresponding to the monitoring identifier includes:
- the monitoring information corresponding to each monitoring type is basically the same, the first monitoring information of the same monitoring type is stored in the same message queue, and the first monitoring information is classified and retained until the monitoring The request monitoring is completed, the phenomenon of the first monitoring information being lost is avoided, and the integrity of the first monitoring information is improved.
- the sending module 203 sends the first monitoring information of the monitoring request to the message queue corresponding to the monitoring identification, monitor the collection time of the first monitoring information of the monitoring request; determine the first monitoring information of the monitoring request; Whether the collection time of the monitoring information is greater than the preset collection time threshold; when the collection time of the first monitoring information is less than or equal to the preset collection time threshold, send the first monitoring information of the monitoring request to In the message queue corresponding to the monitoring identifier; when the collection time of the first monitoring information is greater than the preset collection time threshold, stop collecting the first monitoring information, and start a new thread to perform the first monitoring Collection of monitoring information.
- the The compensation mechanism may be asynchronous sending or local storage, and through the compensation mechanism, manual compensation can be performed after the monitoring returns to normal, and the first monitoring information can be collected.
- the preset information collection time threshold may be preset, for example, may be preset to 30 seconds or 1 minute.
- the processing module 204 is configured to receive the second monitoring information of the monitoring request transmitted by the message queue, and process the second monitoring information of the monitoring request to obtain third monitoring information.
- the second monitoring information is obtained by sorting and classifying the first monitoring information of the monitoring request in the message queue, and then the second monitoring information is transmitted through the message queue.
- the The first monitoring information corresponding to the same monitoring type is stored in the message queue
- the first server can obtain the second monitoring information after sorting and classifying the first monitoring information from the message queue
- the message The queue can save the second monitoring information of the monitoring request until the monitoring of the monitoring request is completed or the time stored in the message queue exceeds the preset storage time threshold, and the second monitoring information corresponding to the monitoring request is deleted.
- the monitoring information improves the correctness and integrity of the second monitoring information.
- the processing module 204 processes the second monitoring information of the monitoring request to obtain third monitoring information including:
- the structured data is used as third monitoring information.
- the third-party search engine may be ES (ElasticSearch: distributed search engine).
- the distributed search engine processes the second monitoring information of the monitoring request, wherein the processing The process includes converting the second monitoring information into structured data, wherein the structured data may be preset according to historical monitoring information corresponding to each monitoring type.
- the monitoring information is converted into structured data in the third-party search engine.
- a plurality of key fields are extracted from the second monitoring information, and each key field is converted into structured data according to a preset format.
- the request time in the second monitoring information transmitted by the message queue is: 1998/1506, and the request time is converted into structured data according to a preset format: 1998-09-06.
- the analysis module 205 is configured to perform analysis according to the third monitoring information and the device identifier to obtain an analysis result of the second server.
- the third monitoring information of the monitoring request when the third monitoring information of the monitoring request is obtained, the third monitoring information corresponding to the multiple application programs running on the second server is obtained according to the device identifier of the monitoring request.
- the third monitoring information is obtained from different dimensions, and the analysis result of the second server is obtained by analyzing the third monitoring information of different dimensions, which improves the accuracy of the monitored analysis result.
- the first server is connected to multiple second servers, the multiple second servers can send monitoring requests to the first server at the same time, and each second server can send multiple monitoring requests at the same time request, specifically, when the first server receives multiple monitoring requests, the phenomenon of slow operation may occur.
- different methods are used for system information analyze.
- the calculation module 206 is configured to calculate the total amount of the monitoring requests received.
- the judgment module 207 is used for judging whether the total amount is greater than the preset total amount threshold; when the total amount is greater than or equal to the preset total amount threshold, obtain the first number of each monitoring request sent by each second server. Monitoring information, processing the first monitoring information of each monitoring request to obtain corresponding third monitoring information, and performing analysis according to the third monitoring information and the device identifier to obtain an analysis result of each second server.
- the multiple monitoring requests sent by the second server M are: monitoring the traffic consumed by the application programs A, B and C, the total amount of monitoring requests is equal to the preset total amount threshold 3,
- the first monitoring information obtained by monitoring the traffic consumed by the application is processed separately, and the monitoring request sent by the second server is obtained as follows: the A application consumes 20G of traffic; the B application consumes 5G of traffic, and the C application consumes 5G of traffic
- the flow rate is 8G
- the device identifier of the second server M is obtained as Q, and the predetermined flow rate corresponding to the Q is 100G.
- the analysis result obtained by the second server M is: The traffic is 33G, not exceeding 100G, and the second server M is running normally.
- each monitoring request sent by at least one second server when the total amount is less than the preset total amount threshold, analyze each monitoring request sent by at least one second server to obtain the monitoring identifier, device identifier and collection type of each monitoring request; according to the The collection type of each monitoring request obtains the first monitoring information of each monitoring request; sends the first monitoring information of each monitoring request to the message queue corresponding to the monitoring identifier; receives the message queue transmission
- the second monitoring information of each monitoring request is processed, and the third monitoring information is obtained by processing the second monitoring information of each monitoring request; and the analysis result of the at least one second server.
- the threshold of the total amount of monitoring requests is preset according to the proportion of the resources occupied by the server of the collected monitoring information.
- the total amount of the monitoring requests is greater than or equal to the preset total amount threshold, It is determined that the resource occupation ratio of the collected monitoring information exceeds the operating requirements of the server.
- the monitoring information does not need to be classified and collected, and the first monitoring information is directly sent to a third-party search engine for processing to obtain the third monitoring information. Guaranteed monitoring efficiency.
- the analysis result of each second server is obtained, the analysis result is displayed on the monitoring interface according to a preset display manner.
- the display mode can be preset according to the preference of the maintainer, and the analysis results can include, but are not limited to, the traffic used by each server, the update data, interaction data, and access frequency of each application, through Displaying the analysis result monitoring interface according to a preset display mode can assist maintenance personnel to quickly determine the running status of each application program and improve monitoring efficiency.
- an alarm is triggered to promptly remind maintenance personnel to monitor the abnormality in danger, and the maintenance personnel can quickly locate the abnormal data according to the data displayed in the monitoring interface. Monitoring and maintenance at the location reduces maintenance costs and improves the timeliness of maintenance.
- the monitoring request sent by the second server is to query the traffic used by the server, and if the obtained analysis result is that the traffic used by the second server exceeds the predetermined traffic of the second server, the excess traffic will be monitored. Perform charging, display the used traffic, excess traffic and charging on the monitoring interface, and send the analysis result to the second server; when the monitoring request sent by the second server is interaction, if the obtained analysis result When the interaction frequency sent for the second server exceeds the preset interaction frequency of the second server, the interaction operation of the second server is closed.
- maintenance personnel can be assisted in monitoring the operation of each second server, and when monitoring is abnormal, maintenance is performed according to the data displayed on the monitoring interface in a timely manner, which improves the timeliness of maintenance. performance and monitoring efficiency.
- the apparatus for analyzing system information based on a cloud environment described in this embodiment obtains the monitoring identifier, the device identifier and the collection type by receiving the monitoring request sent by the second server and parsing the monitoring request; according to the collection type obtaining the first monitoring information of the monitoring request; sending the first monitoring information of the monitoring request to a message queue corresponding to the monitoring identifier; receiving the second monitoring information of the monitoring request transmitted by the message queue, and processing the second monitoring information of the monitoring request to obtain third monitoring information; and performing analysis according to the third monitoring information and the device identifier to obtain the analysis result of the second server.
- the analysis result of each second server is obtained by analyzing the third monitoring information of different dimensions, which improves the accuracy of the analysis result after monitoring;
- the second monitoring information of the monitoring request can avoid the accumulation of excessive second monitoring information and cause slow transmission of the second monitoring information, and improve the transmission efficiency and accuracy of the second monitoring information; finally, by determining different first monitoring information according to different collection types. 1.
- the collection type can be deployed according to different scenarios, that is, some or all of the information can be collected according to the hardware configuration of the second server or different business scenarios, which improves the monitoring efficiency and efficiency. diversity, thereby improving the accuracy of monitoring analysis results.
- the maintenance personnel can be assisted in monitoring the operation of each second server.
- maintenance can be carried out according to the data displayed in the monitoring interface in a timely manner, which improves the timeliness of maintenance and monitoring. efficiency.
- the electronic device 3 includes a memory 31 , at least one processor 32 , at least one communication bus 33 and a transceiver 34 .
- the structure of the electronic device shown in FIG. 3 does not constitute a limitation of the embodiments of the present application, and may be a bus-type structure or a star-shaped structure, and the electronic device 3 may also include a schematic more or less other hardware or software, or a different arrangement of components is shown.
- the electronic device 3 is an electronic device that can automatically perform numerical calculation and/or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application-specific integrated circuits , programmable gate arrays, digital processors and embedded devices.
- the electronic device 3 may also include a client device, which includes but is not limited to any electronic product that can perform human-computer interaction with a client through a keyboard, a mouse, a remote control, a touchpad, or a voice-activated device, for example, Personal computers, tablets, smartphones, digital cameras, etc.
- the electronic device 3 is only an example, and other existing or future electronic products, if applicable to the present application, should also be included within the protection scope of the present application, and incorporated herein by reference .
- the memory 31 is used to store program codes and various data, such as the cloud-based system information analysis apparatus 20 installed in the electronic device 3 and implemented during the operation of the electronic device 3 High-speed, automatic access to programs or data.
- Described memory 31 comprises read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM) , One-time Programmable Read-Only Memory (OTPROM), Electronically-Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read- Only Memory, CD-ROM) or other optical disk storage, magnetic disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.
- Read-Only Memory Read-Only Memory
- PROM programmable read-only memory
- PROM erasable programmable read-only memory
- OTPROM One-time Programmable Read-Only Memory
- the at least one processor 32 may be composed of integrated circuits, for example, may be composed of a single packaged integrated circuit, or may be composed of multiple integrated circuits packaged with the same function or different functions, including one Or a combination of multiple central processing units (Central Processing units, CPUs), microprocessors, digital processing chips, graphics processors, and various control chips.
- the at least one processor 32 is the control core (Control Unit) of the electronic device 3, and uses various interfaces and lines to connect various components of the entire electronic device 3, by running or executing the program stored in the memory 31 or modules, and call data stored in the memory 31 to perform various functions of the electronic device 3 and process data.
- Control Unit Control Unit
- the at least one communication bus 33 is configured to enable connection communication between the memory 31 and the at least one processor 32 and the like.
- the electronic device 3 may also include a power source (such as a battery) for supplying power to the various components. Implement functions such as managing charging, discharging, and power consumption.
- the power source may also include one or more DC or AC power sources, recharging devices, power failure detection circuits, power converters or inverters, power status indicators, and any other components.
- the electronic device 3 may further include a variety of sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.
- the above-mentioned integrated units implemented in the form of software functional modules may be stored in a computer-readable storage medium.
- the above-mentioned software function modules are stored in a storage medium, and include several computer-readable instructions to enable a computer device (which may be a personal computer, an electronic device, or a network device, etc.) or a processor (processor) to execute various embodiments of the present application part of the method.
- the at least one processor 32 can execute the operating device of the electronic device 3 and various installed applications (such as the cloud-based system information analysis device 20 ) , program code, etc., for example, the various modules described above.
- Program codes are stored in the memory 31, and the at least one processor 32 can call the program codes stored in the memory 31 to perform related functions.
- each module described in FIG. 2 is a program code stored in the memory 31 and executed by the at least one processor 32, thereby realizing the functions of the various modules to achieve system information based on a cloud environment purpose of the analysis.
- the computer program may be divided into one or more modules/units, and the one or more modules/units are stored in the memory 31 and executed by the processor 32 to complete the present invention.
- the one or more modules/units may be a series of computer-readable instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device 3 .
- the computer program can be divided into a receiving module 201 , an obtaining module 202 , a sending module 203 , a processing module 204 , an analysis module 205 , a calculation module 206 and a judgment module 207 .
- the memory 31 stores a plurality of computer-readable instructions, and the plurality of computer-readable instructions are executed by the at least one processor 32 to implement the function of system information analysis based on a cloud environment .
- the computer-readable storage medium may be non-volatile or volatile.
- modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, and may be located in one place or distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
- each functional module in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
- the above-mentioned integrated units can be implemented in the form of hardware, or can be implemented in the form of hardware plus software function modules.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Software Systems (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
本申请涉及大数据技术领域，本申请提供一种基于云环境的系统信息分析方法、装置、电子设备及介质，所述方法包括：接收第二服务器发送的监控请求得到监控标识、设备标识及收集类型；根据收集类型获得第一监控信息；将第一监控信息发送至对应监控标识的消息队列中；接收消息队列传输的监控请求的第二监控信息，并对第二监控信息进行处理得到第三监控信息；根据第三监控信息和设备标识进行分析得到第二服务器的分析结果。本申请通过分析不同维度的第三监控信息得到所述第二服务器的分析结果，提高了监控后的分析结果的准确率。
Description
本申请要求于2020年10月30日提交中国专利局，申请号为202011194028.5申请名称为“基于云环境的系统信息分析方法、装置、电子设备及介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本申请涉及大数据技术领域，具体涉及一种基于云环境的系统信息分析方法、装置、电子设备及介质。
在云环境的情况下，面对大量的系统用户，随时随地都会有大量的请求，面对复杂而大量的请求，发明人发现需要监控云环境中的每个服务器的运行情况，并接收每个服务器发送的多个请求，根据多个请求针对不同维度进行统计分析，现有技术仅监控云环境上每个服务器的硬件方面的运行情况，无法根据不同的服务器运行的不同的应用程序进行针对性的服务监控，监控效率低下，使得监控后的分析结果准确率低。
发明内容
鉴于以上内容，有必要提出一种基于云环境的系统信息分析方法、装置、电子设备及介质，通过分析不同维度的第三监控信息得到第二服务器的分析结果，提高了监控后的分析结果的准确率。
本申请的第一方面提供一种基于云环境的系统信息分析方法，应用于第一服务器中，所述方法包括：
接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型；
根据所述收集类型获得所述监控请求的第一监控信息；
将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；
接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息；
根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
本申请的第二方面提供一种电子设备，所述电子设备包括存储器及处理器，所述存储器用于存储至少一个计算机可读指令，所述处理器用于执行所述至少一个计算机可读指令以实现以下步骤：
接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型；
根据所述收集类型获得所述监控请求的第一监控信息；
将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；
接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息；
根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
本申请的第三方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个计算机可读指令，所述至少一个计算机可读指令被处理器执行时实现以下步骤：
接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型；
根据所述收集类型获得所述监控请求的第一监控信息；
将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；
接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息；
根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
本申请的第四方面提供一种基于云环境的系统信息分析装置，运行于第一服务器中，所述装置包括：
接收模块，用于接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型；
获得模块，用于根据所述收集类型获得所述监控请求的第一监控信息；
发送模块，用于将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；
处理模块，用于接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息；
分析模块，用于根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
综上所述，本申请所述的基于云环境的系统信息分析方法、装置、电子设备及介质，一方面，通过分析不同维度的第三监控信息得到每个第二服务器的分析结果，提高了监控后的分析结果的准确率；另一方面，通过采用消息队列的方式传输的所述监控请求的第二监控信息可以避免过多的第二监控信息累计导致第二监控信息传输缓慢，提高第二监控信息的传输效率及正确率；最后，通过根据不同的收集类型确定不同的第一监控信息的获取方式，所述收集类型可以根据不同的场景进行部署，既可以根据第二服务器的硬件设备配置情况或者不同的业务场景进行部分信息收集或者全部信息收集，提高了监控的效率及多样性，进而提高了监控分析结果的准确率。
图1是本申请公开的一种基于云环境的系统信息分析方法的较佳实施例的流程图。
图2是本申请公开的一种基于云环境的系统信息分析装置的较佳实施例的功能模块图。
图3是本申请实现基于云环境的系统信息分析方法的较佳实施例的电子设备的结构示意图。
为了能够更清楚地理解本申请的上述目的、特征和优点，下面结合附图和具体实施例对本申请进行详细描述。需要说明的是，在不冲突的情况下，本申请的实施例及实施例中的特征可以相互组合。
除非另有定义，本文所使用的所有的技术和科学术语与属于本申请的技术领域的技术人员通常理解的含义相同。本文中在本申请的说明书中所使用的术语只是为了描述具体的实施例的目的，不是旨在于限制本申请。
实施例一
图1是本申请实施例一提供的基于云环境的系统信息分析方法的流程图。
在本实施例中，所述基于云环境的系统信息分析方法可以应用于电子设备中，对于需要进行基于云环境的系统信息分析的电子设备，可以直接在电子设备上集成本申请的方法所提供的基于云环境的系统信息分析的功能，或者以软件开发工具包(Software Development Kit，SKD)的形式运行在电子设备中。
如图1所示，所述基于云环境的系统信息分析方法具体包括以下步骤，根据不同的需求，该流程图中步骤的顺序可以改变，某些可以省略。
本申请所述的基于云环境的系统信息分析方法可应用于第一服务器中，其中，所述第一服务器与多个第二服务器连接，所述第一服务器可以为监控平台，用于监控云环境中与所述第一服务器通信连接的所有第二服务器的运行状态，具体地，所述第一服务器用于监控每台第二服务器中的应用程序的运行状态，其中，每台第二服务器可以同时运行多个应用程序，并且运行每个应用程序时发送对应的监控请求至所述第一服务器，所述第一服务器根据所述第二服务器的应用程序发送的监控请求执行监控。
S11，接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型。
本实施例中，在云环境下，所述第一服务器需要监控多个第二服务器发送的多个监控请求，具体地，所述监控请求用于监控每个第二服务器中的不同的应用程序的运行情况，每个第二服务器上可以运行多个应用程序，针对每个应用程序发送一个监控请求。
本实施例中，所述收集类型用于确定所述监控请求具体收集的第一监控信息，具体地，所述第一监控信息包括，但不限于，所述监控请求对应的请求接口名称、请求时间、请求用户、请求服务应用名称、请求参数、请求结果、请求运行时间、请求交互系统、请求频次。
可选地，所述解析所述监控请求得到收集类型包括：
识别所述监控请求中是否存在收集信息标识；
当所述监控请求中存在收集信息标识时，确定所述监控请求的收集类型为部分信息收集类型；
当所述监控请求中不存在收集信息标识时，确定所述监控请求的收集类型为全量信息收集类型。
本实施例中，所述收集信息标识用来唯一识别所述监控请求在进行监控时收集的第一监控信息的类型，通过判断所述监控请求中是否存在收集信息标识确定收集类型，若所述监控请求中存在收集信息标识时，确定为部分信息收集类型，即只收集监控到的收集信息标识对应的第一监控信息；若所述监控请求中不存在收集信息标识时，确定为全量信息收集类型，即收集所有监控到的第一监控信息。
S12，根据所述收集类型获得所述监控请求的第一监控信息。
本实施例中，不同的收集类型表示不同的第一监控信息的获取的方式不同。
可选地，所述根据所述收集类型获得所述监控请求的第一监控信息包括：
当确定所述监控请求的收集类型为部分信息收集类型时，识别所述监控请求中的每个收集信息标识，根据所述每个收集信息标识进行信息收集获得第一监控信息；
当确定所述监控请求的收集类型为全量信息收集类型时，按照预设的收集规则进行全部信息收集得到第一监控信息。
本实施例中，所述收集信息标识用于表示收集的对应的第一监控信息，根据所述收集信息标识可以获得所述监控请求对应的第一监控信息。
本实施例中，通过根据不同的收集类型确定不同的第一监控信息的获取方式，所述收集类型可以根据不同的场景进行部署，例如，既可以根据第二服务器的硬件设备配置情况或者不同的业务场景进行部分信息收集或者全部信息收集，提高了监控的效率及多样性。
S13，将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中。
本实施例中，所述监控标识表示第二服务器请求监控的监控类型，不同的监控类型对应不同的监控标识，具体地，所述监控类型包括，但不限于查询、更新、交互和自定义。
可选地，所述将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中包括：
识别所述监控请求的监控标识对应的监控类型；
将所述监控请求的第一监控信息发送至所述监控类型对应的消息队列中。
本实施例中，每个监控类型对应监控信息基本相同，将相同的监控类型的第一监控信息存储至同一个消息队列中，对所述第一监控信息进行归类并保留，直至所述监控请求监控完成，避免第一监控信息丢失的现象，提高了第一监控信息的完整性。
进一步地，在所述将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中之前，所述方法还包括：
监测所述监控请求的第一监控信息的收集时间；
判断所述第一监控信息的收集时间是否大于预设的收集时间阈值；
当所述第一监控信息的收集时间小于或者等于所述预设的收集时间阈值时，将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；
当所述第一监控信息的收集时间大于所述预设的收集时间阈值时，停止收集所述第一监控信息，并启动新的线程进行所述第一监控信息的收集。
本实施例中，当所述监控请求的第一监控信息的收集时间大于或者等于所述预设的收集时间阈值时，确定监控出现异常，需要启动新的线程进行补偿机制，具体地，所述补偿机制可以为异步发送或者本地存储，通过所述补偿机制可以在监控恢复正常后进行手动补偿，进行所述第一监控信息的收集。
本实施例中，所述预设的信息收集时间阈值可以预先设置，例如，可以预先设置为30秒或者1分钟。
S14，接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息。
本实施例中，通过在消息队列将所述监控请求的第一监控信息进行整理分类得到第二监控信息，然后将所述第二监控信息通过所述消息队列进行信息传输，具体地，所述消息队列中存储有同一种监控类型对应的第一监控信息，所述第一服务器可以从所述消息队列中获取对所述第一监控信息进行整理分类后的第二监控信息，并且所述消息队列可以将所述监控请求的第二监控信息进行保存，直至所述监控请求的监控完成或者在所述消息队列中存储的时间超过预设的存储时间阈值，删除所述监控请求对应的第二监控信息，提高了第二监控信息的正确性和完整性。
本实施例中，通过采用消息队列的方式传输的所述监控请求的第二监控信息可以避免过多的第二监控信息累计导致第二监控信息传输缓慢，提高监控信息的传输效率及正确率。
可选地，所述对所述监控请求的第二监控信息进行处理得到第三监控信息包括：
将所述监控请求的第二监控信息发送至第三方搜索引擎；
接收所述第三方搜索引擎发送的根据所述第二监控信息生成的结构化数据；
将所述结构化数据作为第三监控信息。
本实施例中，所述第三方搜索引擎可以为ES(ElasticSearch：分散式搜索引擎)，具体地，所述分散式搜索引擎对所述监控请求的第二监控信息进行处理，其中，所述处理过程包括将所述第二监控信息转换成结构化数据，其中，所述结构化数据可以根据每个监控类型对应的历史监控信息进行预先设置。
本实施例中，在将所述监控请求的第二监控信息发送至第三方搜索引擎之后，在所述第三方搜索引擎中将所述监控信息转换成结构化数据，具体地，首先从所述第二监控信息中提取多个关键字段，将每个关键字段按照预设的格式转换成结构化数据。
示例性的，所述消息队列传输的第二监控信息中的请求时间为：1998/09/06，将所述 请求时间按照预设的格式转换成结构化数据：1998-09-06。
S15，根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
本实施例中，在得到所述监控请求的第三监控信息时，根据所述监控请求的设备标识得到所述第二服务器上运行的多个应用程序对应的第三监控信息，由于不同的第三监控信息是从不同的维度得到的，通过分析不同维度的第三监控信息得到所述第二服务器的分析结果，提高了监控后的分析结果的准确率。
在其他一些实施例中，所述第一服务器与多个第二服务器连接，所述多个第二服务器可以同时向所述第一服务器发送监控请求，每个第二服务器可以同时发送多个监控请求，具体地，当所述第一服务器接收到多个监控请求时，可能会出现运行缓慢的现象，为了避免运行缓慢的现象，根据接收到的监控请求的总量采用不同的方式进行系统信息分析。
可替代地，所述方法还包括：
计算接收到所述监控请求的总量；
判断所述总量是否大于预设总量阈值；
当所述总量大于或者等于所述预设总量阈值时，获取每个第二服务器发送的每个监控请求的第一监控信息，将所述每个监控请求的第一监控信息进行处理得到对应的第三监控信息，根据所述第三监控信息和所述设备标识进行分析得到每个第二服务器的分析结果。
示例性的，第二服务器M发送的多个监控请求为：监控A、B和C应用程序耗费的流量，监控请求的总量等于预设总量阈值3，通过对所述A、B和C应用程序耗费的流量的监控得到的第一监控信息分别进行处理，得到所述第二服务器发送的所述监控请求的为：A应用程序耗费流量20G；B应用程序耗费流量5G，C应用程序耗费流量8G，获取所述第二服务器M的设备标识为Q，所述Q对应的预定流量为100G，根据所述的和设备标识进行分析，得到所述第二服务器M的分析结果为：耗费总流量为33G，未超过100G，所述第二服务器M运行正常。
本实施例中，当所述总量小于所述预设总量阈值时，解析至少一个第二服务器发送的每个监控请求得到每个监控请求的监控标识、设备标识及收集类型；根据所述每个监控请求的收集类型获得所述每个监控请求的第一监控信息；将所述每个监控请求的第一监控信息发送至对应所述监控标识的消息队列中；接收所述消息队列传输的所述每个监控请求的第二监控信息，并对所述每个监控请求的第二监控信息进行处理得到第三监控信息；根据所述第三监控信息和所述设备标识进行分析得到所述至少一个第二服务器的分析结果。
本实施例中，监控请求的总量阈值是根据已收集的监控信息的占用服务器的资源的比例进行预先设置的，当所述监控请求的总量大于或者等于所述预设总量阈值时，确定已收集的监控信息的资源占用比例超过了服务器的运行要求，为了避免监控效率降低，监控信息不需要进行分类收集，直接发送第一监控信息至第三方搜索引擎进行处理得到第三监控信息，保证了监控效率。
进一步地，在得到每个第二服务器的分析结果之后，所述方法还包括：
按照预设的展示方式展示所述分析结果至监控界面。
本实施例中，展示方式可以根据维护人员的偏好进行预先设置，所述分析结果可以包括，但不限于，每个服务器已用的流量，每个应用程序更新数据、交互数据、访问频次，通过按照预设的展示方式展示所述分析结果监控界面，可以辅助维护人员快速的确定每个应用程序的运行情况，提高了监控效率。
在其他一些实施例中，若所述监控界面中显示异常数据时，触发报警，及时的提醒 维护人员监控出险异常，所述维护人员可以根据所述监控界面中显示的数据快速的定位出异常数据所在位置进行监控维护，降低了维护成本，提高了维护的及时性。
示例性的，第二服务器发送的监控请求为查询服务器已用的流量，若得到的分析结果为所述第二服务器已用的流量超过了所述第二服务器的预定流量时，对超过的流量进行计费，并将已用流量、超过流量及计费展示在监控界面，同时将所述分析结果发送至所述第二服务器；第二服务器发送的监控请求为交互时，若得到的分析结果为所述第二服务器发送的交互频次超过了所述第二服务器的预设交互频次时，关闭所述第二服务器的交互操作。
本实施例中，通过在监控界面展示分析结果，可以辅助维护人员监控每个第二服务器的运行情况，在监控出现异常时，及时的根据监控界面中显示的数据进行维护，提高了维护的及时性及监控效率。
综上所述，本实施例所述的基于云环境的系统信息分析方法，通过接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型；根据所述收集类型获得所述监控请求的第一监控信息；将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息；根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
本实施例，一方面，通过分析不同维度的第三监控信息得到每个第二服务器的分析结果，提高了监控后的分析结果的准确率；另一方面，通过采用消息队列的方式传输的所述监控请求的第二监控信息可以避免过多的第二监控信息累计导致第二监控信息传输缓慢，提高第二监控信息的传输效率及正确率；最后，通过根据不同的收集类型确定不同的第一监控信息的获取方式，所述收集类型可以根据不同的场景进行部署，既可以根据第二服务器的硬件设备配置情况或者不同的业务场景进行部分信息收集或者全部信息收集，提高了监控的效率及多样性，进而提高了监控分析结果的准确率。
此外，通过在监控界面展示分析结果，可以辅助维护人员监控每个第二服务器的运行情况，在监控出现异常时，及时的根据监控界面中显示的数据进行维护，提高了维护的及时性及监控效率。
实施例二
图2是本申请实施例二提供的基于云环境的系统信息分析装置的结构图。
在一些实施例中，所述基于云环境的系统信息分析装置20可以包括多个由程序代码段所组成的功能模块。所述基于云环境的系统信息分析装置20中的各个程序段的程序代码可以存储于电子设备的存储器中，并由所述至少一个处理器所执行，以执行(详见图1描述)基于云环境的系统信息分析的功能。
本实施例中，所述基于云环境的系统信息分析装置20，运行于第一服务器中，根据其所执行的功能，可以被划分为多个功能模块。所述功能模块可以包括：接收模块201、获得模块202、发送模块203、处理模块204、分析模块205、计算模块206及判断模块207。本申请所称的模块是指一种能够被至少一个处理器所执行并且能够完成固定功能的一系列计算机可读指令段，其存储在存储器中。在本实施例中，关于各模块的功能将在后续的实施例中详述。
本实施例所述的基于云环境的系统信息分析装置，可运行于第一服务器中，其中，所述第一服务器与多个第二服务器连接，所述第一服务器可以为监控平台，用于监控云环境中与所述第一服务器通信连接的所有第二服务器的运行状态，具体地，所述第一服务器用于监控每台第二服务器中的应用程序的运行状态，其中，每台第二服务器可以同时运行多个应用程序，并且运行每个应用程序时发送对应的监控请求至所述第一服务器，所述第一服务器根据所述第二服务器的应用程序发送的监控请求执行监控。
接收模块201，用于接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型。
本实施例中，在云环境下，所述第一服务器需要监控多个第二服务器发送的多个监控请求，具体地，所述监控请求用于监控每个第二服务器中的不同的应用程序的运行情况，每个第二服务器上可以运行多个应用程序，针对每个应用程序发送一个监控请求。
本实施例中，所述收集类型用于确定所述监控请求具体收集的第一监控信息，具体地，所述第一监控信息包括，但不限于，所述监控请求对应的请求接口名称、请求时间、请求用户、请求服务应用名称、请求参数、请求结果、请求运行时间、请求交互系统、请求频次。
可选地，所述接收模块201解析所述监控请求得到收集类型包括：
识别所述监控请求中是否存在收集信息标识；
当所述监控请求中存在收集信息标识时，确定所述监控请求的收集类型为部分信息收集类型；
当所述监控请求中不存在收集信息标识时，确定所述监控请求的收集类型为全量信息收集类型。
本实施例中，所述收集信息标识用来唯一识别所述监控请求在进行监控时收集的第一监控信息的类型，通过判断所述监控请求中是否存在收集信息标识确定收集类型，若所述监控请求中存在收集信息标识时，确定为部分信息收集类型，即只收集监控到的收集信息标识对应的第一监控信息；若所述监控请求中不存在收集信息标识时，确定为全量信息收集类型，即收集所有监控到的第一监控信息。
获得模块202，用于根据所述收集类型获得所述监控请求的第一监控信息。
本实施例中，不同的收集类型表示不同的第一监控信息的获取的方式不同。
可选地，所述获得模块202根据所述收集类型获得所述监控请求的第一监控信息包括：
当确定所述监控请求的收集类型为部分信息收集类型时，识别所述监控请求中的每个收集信息标识，根据所述每个收集信息标识进行信息收集获得第一监控信息；
当确定所述监控请求的收集类型为全量信息收集类型时，按照预设的收集规则进行全部信息收集得到第一监控信息。
本实施例中，所述收集信息标识用于表示收集的对应的第一监控信息，根据所述收集信息标识可以获得所述监控请求对应的第一监控信息。
本实施例中，通过根据不同的收集类型确定不同的第一监控信息的获取方式，所述收集类型可以根据不同的场景进行部署，例如，既可以根据第二服务器的硬件设备配置情况或者不同的业务场景进行部分信息收集或者全部信息收集，提高了监控的效率及多样性。
发送模块203，用于将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中。
本实施例中，所述监控标识表示第二服务器请求监控的监控类型，不同的监控类型对应不同的监控标识，具体地，所述监控类型包括，但不限于查询、更新、交互和自定义。
可选地，所述发送模块203将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中包括：
识别所述监控请求的监控标识对应的监控类型；
将所述监控请求的第一监控信息发送至所述监控类型对应的消息队列中。
本实施例中，每个监控类型对应监控信息基本相同，将相同的监控类型的第一监控信息存储至同一个消息队列中，对所述第一监控信息进行归类并保留，直至所述监控请 求监控完成，避免第一监控信息丢失的现象，提高了第一监控信息的完整性。
进一步地，在所述发送模块203将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中之前，监测所述监控请求的第一监控信息的收集时间；判断所述第一监控信息的收集时间是否大于预设的收集时间阈值；当所述第一监控信息的收集时间小于或者等于所述预设的收集时间阈值时，将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；当所述第一监控信息的收集时间大于所述预设的收集时间阈值时，停止收集所述第一监控信息，并启动新的线程进行所述第一监控信息的收集。
本实施例中，当所述监控请求的第一监控信息的收集时间大于或者等于所述预设的收集时间阈值时，确定监控出现异常，需要启动新的线程进行补偿机制，具体地，所述补偿机制可以为异步发送或者本地存储，通过所述补偿机制可以在监控恢复正常后进行手动补偿，进行所述第一监控信息的收集。
本实施例中，所述预设的信息收集时间阈值可以预先设置，例如，可以预先设置为30秒或者1分钟。
处理模块204，用于接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息。
本实施例中，通过在消息队列将所述监控请求的第一监控信息进行整理分类得到第二监控信息，然后将所述第二监控信息通过所述消息队列进行信息传输，具体地，所述消息队列中存储有同一种监控类型对应的第一监控信息，所述第一服务器可以从所述消息队列中获取对所述第一监控信息进行整理分类后的第二监控信息，并且所述消息队列可以将所述监控请求的第二监控信息进行保存，直至所述监控请求的监控完成或者在所述消息队列中存储的时间超过预设的存储时间阈值，删除所述监控请求对应的第二监控信息，提高了第二监控信息的正确性和完整性。
本实施例中，通过采用消息队列的方式传输的所述监控请求的第二监控信息可以避免过多的第二监控信息累计导致第二监控信息传输缓慢，提高监控信息的传输效率及正确率。
可选地，所述处理模块204对所述监控请求的第二监控信息进行处理得到第三监控信息包括：
将所述监控请求的第二监控信息发送至第三方搜索引擎；
接收所述第三方搜索引擎发送的根据所述第二监控信息生成的结构化数据；
将所述结构化数据作为第三监控信息。
本实施例中，所述第三方搜索引擎可以为ES(ElasticSearch：分散式搜索引擎)，具体地，所述分散式搜索引擎对所述监控请求的第二监控信息进行处理，其中，所述处理过程包括将所述第二监控信息转换成结构化数据，其中，所述结构化数据可以根据每个监控类型对应的历史监控信息进行预先设置。
本实施例中，在将所述监控请求的第二监控信息发送至第三方搜索引擎之后，在所述第三方搜索引擎中将所述监控信息转换成结构化数据，具体地，首先从所述第二监控信息中提取多个关键字段，将每个关键字段按照预设的格式转换成结构化数据。
示例性的，所述消息队列传输的第二监控信息中的请求时间为：1998/09/06，将所述请求时间按照预设的格式转换成结构化数据：1998-09-06。
分析模块205，用于根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
本实施例中，在得到所述监控请求的第三监控信息时，根据所述监控请求的设备标识得到所述第二服务器上运行的多个应用程序对应的第三监控信息，由于不同的第三监控信息是从不同的维度得到的，通过分析不同维度的第三监控信息得到所述第二服务器的分析结果，提高了监控后的分析结果的准确率。
在其他一些实施例中，所述第一服务器与多个第二服务器连接，所述多个第二服务器可以同时向所述第一服务器发送监控请求，每个第二服务器可以同时发送多个监控请求，具体地，当所述第一服务器接收到多个监控请求时，可能会出现运行缓慢的现象，为了避免运行缓慢的现象，根据接收到的监控请求的总量采用不同的方式进行系统信息分析。
可替代地，计算模块206，用于计算接收到所述监控请求的总量。
判断模块207，用于判断所述总量是否大于预设总量阈值；当所述总量大于或者等于所述预设总量阈值时，获取每个第二服务器发送的每个监控请求的第一监控信息，将所述每个监控请求的第一监控信息进行处理得到对应的第三监控信息，根据所述第三监控信息和所述设备标识进行分析得到每个第二服务器的分析结果。
示例性的，第二服务器M发送的多个监控请求为：监控A、B和C应用程序耗费的流量，监控请求的总量等于预设总量阈值3，通过对所述A、B和C应用程序耗费的流量的监控得到的第一监控信息分别进行处理，得到所述第二服务器发送的所述监控请求的为：A应用程序耗费流量20G；B应用程序耗费流量5G，C应用程序耗费流量8G，获取所述第二服务器M的设备标识为Q，所述Q对应的预定流量为100G，根据所述的和设备标识进行分析，得到所述第二服务器M的分析结果为：耗费总流量为33G，未超过100G，所述第二服务器M运行正常。
本实施例中，当所述总量小于所述预设总量阈值时，解析至少一个第二服务器发送的每个监控请求得到每个监控请求的监控标识、设备标识及收集类型；根据所述每个监控请求的收集类型获得所述每个监控请求的第一监控信息；将所述每个监控请求的第一监控信息发送至对应所述监控标识的消息队列中；接收所述消息队列传输的所述每个监控请求的第二监控信息，并对所述每个监控请求的第二监控信息进行处理得到第三监控信息；根据所述第三监控信息和所述设备标识进行分析得到所述至少一个第二服务器的分析结果。
本实施例中，监控请求的总量阈值是根据已收集的监控信息的占用服务器的资源的比例进行预先设置的，当所述监控请求的总量大于或者等于所述预设总量阈值时，确定已收集的监控信息的资源占用比例超过了服务器的运行要求，为了避免监控效率降低，监控信息不需要进行分类收集，直接发送第一监控信息至第三方搜索引擎进行处理得到第三监控信息，保证了监控效率。
进一步地，在得到每个第二服务器的分析结果之后，按照预设的展示方式展示所述分析结果至监控界面。
本实施例中，展示方式可以根据维护人员的偏好进行预先设置，所述分析结果可以包括，但不限于，每个服务器已用的流量，每个应用程序更新数据、交互数据、访问频次，通过按照预设的展示方式展示所述分析结果监控界面，可以辅助维护人员快速的确定每个应用程序的运行情况，提高了监控效率。
在其他一些实施例中，若所述监控界面中显示异常数据时，触发报警，及时的提醒维护人员监控出险异常，所述维护人员可以根据所述监控界面中显示的数据快速的定位出异常数据所在位置进行监控维护，降低了维护成本，提高了维护的及时性。
示例性的，第二服务器发送的监控请求为查询服务器已用的流量，若得到的分析结果为所述第二服务器已用的流量超过了所述第二服务器的预定流量时，对超过的流量进行计费，并将已用流量、超过流量及计费展示在监控界面，同时将所述分析结果发送至所述第二服务器；第二服务器发送的监控请求为交互时，若得到的分析结果为所述第二服务器发送的交互频次超过了所述第二服务器的预设交互频次时，关闭所述第二服务器的交互操作。
本实施例中，通过在监控界面展示分析结果，可以辅助维护人员监控每个第二服务 器的运行情况，在监控出现异常时，及时的根据监控界面中显示的数据进行维护，提高了维护的及时性及监控效率。
综上所述，本实施例所述的基于云环境的系统信息分析装置，通过接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型；根据所述收集类型获得所述监控请求的第一监控信息；将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息；根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
本实施例，一方面，通过分析不同维度的第三监控信息得到每个第二服务器的分析结果，提高了监控后的分析结果的准确率；另一方面，通过采用消息队列的方式传输的所述监控请求的第二监控信息可以避免过多的第二监控信息累计导致第二监控信息传输缓慢，提高第二监控信息的传输效率及正确率；最后，通过根据不同的收集类型确定不同的第一监控信息的获取方式，所述收集类型可以根据不同的场景进行部署，既可以根据第二服务器的硬件设备配置情况或者不同的业务场景进行部分信息收集或者全部信息收集，提高了监控的效率及多样性，进而提高了监控分析结果的准确率。
此外，通过在监控界面展示分析结果，可以辅助维护人员监控每个第二服务器的运行情况，在监控出现异常时，及时的根据监控界面中显示的数据进行维护，提高了维护的及时性及监控效率。
实施例三
参阅图3所示，为本申请实施例三提供的电子设备的结构示意图。在本申请较佳实施例中，所述电子设备3包括存储器31、至少一个处理器32、至少一条通信总线33及收发器34。
本领域技术人员应该了解，图3示出的电子设备的结构并不构成本申请实施例的限定，既可以是总线型结构，也可以是星形结构，所述电子设备3还可以包括比图示更多或更少的其他硬件或者软件，或者不同的部件布置。
在一些实施例中，所述电子设备3是一种能够按照事先设定或存储的指令，自动进行数值计算和/或信息处理的电子设备，其硬件包括但不限于微处理器、专用集成电路、可编程门阵列、数字处理器及嵌入式设备等。所述电子设备3还可包括客户设备，所述客户设备包括但不限于任何一种可与客户通过键盘、鼠标、遥控器、触摸板或声控设备等方式进行人机交互的电子产品，例如，个人计算机、平板电脑、智能手机、数码相机等。
需要说明的是，所述电子设备3仅为举例，其他现有的或今后可能出现的电子产品如可适应于本申请，也应包含在本申请的保护范围以内，并以引用方式包含于此。
在一些实施例中，所述存储器31用于存储程序代码和各种数据，例如安装在所述电子设备3中的基于云环境的系统信息分析装置20，并在电子设备3的运行过程中实现高速、自动地完成程序或数据的存取。所述存储器31包括只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable Read-Only Memory，PROM)、可擦除可编程只读存储器(Erasable Programmable Read-Only Memory，EPROM)、一次可编程只读存储器(One-time Programmable Read-Only Memory，OTPROM)、电子擦除式可复写只读存储器(Electrically-Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储器、磁盘存储器、磁带存储器、或者能够用于携带或存储数据的计算机可读的任何其他介质。
在一些实施例中，所述至少一个处理器32可以由集成电路组成，例如可以由单个封装的集成电路所组成，也可以是由多个相同功能或不同功能封装的集成电路所组成，包括一个或者多个中央处理器(Central Processing unit，CPU)、微处理器、数字处理芯 片、图形处理器及各种控制芯片的组合等。所述至少一个处理器32是所述电子设备3的控制核心(Control Unit)，利用各种接口和线路连接整个电子设备3的各个部件，通过运行或执行存储在所述存储器31内的程序或者模块，以及调用存储在所述存储器31内的数据，以执行电子设备3的各种功能和处理数据。
在一些实施例中，所述至少一条通信总线33被设置为实现所述存储器31以及所述至少一个处理器32等之间的连接通信。
尽管未示出，所述电子设备3还可以包括给各个部件供电的电源(比如电池)，可选地，电源可以通过电源管理装置与所述至少一个处理器32逻辑相连，从而通过电源管理装置实现管理充电、放电、以及功耗管理等功能。电源还可以包括一个或一个以上的直流或交流电源、再充电装置、电源故障检测电路、电源转换器或者逆变器、电源状态指示器等任意组件。所述电子设备3还可以包括多种传感器、蓝牙模块、Wi-Fi模块等，在此不再赘述。
应该了解，所述实施例仅为说明之用，在专利申请范围上并不受此结构的限制。
上述以软件功能模块的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能模块存储在一个存储介质中，包括若干计算机可读指令用以使得一台计算机设备(可以是个人计算机，电子设备，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的部分。
在进一步的实施例中，结合图2，所述至少一个处理器32可执行所述电子设备3的操作装置以及安装的各类应用程序(如所述的基于云环境的系统信息分析装置20)、程序代码等，例如，上述的各个模块。
所述存储器31中存储有程序代码，且所述至少一个处理器32可调用所述存储器31中存储的程序代码以执行相关的功能。例如，图2中所述的各个模块是存储在所述存储器31中的程序代码，并由所述至少一个处理器32所执行，从而实现所述各个模块的功能以达到基于云环境的系统信息分析的目的。
示例性的，所述计算机程序可以被分割成一个或多个模块/单元，所述一个或者多个模块/单元被存储在所述存储器31中，并由所述处理器32执行，以完成本申请。所述一个或多个模块/单元可以是能够完成特定功能的一系列计算机可读指令段，该指令段用于描述所述计算机程序在所述电子设备3中的执行过程。例如，所述计算机程序可以被分割成接收模块201、获得模块202、发送模块203、处理模块204、分析模块205、计算模块206及判断模块207。
在本申请的一个实施例中，所述存储器31存储多个计算机可读指令，所述多个计算机可读指令被所述至少一个处理器32所执行以实现基于云环境的系统信息分析的功能。
进一步地，所述计算机可读存储介质可以是非易失性，也可以是易失性。
具体地，所述至少一个处理器32对上述指令的具体实现方法可参考图1对应实施例中相关步骤的描述，在此不赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理单元，既可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能模块可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单 元既可以采用硬件的形式实现，也可以采用硬件加软件功能模块的形式实现。
对于本领域技术人员而言，显然本申请不限于上述示范性实施例的细节，而且在不背离本申请的精神或基本特征的情况下，能够以其他的具体形式实现本申请。因此，无论从哪一点来看，均应将实施例看作是示范性的，而且是非限制性的，本申请的范围由所附权利要求而不是上述说明限定，因此旨在将落在权利要求的等同要件的含义和范围内的所有变化涵括在本申请内。不应将权利要求中的任何附图标记视为限制所涉及的权利要求。此外，显然“包括”一词不排除其他单元或，单数不排除复数。说明书中陈述的多个单元或装置也可以由一个单元或装置通过软件或者硬件来实现。第一，第二等词语用来表示名称，而并不表示任何特定的顺序。
最后应说明的是，以上实施例仅用以说明本申请的技术方案而非限制，尽管参照较佳实施例对本申请进行了详细说明，本领域的普通技术人员应当理解，可以对本申请的技术方案进行修改或等同替换，而不脱离本申请技术方案的精神和范围。
Claims (20)
- 一种基于云环境的系统信息分析方法，应用于第一服务器中，其中，所述基于云环境的系统信息分析方法包括：接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型；根据所述收集类型获得所述监控请求的第一监控信息；将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息；根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
- 如权利要求1所述的基于云环境的系统信息分析方法，其中，所述对所述监控请求的第二监控信息进行处理得到第三监控信息包括：将所述监控请求的第二监控信息发送至第三方搜索引擎；接收所述第三方搜索引擎发送的根据所述第二监控信息生成的结构化数据；将所述结构化数据作为第三监控信息。
- 如权利要求2所述的基于云环境的系统信息分析方法，其中，在所述将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中之前，所述方法还包括：监测所述监控请求的第一监控信息的收集时间；判断所述第一监控信息的收集时间是否大于预设的收集时间阈值；当所述第一监控信息的收集时间小于或者等于所述预设的收集时间阈值时，将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；当所述第一监控信息的收集时间大于所述预设的收集时间阈值时，停止收集所述第一监控信息，并启动新的线程进行所述第一监控信息的收集。
- 如权利要求1所述的基于云环境的系统信息分析方法，其中，所述解析所述监控请求得到收集类型包括：识别所述监控请求中是否存在收集信息标识；当所述监控请求中存在收集信息标识时，确定所述监控请求的收集类型为部分信息收集类型；当所述监控请求中不存在收集信息标识时，确定所述监控请求的收集类型为全量信息收集类型。
- 如权利要求4所述的基于云环境的系统信息分析方法，其中，所述根据所述收集类型获得所述监控请求的第一监控信息包括：当确定所述监控请求的收集类型为部分信息收集类型时，识别所述监控请求中的每个收集信息标识，根据所述每个收集信息标识进行信息收集获得第一监控信息；当确定所述监控请求的收集类型为全量信息收集类型时，按照预设的收集规则进行全部信息收集得到第一监控信息。
- 如权利要求1所述的基于云环境的系统信息分析方法，其中，所述将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中包括：识别所述监控请求的监控标识对应的监控类型；将所述监控请求的第一监控信息发送至所述监控类型对应的消息队列中。
- 如权利要求1所述的基于云环境的系统信息分析方法，其中，所述方法还包括：计算接收到所述监控请求的总量；判断所述总量是否大于预设总量阈值；当所述总量大于或者等于所述预设总量阈值时，获取每个第二服务器发送的每个监控请 求的第一监控信息，将所述每个监控请求的第一监控信息进行处理得到对应的第三监控信息，根据所述第三监控信息和所述设备标识进行分析得到每个第二服务器的分析结果。
- 一种电子设备，其中，所述电子设备包括存储器及处理器，所述存储器用于存储至少一个计算机可读指令，所述处理器用于执行所述至少一个计算机可读指令以实现以下步骤：接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型；根据所述收集类型获得所述监控请求的第一监控信息；将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息；根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
- 如权利要求8所述的电子设备，其中，所述处理器执行所述至少一个计算机可读指令以实现所述对所述监控请求的第二监控信息进行处理得到第三监控信息时，具体包括：将所述监控请求的第二监控信息发送至第三方搜索引擎；接收所述第三方搜索引擎发送的根据所述第二监控信息生成的结构化数据；将所述结构化数据作为第三监控信息。
- 如权利要求9所述的电子设备，其中，在所述将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中之前，所述处理器执行所述至少一个计算机可读指令还用以实现以下步骤：监测所述监控请求的第一监控信息的收集时间；判断所述第一监控信息的收集时间是否大于预设的收集时间阈值；当所述第一监控信息的收集时间小于或者等于所述预设的收集时间阈值时，将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；当所述第一监控信息的收集时间大于所述预设的收集时间阈值时，停止收集所述第一监控信息，并启动新的线程进行所述第一监控信息的收集。
- 如权利要求8所述的电子设备，其中，所述处理器执行所述至少一个计算机可读指令以实现所述解析所述监控请求得到收集类型时，具体包括：识别所述监控请求中是否存在收集信息标识；当所述监控请求中存在收集信息标识时，确定所述监控请求的收集类型为部分信息收集类型；当所述监控请求中不存在收集信息标识时，确定所述监控请求的收集类型为全量信息收集类型。
- 如权利要求11所述的电子设备，其中，所述处理器执行所述至少一个计算机可读指令以实现所述根据所述收集类型获得所述监控请求的第一监控信息时，具体包括：当确定所述监控请求的收集类型为部分信息收集类型时，识别所述监控请求中的每个收集信息标识，根据所述每个收集信息标识进行信息收集获得第一监控信息；当确定所述监控请求的收集类型为全量信息收集类型时，按照预设的收集规则进行全部信息收集得到第一监控信息。
- 如权利要求8所述的电子设备，其中，所述处理器执行所述至少一个计算机可读指令以实现所述将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中时，具体包括：识别所述监控请求的监控标识对应的监控类型；将所述监控请求的第一监控信息发送至所述监控类型对应的消息队列中。
- 一种计算机可读存储介质，其中，所述计算机可读存储介质存储有至少一个计算机可读指令，所述至少一个计算机可读指令被处理器执行时实现以下步骤：接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、设备标识及收集类型；根据所述收集类型获得所述监控请求的第一监控信息；将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息；根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
- 如权利要求14所述的存储介质，其中，所述至少一个计算机可读指令被所述处理器执行以实现所述对所述监控请求的第二监控信息进行处理得到第三监控信息时，具体包括：将所述监控请求的第二监控信息发送至第三方搜索引擎；接收所述第三方搜索引擎发送的根据所述第二监控信息生成的结构化数据；将所述结构化数据作为第三监控信息。
- 如权利要求15所述的存储介质，其中，在所述将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中之前，所述至少一个计算机可读指令被处理器执行时还用以实现以下步骤：监测所述监控请求的第一监控信息的收集时间；判断所述第一监控信息的收集时间是否大于预设的收集时间阈值；当所述第一监控信息的收集时间小于或者等于所述预设的收集时间阈值时，将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；当所述第一监控信息的收集时间大于所述预设的收集时间阈值时，停止收集所述第一监控信息，并启动新的线程进行所述第一监控信息的收集。
- 如权利要求14所述的存储介质，其中，所述至少一个计算机可读指令被所述处理器执行以实现所述解析所述监控请求得到收集类型时，具体包括：识别所述监控请求中是否存在收集信息标识；当所述监控请求中存在收集信息标识时，确定所述监控请求的收集类型为部分信息收集类型；当所述监控请求中不存在收集信息标识时，确定所述监控请求的收集类型为全量信息收集类型。
- 如权利要求17所述的存储介质，其中，所述至少一个计算机可读指令被所述处理器执行以实现所述根据所述收集类型获得所述监控请求的第一监控信息时，具体包括：当确定所述监控请求的收集类型为部分信息收集类型时，识别所述监控请求中的每个收集信息标识，根据所述每个收集信息标识进行信息收集获得第一监控信息；当确定所述监控请求的收集类型为全量信息收集类型时，按照预设的收集规则进行全部信息收集得到第一监控信息。
- 如权利要求14所述的存储介质，其中，所述至少一个计算机可读指令被所述处理器执行以实现所述将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中时，具体包括：识别所述监控请求的监控标识对应的监控类型；将所述监控请求的第一监控信息发送至所述监控类型对应的消息队列中。
- 一种基于云环境的系统信息分析装置，运行于第一服务器中，其中，所述基于云环境的系统信息分析装置包括：接收模块，用于接收第二服务器发送的监控请求并解析所述监控请求得到监控标识、 设备标识及收集类型；获得模块，用于根据所述收集类型获得所述监控请求的第一监控信息；发送模块，用于将所述监控请求的第一监控信息发送至对应所述监控标识的消息队列中；处理模块，用于接收所述消息队列传输的所述监控请求的第二监控信息，并对所述监控请求的第二监控信息进行处理得到第三监控信息；分析模块，用于根据所述第三监控信息和所述设备标识进行分析得到所述第二服务器的分析结果。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011194028.5 | 2020-10-30 | ||
| CN202011194028.5A CN112286762A (zh) | 2020-10-30 | 2020-10-30 | 基于云环境的系统信息分析方法、装置、电子设备及介质 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2022088803A1 true WO2022088803A1 (zh) | 2022-05-05 |
Family
ID=74352715
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2021/109392 WO2022088803A1 (zh) | 2020-10-30 | 2021-07-29 | 基于云环境的系统信息分析方法、装置、电子设备及介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112286762A (zh) |
| WO (1) | WO2022088803A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116048840A (zh) * | 2022-12-30 | 2023-05-02 | 北京白驹易行科技有限公司 | 一种基于多租户的订单es高速写入方法及系统 |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112286762A (zh) * | 2020-10-30 | 2021-01-29 | 深圳壹账通智能科技有限公司 | 基于云环境的系统信息分析方法、装置、电子设备及介质 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105872055A (zh) * | 2016-03-31 | 2016-08-17 | 浪潮通用软件有限公司 | 网络分布部署计算机系统的在线监控方法及系统 |
| CN109586999A (zh) * | 2018-11-12 | 2019-04-05 | 深圳先进技术研究院 | 一种容器云平台状态监控预警系统、方法及电子设备 |
| CN109660380A (zh) * | 2018-09-28 | 2019-04-19 | 深圳壹账通智能科技有限公司 | 服务器运行状态的监控方法、平台、系统及可读存储介质 |
| US20190294481A1 (en) * | 2018-03-21 | 2019-09-26 | Didi Research America, Llc | Endpoint process state collector |
| CN112286762A (zh) * | 2020-10-30 | 2021-01-29 | 深圳壹账通智能科技有限公司 | 基于云环境的系统信息分析方法、装置、电子设备及介质 |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103024060B (zh) * | 2012-12-20 | 2015-05-13 | 中国科学院深圳先进技术研究院 | 一种开放式云计算大规模集群监控系统及方法 |
| CN109747684B (zh) * | 2018-10-09 | 2020-05-22 | 比亚迪股份有限公司 | 用于轨道交通的综合监控系统、方法及计算机设备 |
| CN109587264A (zh) * | 2018-12-20 | 2019-04-05 | 新华三技术有限公司 | 数据监控方法、装置及云平台服务器 |
| CN110297738A (zh) * | 2019-05-21 | 2019-10-01 | 深圳壹账通智能科技有限公司 | 系统服务的监控方法、装置、设备及存储介质 |
| CN111565135A (zh) * | 2020-04-30 | 2020-08-21 | 吉林省鑫泽网络技术有限公司 | 监控服务器运行的方法、监控服务器和存储介质 |
-
2020
- 2020-10-30 CN CN202011194028.5A patent/CN112286762A/zh active Pending
-
2021
- 2021-07-29 WO PCT/CN2021/109392 patent/WO2022088803A1/zh active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105872055A (zh) * | 2016-03-31 | 2016-08-17 | 浪潮通用软件有限公司 | 网络分布部署计算机系统的在线监控方法及系统 |
| US20190294481A1 (en) * | 2018-03-21 | 2019-09-26 | Didi Research America, Llc | Endpoint process state collector |
| CN109660380A (zh) * | 2018-09-28 | 2019-04-19 | 深圳壹账通智能科技有限公司 | 服务器运行状态的监控方法、平台、系统及可读存储介质 |
| CN109586999A (zh) * | 2018-11-12 | 2019-04-05 | 深圳先进技术研究院 | 一种容器云平台状态监控预警系统、方法及电子设备 |
| CN112286762A (zh) * | 2020-10-30 | 2021-01-29 | 深圳壹账通智能科技有限公司 | 基于云环境的系统信息分析方法、装置、电子设备及介质 |
Non-Patent Citations (1)
| Title |
|---|
| "Thesis Xidian University", 15 February 2021, XIDIAN UNIVERSITY, CN, article WANG FUKAN: "Design and Implementation of the Cloud Monitoring System Based on Zabbix", pages: 1 - 63, XP055925161 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116048840A (zh) * | 2022-12-30 | 2023-05-02 | 北京白驹易行科技有限公司 | 一种基于多租户的订单es高速写入方法及系统 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112286762A (zh) | 2021-01-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112367246B (zh) | 消息推送方法、装置、电子设备及存储介质 | |
| CN105357038B (zh) | 监控虚拟机集群的方法和系统 | |
| WO2022088803A1 (zh) | 基于云环境的系统信息分析方法、装置、电子设备及介质 | |
| CN111475370A (zh) | 基于数据中心的运维监控方法、装置、设备及存储介质 | |
| WO2022142016A1 (zh) | 基于规则引擎的参数转换方法、装置、设备及介质 | |
| US20130198370A1 (en) | Method for visualizing server reliability, computer system, and management server | |
| CN111459782B (zh) | 监控业务系统的方法、装置、云平台系统和服务器 | |
| CN112751726B (zh) | 一种数据处理方法、装置、电子设备和存储介质 | |
| CN112101803A (zh) | 业务流程监控方法、装置、系统、设备和介质 | |
| CN111400189A (zh) | 代码覆盖率监测方法、装置、电子设备及存储介质 | |
| CN113094674A (zh) | 页面展示方法、装置、电子设备及存储介质 | |
| CN111754123A (zh) | 数据监控方法、装置、计算机设备及存储介质 | |
| CN110635956A (zh) | 一种设备管理方法、平台、系统、设备及存储介质 | |
| CN117370053A (zh) | 一种面向信息系统业务运行全景监测方法及系统 | |
| CN105446707B (zh) | 一种数据转换方法 | |
| CN115525392A (zh) | 容器监控方法、装置、电子设备及存储介质 | |
| CN110647070A (zh) | 一种用于超大规模数据中心的动力环境监控系统 | |
| WO2023272853A1 (zh) | 基于ai的sql引擎调用方法、装置、设备及介质 | |
| CN110851316A (zh) | 异常预警方法及装置、系统、电子设备、存储介质 | |
| CN115065563A (zh) | 一种基于区块链预言机的民航数据处理系统 | |
| CN115202973A (zh) | 应用运行状态的确定方法、装置、电子设备和介质 | |
| CN112905470A (zh) | 接口调用方法、装置、计算机设备及介质 | |
| CN115220992A (zh) | 接口变更监控方法、装置、计算机设备和存储介质 | |
| CN109766238B (zh) | 基于session数的运维平台性能监控方法、装置及相关设备 | |
| CN113132431B (zh) | 服务监控方法、服务监控装置、电子设备及介质 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21884538 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 110823) |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 21884538 Country of ref document: EP Kind code of ref document: A1 |