A cloud platform event reporting method, device and equipment based on adaptation template

Abstract

The present invention provides a cloud platform event reporting method, device, and equipment based on adaptation templates. The method includes the following steps: upon receiving a report of a new event type, analyzing the reporting attributes of the new event type; traversing pre-stored adaptation templates and searching for the adaptation template containing each reported attribute one by one; generating a corresponding attribute adaptation list from the found adaptation templates; processing the corresponding adaptation templates in the attribute adaptation list, and outputting the corresponding adaptation templates according to priority after processing; determining whether the output adaptation template meets the requirements of the new event type; if so, setting the output adaptation template and reporting the event; if not, creating an adaptation template for the new event type, and after the creation is complete, reporting the event. The reporting and receiving of the event system are decoupled, reducing the phenomenon of customized development during event docking.

Description

Technical Field

[0001] The present invention relates to the technical field of cloud computing data centers, and in particular to a cloud platform event reporting method, apparatus, and device based on an adapter mode. Background Art

[0002] Nowadays, more and more companies are developing their own cloud platform projects, which can access various underlying virtualizations and manage various cloud resources. Cloud platforms generally have their own monitoring and alarm systems, which monitor and issue alarms based on the underlying virtualization resources.

[0003] Cloud platforms can't cover all alarm events, and due to the limitations of a unified interface, they can't display all alarm systems. Furthermore, many virtualized systems have their own alarm systems that generate alarm events. If the cloud platform were to perform additional alarm calculations for these systems, it would waste resources. Therefore, cloud platforms have developed an event system to receive alarm events from other platforms or resources. Some underlying virtualized systems can directly report alarm events for unified display on the cloud platform.

[0004] However, this type of event system is often developed only through interfaces within the platform that needs to report events. When an event occurs, the cloud platform's event system interface is called to report it. This approach can achieve the effect of event reporting, but it also requires development within the reporting platform. When there are many different platforms and resources, it leads to increased development workload and integration difficulties. Summary of the Invention

[0005] Existing event systems can only be developed through interfaces in the platform where events need to be reported. When an event occurs, the interface of the cloud platform's event system is called to report it. This method can achieve the effect of time reporting, but it also requires development in the reporting platform. When there are many types of platforms and resources, it will lead to problems such as increased development workload and difficulty in integration. The present invention provides a cloud platform event reporting method, device, and equipment based on the adapter mode.

[0006] The technical solution of the present invention is:

[0007] In a first aspect, the technical solution of the present invention provides a cloud platform event reporting method based on an adaptation template, comprising the following steps:

[0008] When receiving a report of a new event type, analyze the reported attributes of the new event type;

[0009] Traverse the pre-stored adaptation templates and search for the adaptation template that contains each reported attribute one by one;

[0010] Generate a corresponding attribute adaptation list from the found adaptation template;

[0011] Process the corresponding adaptation templates in the attribute adaptation list, and output the corresponding adaptation templates according to the priority level after processing;

[0012] Determine whether the output adaptation template meets the requirements of the new event type;

[0013] If so, set the output adaptation template and report the event;

[0014] If not, create an adaptation template for the new event type, and after the creation is completed, report the event.

[0015] By creating an adaptation template, the event reporter and receiver are decoupled. The reporter no longer needs to customize the development according to the receiving interface specification. Instead, the intermediate adaptation template is used to map attributes for flexible event reporting and reception.

[0016] Furthermore, upon receiving a report of a new event type, the step of analyzing the report attributes of the new event type includes:

[0017] When an event report is detected, check whether the reported event type is a new event type;

[0018] If not, report the incident;

[0019] If yes, execute step: Analyze the reporting attributes of the new event type.

[0020] Based on the mapping data of existing adaptation templates, when a new system needs to report an event, it can adaptively adapt the existing adaptation mapping relationship based on the attributes of the reported event to provide a basic mapping relationship, reducing manual configuration and improving efficiency. After the basic adapter is formed, it can be modified to make the mapping relationship more accurate so that the underlying events can be uploaded to the cloud platform's event system more reasonably.

[0021] Furthermore, the steps of processing the corresponding adaptation templates in the attribute adaptation list and outputting the corresponding adaptation templates according to the priority after processing include:

[0022] Count the number of times the corresponding adaptation template appears in each attribute adaptation list;

[0023] Sort by the number of times, and set the matching priority to higher the number of times;

[0024] Outputs the number of adaptation templates with the highest priority before the set threshold.

[0025] When there are more adaptation template mapping data, when adding new event types to report, you can take an adaptive approach to select or create the initial template, and then set the last shift to add the mapping relationship to reduce manual workload.

[0026] Furthermore, when an event report is detected, the step of checking whether the reported event type is a new event type includes:

[0027] An adaptation template for a reported event is created based on historical reported events, and the created adaptation template is stored.

[0028] An adaptation method is introduced, which connects the event reporter and the receiver through an adaptation template, rather than directly performing customized development in the report to adapt the receiver's data.

[0029] Furthermore, the steps of creating an adaptation template for the new event type include:

[0030] Initialize the reported event attributes;

[0031] Establish a one-to-one mapping relationship between the reported event attributes and the corresponding cloud platform attributes to generate an adaptation template;

[0032] Establish a correspondence between the reported event and the generated adaptation template.

[0033] It is necessary to set up the adaptation template mapping relationship and the corresponding event reporting system in the cloud platform.

[0034] Furthermore, the method further comprises:

[0035] After the report is completed, check whether the event information is displayed in the cloud platform's event system according to the attributes.

[0036] First, through custom configuration, adapter templates are added to both the virtualization platform that reports events and the cloud platform that receives them. Within the adapter templates, custom attribute mappings are configured between the event attributes of the reporting platform and the attributes of the events received by the cloud platform, enabling smooth reporting to the cloud platform's event system. Secondly, when a large number of events are reported to the cloud platform, adaptive mapping relationships can be established based on the mapping data in the existing cloud platform event adapter templates. This reduces the workload of manually configuring mapping relationships and reduces the complexity of platform usage. This allows other underlying virtualization platforms to report their own alarm events through the cloud platform's event system for unified processing and display within the cloud platform. This facilitates timely response by operations and maintenance personnel, ensuring the normal operation of platform resources.

[0037] Decoupling the reporting and reception of the event system reduces the need for customized development during event integration. Furthermore, when a large number of adaptation templates exist, adaptive algorithms can automatically match newly connected event types with appropriate adaptation templates, or create appropriate templates for user processing, ultimately forming the final adaptation template to complete event reporting and reception, reducing manual intervention.

[0038] In a second aspect, the technical solution of the present invention provides a cloud platform event reporting device based on an adaptation template, comprising an attribute analysis module, a scan matching module, a processing and output module, a judgment module, a reporting module, and a creation module;

[0039] The attribute analysis module is used to analyze the reported attributes of the new event type when receiving the report of the new event type;

[0040] The scanning and matching module is used to traverse the pre-stored adaptation templates and search for the adaptation template containing each reported attribute one by one; and generate the corresponding attribute adaptation list for the found adaptation template;

[0041] The processing output module is used to process the corresponding adaptation templates in the attribute adaptation list and output the corresponding adaptation templates according to the priority level after processing;

[0042] A judgment module is used to judge whether the output adaptation template meets the requirements of the new event type;

[0043] The reporting module is used to report the event after setting the output adaptation template; after the creation module completes the creation of the adaptation template, the event is reported through the created adaptation template;

[0044] The creation module is used to create an adaptation template for the new event type, and is also used to create an adaptation template for the reported event based on historical reported events, and store the created adaptation template.

[0045] By creating an adaptation template, the event reporter and receiver are decoupled. The reporter no longer needs to customize the development according to the receiving interface specification. Instead, the intermediate adaptation template is used to map attributes for flexible event reporting and reception.

[0046] Furthermore, the device further comprises a checking module, which is configured to check whether the reported event type is a new event type when an event is detected to be reported.

[0047] Based on the mapping data of existing adaptation templates, when a new system needs to report an event, it can adaptively adapt the existing adaptation mapping relationship based on the attributes of the reported event to provide a basic mapping relationship, reducing manual configuration and improving efficiency. After the basic adapter is formed, it can be modified to make the mapping relationship more accurate so that the underlying events can be uploaded to the cloud platform's event system more reasonably.

[0048] Furthermore, the processing and output module includes a statistics unit, a setting unit and an output unit;

[0049] A statistical unit, used to count the number of times the corresponding adaptation template appears in each attribute adaptation list;

[0050] Setting unit, used to sort by number of times, and the more times you set, the higher the matching priority;

[0051] The output unit is used to output the adaptation templates with high priority and a set number of adaptation templates before the threshold.

[0052] When there are more adaptation template mapping data, when adding new event types to report, you can take an adaptive approach to select or create the initial template, and then set the last shift to add the mapping relationship to reduce manual workload.

[0053] Furthermore, the creation module includes an initialization unit, a mapping unit, and a correspondence establishment unit;

[0054] Initialization unit, used to initialize the reported event attributes;

[0055] A mapping unit, configured to establish a one-to-one mapping relationship between the reported event attributes and the corresponding cloud platform attributes to generate an adaptation template;

[0056] The corresponding relationship establishing unit is used to establish the corresponding relationship between the reported event and the generated adaptation template.

[0057] An adaptation method is introduced, which connects the event reporter and the receiver through an adaptation template, rather than directly performing customized development in the report to adapt the receiver's data.

[0058] Furthermore, the device further comprises an output display module for displaying reporting time information, and after the reporting is completed, checking whether the display module displays the information of the reporting event according to the attributes.

[0059] The present invention proposes to decouple the reporter and receiver of an event through an adaptation template. The reporter no longer needs to perform customized development according to the received interface specification, but instead performs attribute mapping through the intermediate adaptation template to flexibly report and receive events. Then, based on the mapping data in the existing adaptation template, when a new system needs to report an event, it can perform adaptive adaptation in the existing adaptation template mapping relationship according to the attributes of the reported event to provide a basic mapping relationship, thereby reducing manual configuration and improving efficiency. After the basic adaptation template is formed, it can be manually modified so that the mapping relationship is more accurate, so that the underlying events can be more reasonably uploaded to the event system of the cloud platform.

[0060] In the third aspect, the technical solution of the present invention also provides a computer device, including a processor and a memory, and the processor and the memory communicate with each other through a bus; the memory stores program instructions that can be executed by the processor, and the processor calls the program instructions to execute the cloud platform event reporting method based on the adaptation template as described in the first aspect.

[0061] As can be seen from the above technical solution, the present invention has the following advantages: Through adaptation, the present invention decouples the reporting and reception of the event system, reducing the need for customized development during event docking. Furthermore, when a large number of adapter templates exist, an adaptive algorithm can automatically match newly connected event types to the appropriate adapter template, or create a suitable template for user processing, forming the final adapter template to complete event reporting and reception, reducing manual intervention.

[0062] In addition, the present invention has a reliable design principle, a simple structure and a very broad application prospect.

[0063] It can be seen that compared with the prior art, the present invention has outstanding substantial features and significant progress, and the beneficial effects of its implementation are also obvious. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0065] Figure 1 is a schematic flow chart of a method according to an embodiment of the present invention.

[0066] Figure 2 is a schematic flow chart of a method according to another embodiment of the present invention.

[0067] Figure 3 is a schematic block diagram of an apparatus according to an embodiment of the present invention. DETAILED DESCRIPTION

[0068] In order to enable those skilled in the art to better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0069] like Figure 1 As shown, an embodiment of the present invention provides a cloud platform event reporting method based on an adaptation template, comprising the following steps:

[0070] Step 11: When a new event type report is received, the report attributes of the new event type are analyzed;

[0071] Step 12: Traverse the pre-stored adaptation templates and search for the adaptation template containing each reported attribute one by one;

[0072] Step 13: Generate a corresponding attribute adaptation list based on the found adaptation template;

[0073] Step 14: Process the corresponding adaptation templates in the attribute adaptation list, and output the corresponding adaptation templates according to their priority.

[0074] Step 15: Determine whether the output adaptation template meets the requirements of the new event type; if so, execute step 16; otherwise, execute step 17;

[0075] Step 16: After setting the output adaptation template, report the event;

[0076] Step 17: Create an adaptation template for the new event type. After the creation is complete, report the event.

[0077] By creating an adaptation template, the event reporter and receiver are decoupled. The reporter no longer needs to customize the development according to the receiving interface specification. Instead, the intermediate adaptation template is used to map attributes for flexible event reporting and reception.

[0078] like Figure 2 As shown, an embodiment of the present invention provides a cloud platform event reporting method based on an adaptation template, comprising the following steps:

[0079] Step 21: When an event report is detected, check whether the reported event type is a new event type; if not, execute step 28, otherwise execute step 22;

[0080] In this step, checking whether it is a new event type actually means checking whether there is a corresponding adaptation template for this type.

[0081] Step 22: Analyze the reporting attributes of the new event type;

[0082] Step 23: traverse the pre-stored adaptation templates, search for the adaptation template containing each reported attribute one by one, and generate a corresponding attribute adaptation list for the found adaptation template;

[0083] For the new type of attribute A, the system traverses the existing adapter templates, searches for templates with this attribute, and records them as A_list. For example, if templates 1, 3, and 9 contain attribute A, then A_list = {1, 3, 9}. Iterate through all attributes B, C, D, etc. of the event type to obtain B_list, C_list, D_list, etc.

[0084] Step 24: Process the corresponding adaptation templates in the attribute adaptation list and output them according to priority. This step includes: counting the number of occurrences of the corresponding adaptation template in each attribute adaptation list; sorting by occurrence, setting a higher matching priority for templates with higher occurrences; and outputting the adaptation templates with the highest priority, which are the number of times a threshold is set. Count all lists, including A_list, B_list, C_list, and D_list, and count the number of times the templates appear. Then sort them by occurrence, with the highest matching priority assigned to templates with higher occurrences. The top three matching templates are displayed.

[0085] Step 25: Determine whether the output adaptation template meets the requirements of the new event type; if so, execute step 26; otherwise, execute step 27;

[0086] Step 26: Set the output adaptation template and execute step 28; the data is displayed. After the display is completed, manual modification can be performed to make the adaptation more accurate and rigorous.

[0087] Step 27: Create an adaptation template for the new event type. After the creation is complete, proceed to step 28;

[0088] In this step, creating an adaptation template for the new event type includes:

[0089] Step 271: Initialize the reported event attributes. The event attributes that can be received by the cloud platform need to be initialized so that it can receive reports and display event content. For example, the basic attributes of an event include ID, name, module, category, content, description, prompt information, etc.

[0090] Step 272: Establish a one-to-one mapping relationship between the reported event attributes and the corresponding cloud platform attributes to generate an adaptation template;

[0091] For a new event reporting source or a new event type, you need to add a mapping relationship, mapping the basic attributes of the event in the previous step one by one. For example, if a VMware virtualization system needs to upload a host failure event, the reporting interface uses "name" to identify the name, "type" to identify the type, and "tip" to identify the tip. This mapping relationship needs to be written in the VMware mapping template, for example, "name:name".

[0092] Step 273: Establish a correspondence between the reported event and the generated adaptation template.

[0093] In the previous step, we added a template and established the corresponding relationship between the event system. In this step, we need to set the association between this template and the VMware host event, that is, use the ID of this template as the association template for the VMware host event.

[0094] Step 28: Report the incident;

[0095] Step 29: After the report is completed, check whether the event information of the reported event is displayed according to the attributes in the event system of the cloud platform.

[0096] Based on the mapping data of existing adaptation templates, when a new system needs to report an event, it can adaptively adapt the existing adaptation mapping relationship based on the attributes of the reported event to provide a basic mapping relationship, reducing manual configuration and improving efficiency. After the basic adapter is formed, it can be modified to make the mapping relationship more accurate so that the underlying events can be uploaded to the cloud platform's event system more reasonably.

[0097] When there are more adaptation template mapping data, when adding new event types to report, you can take an adaptive approach to select or create the initial template, and then set the last shift to add the mapping relationship to reduce manual workload.

[0098] It should be noted that when an event report is detected, the step of checking whether the reported event type is new includes: creating an adaptation template for the reported event based on historically reported events and storing the created adaptation template. This introduces an adaptation method, connecting the event reporter and the receiver through the adaptation template, rather than directly customizing the report to adapt the receiver's data.

[0099] First, through custom configuration, adapter templates are added to both the virtualization platform that reports events and the cloud platform that receives them. Within the adapter templates, custom attribute mappings are configured between the event attributes of the reporting platform and the attributes of the events received by the cloud platform, enabling smooth reporting to the cloud platform's event system. Secondly, when a large number of events are reported to the cloud platform, adaptive mapping relationships can be established based on the mapping data in the existing cloud platform event adapter templates. This reduces the workload of manually configuring mapping relationships and reduces the complexity of platform usage. This allows other underlying virtualization platforms to report their own alarm events through the cloud platform's event system for unified processing and display within the cloud platform. This facilitates timely response by operations and maintenance personnel, ensuring the normal operation of platform resources.

[0100] Decoupling the reporting and reception of the event system reduces the need for customized development during event integration. Furthermore, when a large number of adaptation templates exist, adaptive algorithms can automatically match newly connected event types with appropriate adaptation templates, or create appropriate templates for user processing, ultimately forming the final adaptation template to complete event reporting and reception, reducing manual intervention.

[0101] like Figure 3 As shown, an embodiment of the present invention provides a cloud platform event reporting device based on an adaptation template, comprising an attribute analysis module, a scan matching module, a processing and output module, a judgment module, a reporting module, and a creation module;

[0102] The attribute analysis module is used to analyze the reported attributes of the new event type when receiving the report of the new event type;

[0103] The scanning and matching module is used to traverse the pre-stored adaptation templates and search for the adaptation template containing each reported attribute one by one; and generate the corresponding attribute adaptation list for the found adaptation template;

[0104] The processing output module is used to process the corresponding adaptation templates in the attribute adaptation list and output the corresponding adaptation templates according to the priority level after processing;

[0105] A judgment module is used to judge whether the output adaptation template meets the requirements of the new event type;

[0106] The reporting module is used to report the event after setting the output adaptation template; after the creation module completes the creation of the adaptation template, the event is reported through the created adaptation template;

[0107] The creation module is used to create an adaptation template for the new event type, and is also used to create an adaptation template for the reported event based on historical reported events, and store the created adaptation template.

[0108] By creating an adaptation template, the event reporter and receiver are decoupled. The reporter no longer needs to customize the development according to the receiving interface specification. Instead, the intermediate adaptation template is used to map attributes for flexible event reporting and reception.

[0109] It should be noted that the device further includes a checking module for checking whether the reported event type is a new event type when an event is detected;

[0110] The reporting module is used to match the corresponding adaptation template in the adaptation templates pre-stored in the system and report the event.

[0111] Based on the mapping data of existing adaptation templates, when a new system needs to report an event, it can adaptively adapt the existing adaptation mapping relationship based on the attributes of the reported event to provide a basic mapping relationship, reducing manual configuration and improving efficiency. After the basic adapter is formed, it can be modified to make the mapping relationship more accurate so that the underlying events can be uploaded to the cloud platform's event system more reasonably.

[0112] In some specific embodiments, the processing output module includes a statistical unit, a setting unit, and an output unit;

[0113] A statistical unit, used to count the number of times the corresponding adaptation template appears in each attribute adaptation list;

[0114] Setting unit, used to sort by number of times, and the more times you set, the higher the matching priority;

[0115] The output unit is used to output the adaptation templates with high priority and a set number of adaptation templates before the threshold.

[0116] When there are more adaptation template mapping data, when adding new event types to report, you can take an adaptive approach to select or create the initial template, and then set the last shift to add the mapping relationship to reduce manual workload.

[0117] In some specific embodiments, the creation module includes an initialization unit, a mapping unit, and a correspondence establishment unit;

[0118] Initialization unit, used to initialize the reported event attributes;

[0119] A mapping unit, configured to establish a one-to-one mapping relationship between the reported event attributes and the corresponding cloud platform attributes to generate an adaptation template;

[0120] The corresponding relationship establishing unit is used to establish the corresponding relationship between the reported event and the generated adaptation template.

[0121] An adaptation method is introduced, which connects the event reporter and the receiver through an adaptation template, rather than directly performing customized development in the report to adapt the receiver's data.

[0122] The device also includes an output display module for displaying reporting time information, and after the reporting is completed, checking whether the display module displays the information of the reporting event according to the attributes.

[0123] An embodiment of the present invention provides a computer device, which may include: a processor, a communication interface, a memory, and a bus, wherein the processor, the communication interface, and the memory communicate with each other via the bus. The bus can be used to transmit information between the electronic device and the sensor. The processor can call logic instructions in the memory to execute the following method: Step 11: Upon receiving a report of a new event type, analyze the reported attributes of the new event type; Step 12: traverse pre-stored adaptation templates and search for an adaptation template that includes each reported attribute; Step 13: generate a corresponding attribute adaptation list for the found adaptation templates; Step 14: process the corresponding adaptation templates in the attribute adaptation list and output the corresponding adaptation templates according to priority; Step 15: determine whether the output adaptation template meets the requirements of the new event type; if so, execute Step 16; otherwise, execute Step 17; Step 16: set the output adaptation template and report the event; Step 17: create an adaptation template for the new event type and, after creation, report the event.

[0124] In some specific embodiments, the processor can call the logical instructions in the memory, and specifically implement the following steps: count the number of times the corresponding adaptation template appears in each attribute adaptation list; sort by the number of times, and set the matching priority to be higher if the number of times is higher; output the adaptation templates with high priority before the set threshold number.

[0125] In some specific embodiments, the processor can call the logical instructions in the memory, and specifically implement the following steps: initialize the reported event attributes; establish a one-to-one mapping relationship between the reported event attributes and the corresponding attributes of the cloud platform to generate an adaptation template; establish a corresponding relationship between the reported event and the generated adaptation template.

[0126] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from the other embodiments. Reference can be made to the descriptions of the identical or similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and the relevant parts can be referred to the descriptions of the methods.

[0127] In addition, the logical instructions in the above-mentioned memory can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0128] Although the present invention has been described in detail with reference to the accompanying drawings and in conjunction with preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, a person of ordinary skill in the art may make various equivalent modifications or substitutions to the embodiments of the present invention, and such modifications or substitutions shall be within the scope of the present invention. Any person skilled in the art who can easily conceive of changes or substitutions within the technical scope disclosed in the present invention shall be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be based on the scope of protection of the claims.

Claims

1. A cloud platform event reporting method based on an adaptation template, characterized in that: The steps include: When receiving a report of a new event type, analyze the reported attributes of the new event type; Traverse the pre-stored adaptation templates and search for the adaptation template that contains each reported attribute one by one; Generate a corresponding attribute adaptation list from the found adaptation template; Process the corresponding adaptation templates in the attribute adaptation list, and output the corresponding adaptation templates according to the priority level after processing; Determine whether the output adaptation template meets the requirements of the new event type; If so, set the output adaptation template and report the event; If not, create an adaptation template for the new event type, and after the creation is complete, report the event; The steps of processing the corresponding adaptation templates in the attribute adaptation list and outputting the corresponding adaptation templates according to the priority after processing include: Count the number of times the corresponding adaptation template appears in each attribute adaptation list; Sort by the number of times, and set the higher the number of times, the higher the matching priority; Output the adaptation templates with the highest priority before the set threshold number; The steps to create an adaptation template for this new event type include: Initialize the reported event attributes; Establish a one-to-one mapping relationship between the reported event attributes and the corresponding cloud platform attributes to generate an adaptation template; Establish a correspondence between the reported event and the generated adaptation template.

2. The cloud platform event reporting method based on the adaptation template according to claim 1 is characterized in that: When a new event type report is received, the steps for analyzing the reported attributes of the new event type include: When an event report is detected, check whether the reported event type is a new event type; If not, report the incident; If yes, execute step: Analyze the reporting attributes of the new event type.

3. The cloud platform event reporting method based on the adaptation template according to claim 1 is characterized in that: When an event report is detected, the steps for checking whether the reported event type is a new event type include: An adaptation template for a reported event is created based on historical reported events, and the created adaptation template is stored.

4. The cloud platform event reporting method based on the adaptation template according to claim 3 is characterized in that: The method further includes: After the report is completed, check whether the event information is displayed in the cloud platform's event system according to the attributes.

5. A cloud platform event reporting device based on an adaptation template, characterized in that: It includes attribute analysis module, scan matching module, processing output module, judgment module, reporting module and creation module; The attribute analysis module is used to analyze the reported attributes of the new event type when receiving the report of the new event type; The scanning and matching module is used to traverse the pre-stored adaptation templates and search for the adaptation template containing each reported attribute one by one; and generate the corresponding attribute adaptation list for the found adaptation template; The processing output module is used to process the corresponding adaptation templates in the attribute adaptation list and output the corresponding adaptation templates according to the priority level after processing; A judgment module is used to judge whether the output adaptation template meets the requirements of the new event type; The reporting module is used to report the event after setting the output adaptation template; After the creation module completes the creation of the adaptation template, the event is reported; A creation module is used to create an adaptation template for the new event type, and is also used to create an adaptation template for the reported event based on the historical reported events, and store the created adaptation template; The processing output module includes a statistics unit, a setting unit and an output unit; A statistical unit, used to count the number of times the corresponding adaptation template appears in each attribute adaptation list; Setting unit, used to sort by number of times, and the more times you set, the higher the matching priority; The output unit is used to output the adaptation templates with high priority and a set number of adaptation templates before the threshold.

6. The cloud platform event reporting device based on the adaptation template according to claim 5 is characterized in that: The device further comprises a checking module, which is used to check whether the reported event type is a new event type when an event is detected to be reported.

7. A computer device, characterized in that: It includes a processor and a memory, and the processor and the memory communicate with each other through a bus; the memory stores program instructions that can be executed by the processor, and the processor calls the program instructions to execute the cloud platform event reporting method based on the adaptation template as described in any one of claims 1 to 4.

Images