A multi-region cloud architecture monitoring data collection method

Abstract

The application discloses a kind of multi-region cloud architecture monitoring data acquisition methods, it is related to distributed data acquisition technical field;Including: step 1: to each Region deployment acquisition end, step 2: through acquisition end, acquisition monitoring data, the monitoring data includes server performance data, database performance data, network equipment data, port state data and business related inspection data, step 3: different protocol monitoring data is converted into standard format monitoring data, step 4: through acquisition end, standard format monitoring data is encrypted and pushed to cloud platform, step 5: through cloud platform, according to the mode of power and domain, save data, step 6: through cloud platform, according to demand, show monitoring data, step 7: through cloud platform, provide interface, for third party to obtain monitoring data, step 8: using Kapacitor handles monitoring data, triggers abnormal alarm.

Description

TECHNICAL FIELD

[0001] The application discloses a method and relates to the technical field of distributed data collection, in particular to a multi-Region cloud architecture monitoring data collection method. BACKGROUND

[0002] With the deployment of large-scale, multi-Region cloud platforms, in order to ensure normal operation of the system, real-time monitoring resource usage must be obtained in time. At present, the monitoring data collection module and the analysis module are concentrated together, which is inconvenient for expansion. The monitoring object in each Region provides inconsistent monitoring data interface protocols, and when the interface protocol is changed, the corresponding monitoring system needs to be adjusted, which is very inconvenient. Meanwhile, when the monitoring data is transmitted on the Internet, sensitive data collected by the monitoring system is not processed, and there is a risk of information leakage. SUMMARY

[0003] The application provides a multi-Region cloud architecture monitoring data collection method, realizes data collection, improves the maintainability of the monitoring system in the multi-Region architecture mode, and reduces the risk of monitoring data leakage.

[0004] The specific scheme provided by the application is as follows:

[0005] The application provides a multi-Region cloud architecture monitoring data collection method, which comprises the following steps:

[0006] Step 1: deploying a collection end in each Region,

[0007] Step 2: collecting monitoring data through the collection end, wherein the monitoring data comprises server performance data, database performance data, network equipment data, port state data and business-related inspection data,

[0008] Step 3: converting monitoring data of different protocols into monitoring data in a standard format,

[0009] Step 4: pushing the monitoring data in the standard format to a cloud platform through the collection end,

[0010] Step 5: saving the monitoring data in a decentralized manner through the cloud platform,

[0011] Step 6: displaying the monitoring data according to requirements through the cloud platform,

[0012] Step 7: providing an interface through the cloud platform to enable a third party to obtain the monitoring data,

[0013] Step 8: processing the monitoring data through Kapacitor and triggering an abnormal alarm.

[0014] Further, in the step 2 of the multi-Region cloud architecture monitoring data collection method, each Region collects monitoring data in a time manner according to different configuration files through the collection end.

[0015] Further, in the step 4 of the multi-Region cloud architecture monitoring data collection method, the information of the collection end is registered through the cloud platform, and the CA certificate, the authorization code, the client private key and the server public key corresponding to each collection end are distributed,

[0016] The collection end uses the CA certificate authentication interface, and if the authentication is successful, the interface is called to obtain token information, the to-be-sent plaintext is encrypted by using the server public key, the to-be-sent plaintext is signed by using the client private key, the token information is added to the request header, and the encrypted and signed monitoring data is pushed to the cloud platform.

[0017] Further, in the step 5 of the multi-Region cloud architecture monitoring data collection method, the token information in the request header is verified through the cloud platform, if the verification is successful, the signature verification operation of the request message is performed, if the signature verification is successful, the decryption operation of the request message is performed, if the decryption is successful, the data is saved in a power and domain manner.

[0018] The application provides a multi-Region cloud architecture monitoring data collection device, which comprises a deployment module, a collection module, a conversion module, an encryption pushing module, a receiving module, a display module, a third-party interface module and an alarm module,

[0019] The deployment module deploys the collection end to each Region,

[0020] The collection end collects monitoring data through the collection module, and the monitoring data comprises server performance data, database performance data, network equipment data, port state data and business-related inspection data,

[0021] The conversion module converts monitoring data in different protocols into monitoring data in a standard format,

[0022] The collection end pushes the monitoring data in the standard format to the cloud platform through the encryption pushing module,

[0023] The cloud platform saves data in a power and domain manner through the receiving module,

[0024] The cloud platform displays monitoring data according to requirements through the display module,

[0025] The cloud platform provides an interface through the third-party interface module, so that a third party can obtain monitoring data,

[0026] The alarm module uses Kapacitor to process monitoring data and trigger abnormal alarm.

[0027] Furthermore, in the multi-Region cloud architecture monitoring data acquisition device, the acquisition end collects monitoring data periodically through the acquisition module according to the different configuration files of each Region.

[0028] Furthermore, in the multi-Region cloud architecture monitoring data acquisition device, the information of the acquisition terminals is registered through the cloud platform, and each acquisition terminal is assigned a corresponding CA certificate, authorization code, client private key, and server public key.

[0029] The data collection end uses the CA certificate authentication interface through the encrypted push module. If the authentication is successful, it calls the interface to obtain the token information, encrypts the plaintext to be sent using the server's public key, and signs the plaintext to be sent using the client's private key. The token information is added to the request header, and the encrypted and signed monitoring data is pushed to the cloud platform.

[0030] Furthermore, in the multi-Region cloud architecture monitoring data acquisition device, the cloud platform verifies the token information in the request header through the receiving module. If the verification is successful, the request message is verified. If the verification is successful, the request message is decrypted. If the decryption is successful, the data is saved in a hierarchical manner.

[0031] The advantages of this invention are:

[0032] This invention provides a method for collecting monitoring data in a multi-Region cloud architecture. It collects monitoring object data from each Region without changing the interface protocol, processes the monitoring data, and encrypts and pushes the data, eliminating the risk of information leakage. This improves the maintainability of the monitoring system while reducing the risk of monitoring data leakage. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of the application framework of the method of the present invention.

[0034] Figure 2 This is a schematic diagram of the monitoring data push process involved in the method of the present invention. Detailed Implementation

[0035] The present invention will be further described below with reference to the accompanying drawings and specific embodiments, so that those skilled in the art can better understand and implement the present invention. However, the embodiments described are not intended to limit the present invention.

[0036] This invention provides a method for collecting monitoring data in a multi-Region cloud architecture, including:

[0037] Step 1: Deploy the data collection terminal in each Region.

[0038] Step 2: collecting monitoring data through the collection end, wherein the monitoring data comprises server performance data, database performance data, network equipment data, port state data and business-related inspection data,

[0039] Step 3: converting monitoring data of different protocols into monitoring data in a standard format,

[0040] Step 4: encrypting and pushing the monitoring data in the standard format to the cloud platform through the collection end,

[0041] Step 5: saving the monitoring data in a decentralized manner through the cloud platform,

[0042] Step 6: displaying the monitoring data according to requirements through the cloud platform,

[0043] Step 7: providing an interface for a third party to obtain the monitoring data through the cloud platform,

[0044] Step 8: processing the monitoring data using Kapacitor to trigger an abnormal alarm.

[0045] The method of the application collects monitoring data based on a multi-Region cloud architecture, and the collection part and the analysis function are divided into two different functions, thereby further reducing system coupling. The collection part can be implemented by supporting multiple programming languages, thereby facilitating different language developers to quickly implement. Different protocol monitoring data can be converted into standard data at the gateway layer, and the central end business logic does not need to be modified when the protocol changes. When transmitting monitoring data on the Internet, CA certificates, encryption, signature and other technologies are used, thereby further reducing the risk of sensitive data leakage.

[0046] In some embodiments of the method of the application, with reference to Figure 1 , the process is as follows:

[0047] Step 1: deploying a collection end for each Region.

[0048] Step 2: collecting monitoring data through the collection end, wherein the monitoring data comprises server performance data, database performance data, network equipment data, port state data and business-related inspection data.

[0049] Further, in step 2, each Region collects monitoring data through the collection end according to different configuration files.

[0050] Step 3: converting monitoring data of different protocols into monitoring data in a standard format,

[0051] Step 4: encrypting and pushing the monitoring data in the standard format to the cloud platform through the collection end.

[0052] In step 4, the information of the collection end is registered through the cloud platform, and the CA certificate, authorization code, client private key and server public key corresponding to each collection end are distributed,

[0053] If the CA authentication fails, the process is ended, and error information is returned, if the authentication is successful, the interface is called to obtain token information, the server public key is used for encryption of the to-be-sent plaintext, the client private key is used for signature of the to-be-sent plaintext, the token information is added to the request header, and the encrypted and signed monitoring data is pushed to the cloud platform.

[0054] In step 5, the cloud platform receives the monitoring data and saves the data in a decentralized manner.

[0055] If the Token verification fails, the process is ended, and error information is returned,

[0056] If the Token verification succeeds, the request message is verified, if the request message verification fails, the process is ended, and error information is returned,

[0057] If the request message verification succeeds, the request message is decrypted, if the request message decryption fails, the process is ended, and error information is returned,

[0058] If the request message decryption succeeds, the data is saved in a decentralized manner, and the monitoring data is stored in a database.

[0059] In step 6, the cloud platform displays the monitoring data according to requirements.

[0060] In step 7, the cloud platform provides an interface for a third party to obtain monitoring data.

[0061] In step 8, the Kapacitor is used to process the monitoring data and trigger an abnormal alarm.

[0062] The application provides a multi-Region cloud architecture monitoring data collection device, which comprises a deployment module, a collection module, a conversion module, an encryption pushing module, a receiving module, a display module, a third-party interface module and an alarm module,

[0063] The deployment module deploys a collection end for each Region,

[0064] The collection end collects monitoring data through the collection module, and the monitoring data comprises server performance data, database performance data, network equipment data, port state data and business-related inspection data,

[0065] The conversion module converts monitoring data of different protocols into monitoring data in a standard format,

[0066] The acquisition end pushes the monitoring data in a standard format to the cloud platform through an encryption pushing module,

[0067] The cloud platform receives the monitoring data through a receiving module and saves the data in a decentralized manner,

[0068] The cloud platform displays the monitoring data according to requirements through a display module,

[0069] The cloud platform provides an interface for a third party to obtain the monitoring data through a third-party interface module,

[0070] The alarm module uses Kapacitor to process the monitoring data and trigger an abnormal alarm.

[0071] The information interaction and execution process between the modules in the device are based on the same concept as the method embodiments of the present application, and the specific content can be referred to the description in the method embodiments of the present application, which will not be repeated here.

[0072] Similarly, the device of the present application collects monitoring object data in each Region, processes the monitoring data, and pushes the data after encryption, without changing the interface protocol, and without the risk of information leakage. The maintainability of the monitoring system is improved, and the risk of monitoring data leakage is reduced.

[0073] It should be noted that not all steps and modules in the above processes and device structures are necessary, and some steps or modules can be ignored according to actual needs. The execution order of each step is not fixed and can be adjusted as needed. The system structure described in the above embodiments can be a physical structure or a logical structure, that is, some modules can be implemented by the same physical entity, or some modules can be implemented by multiple physical entities, or they can be implemented by some components in multiple independent devices.

[0074] The above-described embodiments are only preferred embodiments of the present application, and the protection scope of the present application is not limited thereto. Equivalent substitutions or transformations made by those skilled in the art based on the present application are within the protection scope of the present application. The protection scope of the present application is subject to the claims.

Claims

1. A method for collecting monitoring data in a multi-Region cloud architecture, characterized by: include: Step 1: Deploy the data collection terminal in each Region. Step 2: Collect monitoring data through the acquisition terminal. The monitoring data includes server performance data, database performance data, network device data, port status data, and service-related inspection data. Step 3: Convert monitoring data from different protocols into monitoring data in a standard format. Step 4: Encrypt and push standard-format monitoring data to the cloud platform via the acquisition terminal. This involves registering the acquisition terminal's information on the cloud platform and assigning each acquisition terminal a corresponding CA certificate, authorization code, client private key, and server public key. The data acquisition end uses a CA certificate authentication interface. Upon successful authentication, the interface is called to obtain token information. The plaintext to be sent is signed using the client's private key, and the signed message is encrypted using the server's public key. Token information is added to the request header, and the encrypted and signed monitoring data is pushed to the cloud platform. Step 5: Receive monitoring data via the cloud platform and save the data according to a hierarchical and domain-based approach. Specifically, the cloud platform verifies the token information in the request header. If verification is successful, the request message is verified for signature. If signature verification is successful, the request message is decrypted. If decryption is successful, the data is saved according to the hierarchical and domain-based approach. Step 6: Display the monitoring data as needed through the cloud platform. Step 7: Provide an interface through the cloud platform for third parties to obtain monitoring data. Step 8: Use Kapacitor to process monitoring data and trigger anomaly alerts.

2. The method for collecting monitoring data in a multi-Region cloud architecture according to claim 1, characterized in that: In step 2, each Region collects monitoring data periodically through the acquisition terminal according to different configuration files.

3. A multi-Region cloud architecture monitoring data acquisition device, characterized in that: It includes a deployment module, a data collection module, a conversion module, an encrypted push module, a receiving module, a display module, a third-party interface module, and an alarm module. The deployment module deploys the data collection terminal to each Region. The acquisition terminal collects monitoring data through the acquisition module. This monitoring data includes server performance data, database performance data, network device data, port status data, and service-related inspection data. The conversion module converts monitoring data from different protocols into monitoring data in a standard format. The data acquisition terminal uses an encrypted push module to encrypt and push standard-format monitoring data to the cloud platform. This involves registering the data acquisition terminal's information on the cloud platform and assigning each terminal a corresponding CA certificate, authorization code, client private key, and server public key. The data collection terminal uses a CA certificate authentication interface through the encrypted push module. Upon successful authentication, it calls the interface to obtain token information, signs the plaintext to be sent using the client's private key, encrypts the signed message using the server's public key, adds token information to the request header, and pushes the encrypted and signed monitoring data to the cloud platform. The cloud platform receives monitoring data through a receiving module and saves the data in a hierarchical and domain-based manner. Specifically, the cloud platform verifies the token information in the request header through the receiving module. If the verification is successful, it performs a signature verification operation on the request message. If the signature verification is successful, it performs a decryption operation on the request message. If the decryption is successful, the data is saved in a hierarchical and domain-based manner. The cloud platform displays monitoring data according to needs through its display module. The cloud platform provides interfaces through third-party interface modules, allowing third parties to obtain monitoring data. The alarm module uses Kapacitor to process monitoring data and trigger abnormal alarms.

4. The multi-Region cloud architecture monitoring data acquisition device according to claim 3, characterized in that: Based on the different configuration files for each Region, the acquisition terminal collects monitoring data periodically through the acquisition module.

Images