Event monitoring system construction method, monitoring method, device, equipment and medium
By building an event monitoring system with multi-level modules and traceability links, and integrating monitoring functions of different cloud products, the problems of isolated event monitoring products and limited resource objects in the existing technology are solved, and efficient monitoring and operation and maintenance experience is improved.
Patent Information
- Application Number
- CN202211518429.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-11-29
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2042-11-29
AI Technical Summary
Existing event monitoring products are isolated from each other and cannot be linked, and the resource objects that each product can monitor are limited, resulting in users needing to jump multiple products for monitoring, which has low monitoring efficiency and poor user experience.
By building multiple hierarchical modules and internal and external traceability links, a full-link event monitoring system is formed, monitoring functions of different cloud products are integrated, and the entrances are centralized to achieve integrated monitoring and operation and maintenance.
It reduces the complexity of event traceability and troubleshooting, expands the scope of monitoring resource objects, improves the efficiency and user experience of monitoring and operation and maintenance, and reduces the jump between multiple cloud products.
Smart Images

Figure CN116016098B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of cloud computing technology, and in particular to a construction method, monitoring method, device, equipment and medium of an event monitoring system. Background Art
[0002] Event monitoring refers to the reporting, querying and alarming of event type data, including cloud product failures, operation and maintenance events, user business abnormal events, application events, etc. Existing event monitoring products are isolated from each other, and each event monitoring product can monitor a limited number of resource objects. Different resource objects need to be monitored by different event monitoring products. Users have to jump to multiple event monitoring products, which leads to low monitoring efficiency, fragmented user monitoring links and poor interactive experience. Summary of the invention
[0003] The embodiments of the present application provide a construction method, monitoring method, device, equipment and medium of an event monitoring system to solve the problems existing in the prior art.
[0004] In a first aspect, an embodiment of the present application provides a method for constructing an event monitoring system, including:
[0005] According to the multiple resource attributes of the object to be monitored, construct multiple hierarchical modules corresponding to the object to be monitored; the resource attributes include cloud product attributes, and the multiple hierarchical modules include cloud product layers corresponding to multiple cloud products;
[0006] According to the object association relationship within each level module, build the internal traceability link of each level module;
[0007] According to the object association relationship between modules at each level, build external traceability links between modules at each level;
[0008] An event monitoring system is constructed based on the multiple hierarchical modules, the internal traceability link and the external traceability link.
[0009] In a second aspect, an embodiment of the present application provides an event monitoring method, including:
[0010] The events of the target object are monitored through an event monitoring system; the event monitoring system is constructed by the event monitoring system construction method provided by the first aspect of the embodiment of the present application.
[0011] In a third aspect, an embodiment of the present application provides a device for constructing an event monitoring system, including:
[0012] A hierarchical construction module, used to construct a plurality of hierarchical modules corresponding to the object to be monitored according to a plurality of resource attributes of the object to be monitored; the resource attributes include cloud product attributes, and the plurality of hierarchical modules include cloud product layers corresponding to a plurality of cloud products;
[0013] The internal link construction module is used to construct the internal traceability links of each level module according to the object association relationship within each level module;
[0014] The external link construction module is used to construct the external traceability links between modules at each level according to the object association relationship between modules at each level;
[0015] A system building module is used to build an event monitoring system based on the multiple hierarchical modules, the internal tracing link and the external tracing link.
[0016] In a fourth aspect, an embodiment of the present application provides an event monitoring device, including:
[0017] The monitoring module is used to monitor the events of the target object through an event monitoring system; the event monitoring system is constructed by the event monitoring system construction method provided by the first aspect of the embodiment of the present application.
[0018] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory, wherein the processor implements any one of the methods provided in the embodiment of the present application when executing the computer program.
[0019] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, any one of the methods provided in the embodiment of the present application is implemented.
[0020] Compared with the prior art, this application has the following advantages:
[0021] The technical solution provided in the embodiment of the present application can perform a full-link design for the monitoring function of the event monitoring system by constructing multiple hierarchical modules and internal traceability links and external traceability links corresponding to each hierarchical module, thereby forming a troubleshooting track, reducing the complexity of event tracing and troubleshooting, and enabling the constructed event monitoring system to cover resource objects with different resource attributes, thereby expanding the scope of resource objects that can be monitored.
[0022] The technical solution provided in the embodiment of the present application can integrate the monitoring functions of different cloud products into the same event monitoring system by constructing a cloud product layer including corresponding multiple cloud products, and concentrate the monitoring entrances in the same event monitoring system to solve the problems of user's monitoring link fragmentation and monitoring entrance dispersion, realize integrated monitoring and operation and maintenance, reduce the user's jumping between multiple cloud products, effectively improve the intelligence of event monitoring and operation and maintenance products, improve the efficiency of monitoring and operation and maintenance and the user's autonomous monitoring ability, and thus improve the user's interactive experience.
[0023] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the multiple drawings represent the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments according to the present application and should not be regarded as limiting the scope of the present application.
[0025] Figure 1 A flowchart of a method for constructing an event monitoring system provided in this application;
[0026] Figure 2 This is a schematic diagram of the architecture of an event monitoring system in an embodiment of the present application;
[0027] Figure 3 A schematic diagram of matching an event monitoring system with cloud form and management authority in an embodiment of the present application;
[0028] Figure 4 This is a schematic diagram of an event level identification in an embodiment of the present application;
[0029] Figure 5 A schematic diagram of determining the influence range of an abnormal object in an embodiment of the present application;
[0030] Figure 6 A schematic diagram of switching between the display interface of the upstream level module and the display interface of the downstream level module in an embodiment of the present application;
[0031] Figure 7 A schematic diagram of a panoramic interface in an embodiment of the present application;
[0032] Figures 8a to 8c This is a schematic diagram of the hierarchical interface of the business layer in the embodiment of the present application;
[0033] Figure 9a to Figure 9b This is a schematic diagram of the hierarchical interface of the application layer in the embodiment of the present application;
[0034] Fig.10 A schematic diagram of the hierarchical interface of the cloud service instance layer in an embodiment of the present application;
[0035] Figures 11a to 11c This is a schematic diagram of the hierarchical interface of the cloud product layer in the embodiment of the present application;
[0036] Figures 12a to 12cThis is a schematic diagram of the hierarchical interface of the infrastructure layer in an embodiment of the present application;
[0037] Fig.13 This is a schematic diagram of a prompt of an event message on a computer in an embodiment of the present application;
[0038] Fig.14 This is a schematic diagram of a prompt of an event message on a mobile phone in an embodiment of the present application;
[0039] Fig.15 This is an example diagram of the first prompt message in an embodiment of the present application;
[0040] Fig.16 This is an example diagram of the second prompt message in the embodiment of the present application;
[0041] Fig.17 This is another example diagram of the second prompt message in the embodiment of the present application;
[0042] Fig.18 This is a schematic diagram of outputting abnormal information and operation and maintenance information in an embodiment of the present application;
[0043] Fig.19 A schematic diagram of a structural framework of a device for constructing an event monitoring system provided in an embodiment of the present application; and
[0044] Fig. 20 A schematic diagram of the structural framework of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0045] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the concept or scope of the present application. Therefore, the drawings and descriptions are considered to be exemplary in nature and not restrictive.
[0046] First, some technical terms involved in the embodiments of the present application are introduced as follows:
[0047] Observability: It is used to describe and measure the ability of the internal state of the system. Common means are to collect indicators, logs, and track trajectories to detect problems in a timely manner. It can also be used to describe the real-time monitoring needs of real-time, diverse, dynamic, and continuously updated businesses, as well as to provide comprehensive and deterministic system observation capabilities. It can effectively solve the problem tracing in complex links, understand the interdependencies of events, and locate the root causes of problems.
[0048] Event alert: refers to the information and notification of business system failure caused by major unexpected interruptions or serious failures of IT (Internet Technology) services or CI (config item) configuration items.
[0049] Existing event monitoring products are isolated from each other and cannot be linked. Each event monitoring product can monitor a limited number of resource objects. Different resource objects need to be monitored by different event monitoring products. There is a lack of global event monitoring products. Users have to jump to multiple event monitoring products to monitor different resource objects. The links for discovering, locating and solving problems are too long. When solving problems, multiple event monitoring products need to cooperate with each other. The efficiency of monitoring and operation and maintenance is low, the user's monitoring link is fragmented, and the interactive experience is poor.
[0050] In order to solve the above problems, the embodiment of the present application provides a solution for event monitoring. To facilitate understanding of the technical solution of the embodiment of the present application, the related technologies of the embodiment of the present application are described below. The following related technologies can be combined arbitrarily with the technical solution of the embodiment of the present application as optional solutions, and they all belong to the protection scope of the embodiment of the present application.
[0051] like Figure 1 As shown, an embodiment of the present application provides a method 100 for constructing an event monitoring system, which may include the following steps: S101, constructing multiple hierarchical modules corresponding to the object to be monitored (i.e., the resource object to be monitored) according to multiple resource attributes of the object to be monitored, the resource attributes may include cloud product attributes, and the multiple hierarchical modules may include cloud product layers corresponding to multiple cloud products; S102, constructing internal traceability links of each hierarchical module according to the object association relationship within each hierarchical module (i.e., the association relationship between resource objects within each hierarchical module); S103, constructing external traceability links between modules of each hierarchical level according to the object association relationship between modules of each hierarchical level (i.e., the association relationship between resource objects of different hierarchical levels); S104, constructing an event monitoring system according to multiple hierarchical modules, the internal traceability links of each hierarchical module and the external traceability links of each hierarchical module.
[0052] The above-mentioned construction method 100 provided in the embodiment of the present application can perform a full-link design for the monitoring function of the event monitoring system by constructing multiple hierarchical modules and internal traceability links and external traceability links corresponding to each hierarchical module, thereby forming a full-link troubleshooting track, reducing the complexity of event tracing and troubleshooting, and enabling the constructed event monitoring system to cover resource objects with different resource attributes, expand the scope of monitorable resource objects, and achieve global monitoring.
[0053] The above-mentioned construction method 100 provided in the embodiment of the present application can integrate the functions of monitoring different cloud products into the same event monitoring system by constructing a cloud product layer including corresponding multiple cloud products, and concentrate the monitoring entrances in the same event monitoring system to solve the problems of user's monitoring link fragmentation and monitoring entrance dispersion, realize integrated monitoring and operation and maintenance, reduce the user's jumping between multiple event monitoring products, effectively improve the intelligence of event monitoring and operation and maintenance products, improve the efficiency of monitoring and operation and maintenance and the user's autonomous monitoring ability, and thus improve the user's interactive experience.
[0054] In one embodiment, the resource attributes of the object to be monitored may also include business attributes, application attributes, instance attributes, cloud product attributes and infrastructure attributes. Correspondingly, the multiple hierarchical modules constructed based on resource attributes may also include: business layer, application layer, cloud service instance layer and infrastructure layer.
[0055] The objects to be monitored with business attributes may include the following: business (indicating matters that need to be handled by various industries, such as technology management, development, etc.), business scenarios in business (such as fund custody, payment, etc.), and business transactions in business scenarios (such as transaction volume). The objects to be monitored with application attributes may include application systems that can realize business, applications that form application systems, deployment clusters that can support applications, cloud instances in deployment clusters, etc. The deployment cluster may be a collection of multiple instances in a certain geographical area. The objects to be monitored with instance attributes may include resource clusters and multiple cloud instances in resource clusters. Cloud instances may be any instance of cloud servers ECS (Elastic Compute Service), VPC (Virtual Private Cloud), SLB (Server Load Balancer), etc.; the objects to be monitored with cloud product attributes may include cloud products, cloud instances in cloud products, and machine clusters that can support cloud instances. Cloud products can include: IaaS (Infrastructure as a Service) layer network, storage, elastic computing and other products, PaaS (Platform as a Service) middleware, database and other products, enterprise management and operation products; machine clusters can be a collection of machines with service software deployed, thus providing both hardware and software resources. Objects to be monitored with infrastructure attributes can include physical facilities such as computer rooms, servers, and network equipment (such as switches).
[0056] In the hierarchical modules, the business layer can include a large number of objects with business attributes, the application layer can include a large number of objects with application attributes, the cloud service instance layer can include a large number of objects with instance attributes, the cloud product layer can include a large number of objects with cloud product attributes, and the infrastructure layer can include multiple objects with infrastructure attributes. The construction of five hierarchical modules from the business layer to the infrastructure layer can incorporate a large number of objects with different resource attributes into the monitoring system, and build a multi-level, full-link event monitoring system. This hierarchical event monitoring system helps to improve the efficiency of monitoring and operation and maintenance, and achieve the fault handling goal of 1-10-30 (1 minute discovery-10 minutes response, 30 minutes resolution) to better suit the scenario of private cloud, and can also achieve the fault handling goal of 1-5-10 (1 minute discovery-5 minutes response-10 minutes resolution) to better suit the scenarios of public cloud and industry cloud, thereby solving the problems of long links in discovering problems, locating problems, and solving problems, and long fault handling time in existing event monitoring products, and better meet the needs of emergency handling of events. Based on the above five hierarchical modules, the above construction method 100 can construct an integrated monitoring system of cloud products + applications.
[0057] In the embodiment of the present application, there may be a dependency relationship between modules at each level, and the external traceability links between modules at each level and the vertical links between modules at each level (in terms of Figure 2 In one example, Figure 2 As shown, each level module may include the business layer, application layer, cloud service instance layer, cloud product layer and infrastructure layer. The business layer may rely on the application layer for implementation, the application layer may rely on the cloud service instance layer or the cloud product layer for implementation, the cloud service instance layer may rely on the cloud product layer for implementation, and the cloud product layer may rely on the infrastructure layer for implementation. Thus, the external traceability link may be a link for troubleshooting abnormalities in the order of the business layer, application layer, cloud service instance layer, cloud product layer and infrastructure layer.
[0058] In the embodiment of the present application, at least part of the hierarchical modules may include multiple sub-levels with dependencies, and the internal traceability links of the part of the hierarchical modules and the horizontal (in terms of Figure 2 In one example, Figure 2As shown, the business layer may include three sub-levels: business, business scenario, and business transaction. The business is composed of multiple business scenarios, and the business scenario is composed of multiple business transactions. Therefore, the business depends on the business scenario, and the business scenario depends on the business transaction. The internal traceability link of the business layer can be a link for troubleshooting abnormalities in the order of business, business scenario, and business transaction; the application layer may include four sub-levels: application system, application, deployment cluster, and cloud instance. The application system is composed of multiple applications, and the application is implemented by the deployment cluster, which is composed of multiple cloud instances. Therefore, the application system depends on the application, the application depends on the deployment cluster, and the deployment cluster depends on the cloud instance. The internal traceability link of the application layer can be a link for troubleshooting abnormalities in the order of application system, application, deployment cluster, and cloud instance; the cloud service instance layer may include two sub-levels: resource cluster and cloud instance. The resource cluster is composed of multiple cloud instances, so the resource cluster depends on the cloud instance. The internal traceability link of the cloud service instance layer can be a link for troubleshooting anomalies in the order of resource clusters and cloud instances; the cloud product layer can include three sub-levels: cloud products, cloud instances, and machine clusters. Cloud products are composed of multiple cloud instances, and cloud instances are implemented by multiple machine clusters. Therefore, cloud products depend on cloud instances, and cloud instances depend on machine clusters. The internal traceability link of the cloud product layer can be a link for troubleshooting anomalies in the order of cloud products, cloud instances, and machine clusters; the infrastructure layer can include three sub-levels: computer room, cabinet, and machine (server or network equipment). The computer room is composed of multiple cabinets, and the cabinet is composed of multiple machines. Therefore, the computer room depends on the cabinet, and the cabinet depends on the machine. The internal traceability link of the basic equipment layer can be a link for troubleshooting anomalies in the order of computer room, cabinet, and equipment.
[0059] In one embodiment, in the above step S104, an event monitoring system is constructed based on multiple hierarchical modules, internal traceability links of each hierarchical module, and external traceability links of each hierarchical module, including: determining the cloud form type of the event monitoring system to be constructed based on user demand information; selecting a hierarchical module that conforms to the cloud form type from each hierarchical module, and constructing an event monitoring system including the selected hierarchical module, the internal traceability link corresponding to the selected hierarchical module, and the external traceability link corresponding to the selected hierarchical module.
[0060] User demand information may include the required cloud form information provided by the user, such as public cloud, private cloud, industry cloud, etc., and may also include at least one type of information such as the user's organizational structure, industry field, business scale, and the type of cloud service required by the user. The organizational structure may include institutions, enterprises, etc. The industry field may include finance, medical care, Internet, education and other fields. The cloud service type may include one-to-one service, high-security service, etc.
[0061] A public cloud can be a cloud service for the general public; a private cloud can be a cloud service that provides customization and network isolation for specific users; an industry cloud can be a cloud service form with industry characteristics built based on the private cloud enterprise edition product, and can provide cloud services to various industries, related organizations or the public.
[0062] In one example, determining the cloud morphology type of the event monitoring system to be constructed based on user demand information may include: determining the cloud morphology type of the event monitoring system to be constructed based on the required cloud morphology information provided by the user; for example, if the cloud morphology type required by the user is a public cloud, then the cloud morphology type of the event monitoring system to be constructed may be determined to be a public cloud scenario; if the cloud morphology type required by the user is a private cloud, then the cloud morphology type of the event monitoring system to be constructed may be determined to be a private cloud scenario.
[0063] In another example, determining the cloud form type of the event monitoring system to be constructed based on user demand information may include: judging the cloud form type suitable for the user based on at least one type of information such as the user's organizational structure, industry field, business scale, cloud service type, and so on, and then determining the cloud form type of the event monitoring system to be constructed. For example, if the user is a public institution or an enterprise with a large business scale (i.e., a large enterprise), has high requirements for data and network security, and needs one-to-one service, it can be judged that it is more suitable for a proprietary cloud. If the user is an enterprise with a small business scale (i.e., a small and medium-sized enterprise) or an individual developer, it can be judged that it is more suitable for a public cloud. For users in a specific industry field (e.g., the financial field), it can be applied to an industry cloud. This judgment method is only used as an example. In actual applications, the cloud form type required by the user can be judged based on actual conditions, such as the data objects that the user is more concerned about.
[0064] In one example, if Figure 3 As shown, the objects to be monitored include five hierarchical modules, namely, the business layer, the application layer, the cloud service instance layer, the cloud product layer and the infrastructure layer. Among the hierarchical modules, a hierarchical module that meets the cloud form type of the event monitoring system to be constructed is selected, and an event monitoring system including the selected hierarchical module, the internal tracing link corresponding to the hierarchical module and the external tracing link corresponding to the hierarchical module is constructed. The following situations can be included: If the cloud form type of the event monitoring system to be constructed is a proprietary cloud, an event monitoring system including the above five hierarchical modules, the internal tracing links corresponding to the five hierarchical modules and the external tracing links corresponding to the five hierarchical modules can be constructed. The event monitoring system can be applicable to proprietary clouds, and the architecture of the five hierarchical modules can cover all objects to be monitored from the business layer to the infrastructure layer, realizing full-data, integrated monitoring; if the cloud form type of the event monitoring system to be constructed is an industry cloud or a public cloud, an event monitoring system including three hierarchical modules, namely, the business layer, the application layer and the cloud service instance layer, can be constructed to realize lightweight quantity monitoring.
[0065] Based on this method, flexible and pluggable combinations of modules at all levels can be achieved, and the event monitoring system can be customized. The corresponding event monitoring system can be customized according to specific user needs. The original hierarchical modules are highly versatile and can be flexibly split and reorganized. Through customization, they can adapt to the needs of various cloud forms, and then adapt to the different monitoring service needs of different users such as enterprise and agile users.
[0066] In one embodiment, the above-mentioned construction method 100 may also include: setting multiple administrator candidates with different management permissions; the management permissions are used to manage a specified part or all of the hierarchical modules. The event monitoring system constructed by the embodiment of the present application may also include multiple administrator candidates.
[0067] The administrator candidate may include the administrator's role name and the administrator's management permissions. Figure 3 , the objects to be monitored include five hierarchical modules, namely, the business layer, application layer, cloud service instance layer, cloud product layer and infrastructure layer. The following six administrators can be set, and the role names are respectively manager, operation and maintenance expert, screen monitor, application operation and maintenance personnel, instance operation and maintenance personnel and system operation and maintenance personnel. Among them, the manager has the highest global management authority, that is, the authority to view, operate and configure all hierarchical modules, the operation and maintenance expert has partial global management authority, that is, the authority to view and operate all hierarchical modules, and the screen monitor has partial global management authority, that is, the authority to view all hierarchical modules; application operation and maintenance personnel, instance operation and maintenance personnel and system operation and maintenance personnel all have local management authority, among which application operation and maintenance personnel have the authority to view and operate the business layer and application layer, instance operation and maintenance personnel have the authority to view and operate the cloud service instance layer, and system operation and maintenance personnel have the authority to view and operate the cloud product layer and infrastructure layer. Figure 3 The role names and management permissions shown are for example purposes only. You can set other role names and permission ranges based on actual needs.
[0068] The setting of administrator candidates with different management permissions is conducive to a clear interface of the role functions and management permissions of different administrators, ensuring data security, and at the same time meeting the management needs of users. Users can call administrator candidates according to needs and assign administrator candidates to actual managers. Actual managers can implement corresponding management based on the management permissions in the administrator candidates. Users do not need to set role names and management permissions, and can directly call them, which can improve user management efficiency.
[0069] In one embodiment, the construction method 100 may further include: setting a plurality of event level identifiers for marking the urgency of the event; the event level identifier may include information of at least one element of color, text, shape, and sound. The setting of a plurality of event level identifiers may meet the marking needs of the user, and the user may call the corresponding event level identifier for marking according to the needs.
[0070] In an example, the number of event level identifiers can be 3 to 10, which can meet the labeling needs of most private cloud users in the current market.
[0071] In one example, the event level identifier used to mark the emergency procedures of different events can be represented by different information of the same element, for example, different colors of event level identifiers are used to represent different event urgency levels, different shapes are used to represent different event urgency levels, different texts are used to represent different event urgency levels, and different frequencies or loudness of sounds are used to represent different event urgency levels; the above-mentioned same element can be one element or multiple elements, for example, only one of color, text, shape and sound can be used to represent the urgency level of the event, or a combination of any two or more of the elements of color, text, shape and sound can be used to represent the emergency procedures of the event, such as a combination of color and text, a combination of color, text and shape, a combination of color and sound, etc.
[0072] The text used to form the event level identification can be in any language and format, such as Chinese, English, numbers, etc. The specific content of the text can be customized by the user during the use stage, or the default content can be preset when setting the event level identification. Figure 4 Users can customize the specific content of Chinese content as "Major, Urgent, Serious, Important", and the specific content of English content as "Grave, Critical, Warning, Info", and the default content can be "P1, P2, P3, P4". Figure 4 The several event level identifiers shown are only examples, and the corresponding identification content can be customized according to actual needs, such as the scope and degree of impact of the event / fault on the business application, thereby forming a standardized classification management solution. In one example, administrator candidates or event level identifiers can be set based on user input.
[0073] Based on the same technical concept, an embodiment of the present application also provides an event monitoring method, which may include: monitoring events of a target object through an event monitoring system; the event monitoring system may be constructed by any one of the construction methods of the event monitoring system provided in the embodiment of the present application.
[0074] The event monitoring system may include multiple hierarchical modules, internal traceability links of each hierarchical module, and external traceability links between each hierarchical module. The event monitoring system can monitor the operating status of the target objects corresponding to each hierarchical module and globally perceive the events of the target objects.
[0075] In one embodiment, the event monitoring method may further include: when an abnormal event exists in the event of the target object being monitored, the target objects corresponding to each level module in the event monitoring system are checked layer by layer according to the internal traceability link and the external traceability link in the event monitoring system to find the abnormal object in each target object. The abnormal object may be the target object of the abnormal event.
[0076] Reference Figure 2 For example, the event monitoring system can include five hierarchical modules: business layer, application layer, cloud service instance layer, cloud product layer, and infrastructure layer. First, based on the internal traceability link of the business layer (such as Figure 2 The target object corresponding to the business layer is checked (as shown by the arrow inside the business layer in the figure). The internal traceability link of the business layer is as follows: Figure 2 As shown by the arrow in the business layer, based on the traceability link, we can first check each business in the business layer to find the business with abnormal events, then check each business scenario in the business with abnormal events to find the business scenario with abnormal events, and then check the business transactions in the business scenario with abnormal events to find the business transactions with abnormal events.
[0077] After finding the business transaction with abnormal events, the external traceability link between the business layer and the application layer (such as Figure 2 The arrows between the business layer and the application layer in Figure 1) and the internal traceability links of the application layer (such as Figure 2 The application layer is checked (as shown by the arrow inside the application layer in the figure). Based on the external traceability link and the internal traceability link, each application system in the application layer can be checked first to find the application system with abnormal events. Then, the applications in the application system with abnormal events can be checked to find the applications with abnormal events. Then, each deployment cluster corresponding to the application with abnormal events can be checked to find the deployment cluster with abnormal events.
[0078] After finding the deployment cluster with abnormal events, you can continue to trace the source in two ways: Method 1: Check the cloud instances in the deployment cluster based on the internal traceability link of the application layer to find the cloud instances with abnormal events, and then trace the source based on the external traceability link between the application layer and the cloud product layer (i.e. Figure 2 Link 1 in the above example directly checks the machine cluster where the cloud instance is deployed to find the machine cluster with abnormal events. Method 2 is based on external traceability between the application layer and the cloud service instance layer (i.e. Figure 2 Link 2 in the cloud service instance layer is used to check the cloud instances in the cloud service instance layer to find the cloud instances with abnormal events, and then the external traceability link between the cloud service instance layer and the cloud product layer (i.e. Figure 2 In link 3), check each machine cluster where the cloud instance is deployed to find the machine cluster with abnormal events.
[0079] After finding the machine cluster with abnormal events, we can use the external traceability link between the cloud product layer and the infrastructure layer (such as Figure 2 The infrastructure layer is checked based on the internal traceability link of the infrastructure layer (as shown in the arrow between the cloud product layer and the infrastructure layer). Figure 2 (as shown by the arrow inside the infrastructure layer in the figure), we can first check each computer room in the infrastructure layer to find the computer room with abnormal events, then check each cabinet in the computer room with abnormal events to find the cabinet with abnormal events, and then check each machine in the cabinet with abnormal events to find the machine that caused the abnormal event.
[0080] Through the above method, it is possible to check layer by layer from the business layer to the infrastructure layer to determine whether any abnormalities have occurred in the target objects at each layer.
[0081] In one embodiment, the above-mentioned event monitoring method may also include: determining the influence range (or influence surface) of each abnormal object based on the association relationship between the abnormal objects; determining the event level of each abnormal object based on the influence range; and outputting an event level identifier associated with the event level.
[0082] In one example, Figure 2 Taking an abnormal object of the cloud product layer shown as an example, it can be determined whether the abnormal object is associated with the abnormal object corresponding to the upstream infrastructure layer, and whether it is associated with the abnormal object corresponding to the downstream application layer, and the number of associated upstream abnormal objects and downstream abnormal objects. The impact range of the abnormal object on the abnormal objects corresponding to the adjacent level modules can be determined based on the size of the number. The larger the number, the larger the impact range, and the higher the corresponding event level.
[0083] In another example, Figure 2Taking a certain abnormal object of the cloud product layer shown as an example, it can be determined whether the abnormal object is associated with the abnormal objects corresponding to the upstream and downstream level modules (upstream level modules such as the infrastructure layer, downstream level modules such as the application layer), and whether it is associated with the abnormal objects corresponding to the same level module (i.e., the cloud product layer). The number of associated upstream abnormal objects, downstream abnormal objects, and abnormal objects corresponding to the same level module is how many. According to the size of the number, the impact range of the abnormal object on the abnormal objects corresponding to the adjacent level modules can be determined. The larger the number, the larger the impact range, and the higher the corresponding event level. The above process of determining the impact range from upstream to downstream can be carried out through Figure 5 The interface shown is displayed to increase the observability of the impact range analysis process, such as Figure 5 The interface shown can also display the tracing process from downstream to upstream.
[0084] Reference Figure 2 For example, the present application embodiment can realize top-down tracing and bottom-up impact range analysis, that is, from Figure 2 The top level module starts the pearl layer traceback, from Figure 2 The lowest level module starts to analyze the impact range layer by layer.
[0085] In one example, outputting an event level identifier associated with the event level may include the following two methods: Method 1, selecting an identifier that matches the impact range of the abnormal object from multiple event level identifiers built into the event monitoring system and outputting the identifier. For example, when the event level identifier built into the event monitoring system is a combination of multiple elements, Method 1 may be used to output the event level identifier. Method 2, selecting multiple event level identifiers that match the impact range of the abnormal object from multiple event level identifiers built into the event monitoring system and combining them, and outputting the combined event level identifier. For example, when the event level identifier built into the event monitoring system includes one element, Method 2 may be used to output the combined event level identifier.
[0086] In one example, the output method of the event level identification includes at least one of the following: output in the form of a visual image through a display device, and output in the form of sound through an audio output device. The appropriate output method can be determined according to the elements included in the event level identification, and the output method based on the visual image is conducive to achieving event monitoring with high observability.
[0087] In one embodiment, the above-mentioned event monitoring method may also include: in the process of layer-by-layer investigation, at least one of the target objects and traceability paths corresponding to the investigated hierarchical modules is displayed in real time through a visual interface; the traceability path displayed in real time is a part of the internal traceability links of each hierarchical module and the external traceability links between each hierarchical module.
[0088] The target objects and traceability paths corresponding to the hierarchical modules being checked are displayed in real time through a visual interface, which allows users to observe the troubleshooting process in real time, observe the mutual impact on abnormal objects, and facilitate operation and maintenance.
[0089] Visualization can include panoramic interface and hierarchical interface. The panoramic interface can be used to display the target objects corresponding to all hierarchical modules and the association relationship between each target object. The hierarchical interface can display the target objects corresponding to a certain hierarchical module and the association relationship between each target object. The hierarchical interface corresponding to different hierarchical modules can be switched through the cross-level entrance. Figure 6 The schematic diagram shows the switching principle between the display interface of an upstream level module and the display interface of a downstream level module. Compared with the display interface of the downstream level module, the display interface of the upstream level module can display the event level distribution of all objects. Figure 6 , the display interface of the downstream level module can display the event level distribution of the subset objects in the full object, and the display interface of the upstream level module can also be displayed in the event data panel (such as Figure 6 The event data panel of a part of the full objects can be displayed in the platform layer event data panel shown in the figure. The display interface of the downstream level module can also be displayed in the event data panel (such as Figure 6 The object layer event data panel shown in the figure displays the event data of a part of the objects in the subset object. The event data panel can be superimposed on the initial event level distribution interface. Figure 6 When switching between the display panel of the upstream module and the display interface of the downstream module, you can use Figure 6 Switch through the cross-level entries shown.
[0090] Figure 7 A schematic diagram of a panoramic interface is shown, in which a point is taken as the center, and the business layer, application layer, and cloud product layer are shown from the inside to the outside. Figure 7 Cloud products) and infrastructure layers ( Figure 7 The sub-levels in each level module, the target objects corresponding to each level module, and the overall event level distribution are shown in the form of dots. Figure 7 The Security Department, Health and Safety Office, System Department, and General Office are all examples of departments responsible for a certain business at the business level. Figure 7 In the panoramic interface, the event data panel on the right can also display the number of today's events, the number of serious events, the number of events being processed, the latest event information, etc. Figure 7 In the panoramic interface shown, you can intuitively observe the event levels of the target objects in each level module, and switch to the interface of each target object through the cross-level entrance. In one example, you can click Figure 7 Click the dot of "Comprehensive Office" in the pop-up window with the business name, event ID (Identity Document) data, event level and business transaction data. This window is the cross-level entrance to the "Comprehensive Office". Click "Enter" in the window to enter the display interface of the "Comprehensive Office". Figure 8a shown.
[0091] Figures 8a to 8c It shows three levels of interfaces of the business layer. Figure 8a Examples of various business departments in the business layer and the event level distribution of various business scenarios in the "General Office" business are shown as examples. "Science and Technology Department", "Life Adjustment Office", "Application Department", "System Department", "Development Center" and so on are all examples of departments responsible for a certain business in the business layer. Figure 8a You can intuitively observe which business scenario event level is higher in the "General Office" business, and then switch to the association interface between this business scenario and other business scenarios, such as Figure 8b As shown. Figure 8b You can visually observe the relationship between a business scenario with a higher event level (such as "funds custody") and other business scenarios. The relationship is represented by a line, and then you can switch to the display interface of the "funds custody" business scenario. Figure 8c As shown. Figure 8c You can visually observe which business transaction has a higher event level in a certain business scenario, and you can use the cross-level entry ( Figure 8c (not shown) can be switched to Figure 9a The display interface of the application layer is shown in Figure 1. Figures 8a to 8c The hierarchical interface of the business layer can also display the monitoring coverage, health, number of business scenarios, number of abnormal business scenarios, transaction amount, transaction success rate, event resolution rate, event list and other information of the business layer in the event data panel on the right.
[0092] Figure 9a to Figure 9b Two levels of interface of application layer are shown. Figure 9a The event level distribution of each application system in the application layer and each application in each application system is shown. Figure 9a You can intuitively observe the application systems and applications with higher event levels, as well as the associations between applications with higher event levels. By drilling down on the page, you can switch to a schematic diagram of the association between a certain application and the deployment cluster, such as Figure 9b As shown, Figure 9b Region-cn-shanghai and Region-cn-beijing in the figure represent two deployment clusters divided by geographical range, and their relationship can be represented by connecting lines. Figure 9bIn the cross-level entry ( Figure 9b ) can be switched to Fig.10 The display interface of the cloud service instance layer shown in the figure or Figures 11a-11c The display interface of the cloud product layer is shown. Figure 9a to Figure 9b The hierarchical interface of the application layer can also display monitoring coverage, number of applications, number of abnormal applications, health, number of events, event resolution rate, event list, cloud product type, number of releases in the past week, number of resource instances, business impact, instance status and other information in the event data panel on the right.
[0093] Fig.10 A hierarchical interface of the cloud service instance layer is shown, which shows the resource cluster of the cloud service instance layer (i.e. Fig.10 The event level distribution of cloud instances in each resource cluster is Fig.10 You can intuitively observe resource clusters and cloud instances with higher event levels through cross-level portals ( Fig.10 ) can be switched to Fig.11b The display interface of the cloud instance is shown in Figure 1. Fig.10 ,The hierarchical interface of the cloud service instance layer can also display the alarm status of the cloud instance, the number of ,deployed clusters, the number of machines included in the cloud instance, the number of abnormal machines, the ,working service roles, the management service roles, the component allocation, the event list and other information in the ,event data panel on the right.
[0094] Figures 11a to 11c It shows three levels of interfaces of cloud product layer. Fig.11a The event level distribution of each cloud product in the cloud product layer and the cloud instances in each cloud product is shown. Fig.11a You can intuitively observe the cloud instances with higher event levels and the associations between cloud instances with higher event levels. You can switch to the display interface of a cloud instance by drilling down on the page, such as Fig.11b As shown, it can be switched to Fig.11c The display interface of the machine cluster (e.g., a computer room) shown in FIG. 1 can display the association relationship between the cloud instance and the IDC (Internet Data Center) computer room. The association relationship can be represented by a line, through the cross-level entrance ( Fig.11c ) can be switched to Fig.12a The display interface of the infrastructure layer is shown. Figures 11a to 11cThe hierarchical interface of the cloud product layer can also display the monitoring coverage, number of cloud products, number of abnormal products, health, Top 5 abnormal cloud products, number of pending events, event resolution rate, event list, alarm status of cloud instances, number of deployed clusters, number of machines included in the cloud instance, number of abnormal machines, working service roles, management and control service roles, component allocation and other information in the event data panel on the right.
[0095] Figures 12a to 12c The three levels of interfaces of the infrastructure layer are shown. Fig.12a The event level distribution of the cabinets in each computer room in the infrastructure layer is shown. A to F are the numbers of the cabinets in the computer room in one direction, and 01 to 06 are the numbers of the cabinets in the computer room in the other direction. The numbers in both directions point to a specific cabinet. For example, A01 represents a cabinet, and A02 represents another cabinet. Fig.12a You can intuitively observe the cabinets with higher event levels. You can switch to the display interface of a cabinet by drilling down on the page, such as Figure 12b As shown. Figure 12b You can intuitively observe the servers and network devices with higher event levels in a cabinet, as well as the association between servers and network devices. Figure 12b The ASW (access layer switch) in the network is a type of network device. Figure 12b In the interface shown, you can click the "Network" icon at the top to switch to the following Fig.12c The display interface of the network device shown in the figure is Fig.12c The relationship between different network devices can be intuitively observed. The relationship is represented by lines. Different network devices include ISW (an industrial-grade switch), CSW (intranet access switch), DSW (distribution layer switch), ASW, LSW (integrated access switch) and HSW (another working-level switch). Figure 12b In the interface shown, you can click the "Server" icon at the top to switch to the following Figure 12b The display interface shown. Fig.12a The interface shown can also display the alarm status of a certain computer room, the number of cabinets included, the number of machines included, the number of abnormal machines, capacity water level, product distribution, event list, etc. in the event data panel on the right. Figure 12b It can also display information such as the server IP (Internet Protocol), the cluster to which the server belongs, the product to which the server belongs, capacity level, service status, event list, etc. Fig.12c It can also display information such as network device name, network device role, network device IP, network device status, network traffic, number of network monitoring alarms, network monitoring alarm items, etc.
[0096] Reference Figures 8a to 12c Each level of the interface can also display the troubleshooting progress at the bottom and highlight the current troubleshooting stage.
[0097] Reference Figures 7 to 12c Compared with the traditional way of displaying visual content through list pages and detail pages, the panoramic interface and each level interface in the embodiment of the present application can present multi-dimensional data in the same display interface, integrating the data indicators corresponding to each level module. Users can view the relationship between each target object without switching repeatedly. They can start from the display interface of the downstream level module and view it layer by layer to the display interface of the upstream level module, which can realize the monitoring visualization of complex distributed systems.
[0098] In one embodiment, the above-mentioned event monitoring method may also include: when an abnormal event occurs in the events monitored for the target object, sending an event message for prompting the abnormality to a first terminal device; the first terminal device is a terminal device of an administrator who has management authority over the abnormal object.
[0099] Sending event messages to the terminal devices of administrators who have management rights to the abnormal objects can prompt the administrators to handle the abnormal objects in time, realize event alarms, and facilitate administrators to work on the move and respond quickly to avoid the above abnormalities causing greater impact. The first terminal device can be any device such as a mobile phone, computer, tablet computer, etc. Fig.13 A schematic diagram showing the prompt of the event message on the computer side is shown. Fig.14 The following figure shows the prompt diagram of the event message on the mobile phone. The specific content of the event message can be set according to actual needs. Fig.13 An example of this could be "Event warning pending, an event warning has occurred in the payment service, please handle it in time!", refer to Fig.14 An example of this could also be "[Operation and Maintenance of pending events] There is a "payment business failure" event assigned to you, please handle it as soon as possible!".
[0100] The administrator who receives the event message can be any administrator of the event monitoring system, that is, the embodiment of the present application can be sent to any one or more administrators of the event monitoring system with management authority, so as to realize cross-system monitoring and operation and maintenance, realize distribution perception, enable different event monitoring systems to be linked, realize multi-role collaboration, and improve the overall monitoring and operation and maintenance efficiency.
[0101] In one embodiment, the event monitoring method may further include: when an abnormal event is detected in the event of the target object, sending a first prompt message for prompting operation and maintenance to the first terminal device, and the specific method of sending the prompt message may be any one of SMS notification, interactive software notification (such as DingTalk notification), and telephone call. Fig.15The interface shown displays candidate options for operation and maintenance notification methods and candidate options for operation and maintenance handlers (i.e., administrators) for users to select or confirm. After the administrator selects or confirms the specific operation and maintenance notification method and operation and maintenance handler, the operation and maintenance notification is sent to the terminal device of the operation and maintenance handler.
[0102] In one embodiment, referring to Fig.16 and Fig.17 , the event monitoring method may further include: when an abnormal event exists in the event of the target object being monitored, sending a second prompt message to the first terminal device for prompting whether to jump to a certain operation and maintenance system, and jumping to the corresponding operation and maintenance system based on the administrator's choice, for example Fig.16 and Fig.17 Normandy (an application operation and maintenance system) and ASO (a cloud product operation and maintenance system) in it can link the operation and maintenance systems, which helps to perform rapid operation and maintenance.
[0103] In one example, the first prompt message or the second prompt message may be sent in response to a trigger operation of a user on an icon of the hierarchical interface.
[0104] In another embodiment, the event monitoring method 100 may further include: analyzing data indicators of abnormal objects to determine the cause of the abnormal event.
[0105] The data indicators of abnormal objects can include Figures 7 to 12c The information shown in the event data panel on the right can be analyzed based on data indicators to determine the specific cause of the abnormal event, which helps to locate the fault. In one example, the event message sent to the first terminal device may include the cause of the abnormal event so that the administrator can quickly identify the cause of the abnormality and then perform targeted operation and maintenance. Data indicators can be obtained from event logs, making analysis based on data indicators more accurate.
[0106] In one embodiment, the event monitoring method may further include: after the operation and maintenance for the abnormality is completed, in response to the received replay request, the event monitoring system outputs the abnormality information and operation and maintenance information of the abnormal object.
[0107] The review request can be input by the administrator. Depending on the specific object involved in the input review request, the event monitoring system can Fig.18 The display interface shown shows the abnormal information and operation and maintenance information of all nodes, that is, all abnormal objects, and can also show the abnormal information and operation and maintenance information of some nodes, that is, some abnormal objects. Fig.18, the exception information can include the event type, status, event details, root cause analysis, assigned operation and maintenance personnel, etc. of the exception object, and the operation and maintenance information can include the entire process of the administrator handling the exception, the information of the person handling each processing link, etc. Outputting the exception information and operation and maintenance information can facilitate the administrator to analyze and review the exception and improve the problem management capabilities of operation and maintenance.
[0108] In one embodiment, the event monitoring system outputs the abnormal information and operation and maintenance information of the abnormal object, including at least one of the following processing: the event monitoring system outputs the abnormal information and operation and maintenance information of the corresponding abnormal object to the second terminal device, and the event monitoring system outputs the abnormal information and operation and maintenance information of the corresponding abnormal object to the third terminal device. The second terminal device is a terminal device of an administrator who has management authority over all target objects, for example Figure 3 The terminal device of the manager or operation and maintenance expert shown in the figure can enable the global administrator to review the global abnormal events. The third terminal device is the terminal device of the administrator who has the management authority over some target objects, for example Figure 3 The application operation and maintenance personnel, instance operation and maintenance personnel, or system operation and maintenance personnel shown can enable the administrator of the local level module to review the local abnormal events.
[0109] Based on the event monitoring method provided in the embodiment of the present application, even if the permissions are isolated, each administrator can notify the corresponding personnel to perform emergency processing through the response, work order, operation and maintenance operations of the integrated event monitoring system, thereby achieving rapid response, efficient troubleshooting and precise operation and maintenance.
[0110] Based on the same technical concept, such as Fig.19 As shown, the embodiment of the present application also provides a construction device 1900 for an event monitoring system, and the construction device 1900 may include: a hierarchical construction module 1901, an internal link construction module 1902, an external link construction module 1903 and a system construction module 1904.
[0111] The hierarchical construction module 1901 is used to construct multiple hierarchical modules corresponding to the object to be monitored according to multiple resource attributes of the object to be monitored; the resource attributes include cloud product attributes, and the multiple hierarchical modules include cloud product layers corresponding to multiple cloud products; the internal link construction module 1902 is used to construct the internal traceability link of each hierarchical module according to the object association relationship within each hierarchical module; the external link construction module 1903 is used to construct the external traceability link between each hierarchical module according to the object association relationship between each hierarchical module; the system construction module 1904 is used to construct an event monitoring system according to the multiple hierarchical modules, the internal traceability link and the external traceability link.
[0112] In one embodiment, the resource attributes further include business attributes, application attributes, cloud service instance attributes and infrastructure attributes, and the multiple hierarchical modules further include: business layer, application layer, cloud service instance layer and infrastructure layer.
[0113] In one embodiment, the system construction module 1904 is used to: determine the cloud form type of the event monitoring system to be constructed based on user demand information; select a hierarchical module that conforms to the cloud form type from each hierarchical module, and construct an event monitoring system including the selected hierarchical module, an internal traceability link corresponding to the selected hierarchical module, and an external traceability link corresponding to the selected hierarchical module.
[0114] In one embodiment, the construction device 1900 may further include a first setting module for setting a plurality of administrator candidates with different management permissions; the management permissions are used to manage a specified part or all of the hierarchical modules, and the event monitoring system also includes the plurality of administrator candidates.
[0115] In one embodiment, the construction device 1900 may further include a second setting module for setting a plurality of event level identifiers for marking the urgency of events; the event level identifiers include information of at least one element of color, text, shape and sound.
[0116] Based on the same technical concept, an embodiment of the present application also provides an event monitoring device, which may include: a monitoring module for monitoring events of a target object through an event monitoring system; the event monitoring system is constructed by any one of the event monitoring system construction methods provided in the embodiments of the present application.
[0117] In one embodiment, the above-mentioned event monitoring device may also include a troubleshooting module, which is used to, when there are abnormal events in the events monitored by the target object, conduct a layer-by-layer troubleshooting of the target objects corresponding to the modules at each level in the event monitoring system according to the internal traceability link and the external traceability link in the event monitoring system, to find abnormal objects in each target object.
[0118] In one embodiment, the above-mentioned event monitoring device may also include an impact range analysis module, which is used to determine the impact range of each abnormal object based on the association relationship between the abnormal objects, determine the event level of each abnormal object based on the impact range, and output an event level identifier associated with the event level.
[0119] In one embodiment, the above-mentioned event monitoring device may also include a display module, which is used to display in real time through a visual interface at least one of the target objects and traceability paths corresponding to the checked hierarchical modules during the layer-by-layer investigation process; the traceability path displayed in real time is a part of the internal traceability link and the external traceability link.
[0120] In one embodiment, the above-mentioned event monitoring device may also include a first information sending module, which is used to send an event message for prompting the abnormality to a first terminal device when an abnormal event is detected in the events monitored for the target object; the first terminal device is a terminal device of an administrator who has management authority over the abnormal object.
[0121] In one embodiment, the event monitoring device may further include an abnormality analysis module for analyzing the data indicators of the abnormal object to determine the cause of the abnormal event.
[0122] In one embodiment, the event monitoring device may further include a review module, which is used to output the abnormal information and operation and maintenance information of the abnormal object in response to a received review request after the operation and maintenance of the abnormal event is completed.
[0123] In one embodiment, the above-mentioned review module can be used to perform at least one of the following processing: outputting the abnormal information and operation and maintenance information of the corresponding abnormal object to a second terminal device; the second terminal device is a terminal device of an administrator who has management authority over all target objects; outputting the abnormal information and operation and maintenance information of the corresponding abnormal object to a third terminal device; the third terminal device is a terminal device of an administrator who has management authority over some target objects.
[0124] The functions of each module in each device in the embodiments of the present application can be found in the corresponding description in the above method, and have corresponding beneficial effects, which will not be repeated here.
[0125] Based on the same technical concept, the embodiment of the present application also provides an electronic device, such as Fig. 20 As shown, the electronic device includes: a memory 2001 and a processor 2002, wherein the memory 2001 stores a computer program that can be run on the processor 2002. When the processor 2002 executes the computer program, the method in the above embodiment is implemented. The number of the memory 2001 and the processor 2002 can be one or more.
[0126] The electronic device also includes:
[0127] The communication interface 2003 is used to communicate with external devices and perform data exchange transmission.
[0128] If the memory 2001, the processor 2002 and the communication interface 1630 are implemented independently, the memory 2001, the processor 2002 and the communication interface 2003 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 20 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0129] Optionally, in a specific implementation, if the memory 2001, the processor 2002 and the communication interface 2003 are integrated on a chip, the memory 2001, the processor 2002 and the communication interface 2003 can communicate with each other through an internal interface.
[0130] An embodiment of the present application provides a computer-readable storage medium storing a computer program, which implements the method provided in the embodiment of the present application when the program is executed by a processor.
[0131] An embodiment of the present application also provides a chip, which includes a processor for calling and executing instructions stored in the memory from the memory, so that a communication device equipped with the chip executes the method provided by the embodiment of the present application.
[0132] An embodiment of the present application also provides a chip, including: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the method provided in the embodiment of the application.
[0133] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. It is worth noting that the processor may be a processor supporting the Advanced RISC Machines (ARM) architecture.
[0134] Further, optionally, the above-mentioned memory may include a read-only memory and a random access memory. The memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may include a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may include a random access memory (RAM), which is used as an external cache. By way of exemplary but not limiting description, many forms of RAM are available. For example, static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DR RAM).
[0135] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
[0136] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments or examples described in this specification and the features of different embodiments or examples, unless they are contradictory.
[0137] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.
[0138] Any process or method described in the flow chart or otherwise described herein can be understood as a module, fragment or portion of a code representing one or more executable instructions for implementing the steps of a specific logical function or process. And the scope of the preferred embodiment of the present application includes other implementations, in which the functions may not be performed in the order shown or discussed, including in a substantially simultaneous manner or in a reverse order according to the functions involved.
[0139] The logic and / or steps described in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, which can be specifically implemented in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or used in combination with these instruction execution systems, devices or apparatuses.
[0140] It should be understood that the various parts of the present application can be implemented with hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented with software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above embodiment method can be completed by instructing the relevant hardware through a program, which can be stored in a computer-readable storage medium, and when the program is executed, it includes one of the steps of the method embodiment or a combination thereof.
[0141] In addition, each functional unit in each embodiment of the present application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the above-mentioned integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The storage medium can be a read-only memory, a disk or an optical disk, etc.
[0142] The above is only an exemplary embodiment of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various changes or substitutions within the technical scope recorded in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A method for constructing an event monitoring system, characterized in that: include: According to the multiple resource attributes of the object to be monitored, construct multiple hierarchical modules corresponding to the object to be monitored; the resource attributes include cloud product attributes, and the multiple hierarchical modules include cloud product layers corresponding to multiple cloud products; According to the object association relationship within each level module, an internal traceability link of each level module is constructed, wherein at least some of the level modules include multiple sub-levels with dependency relationships, and the internal traceability link of the part of the level modules corresponds to the horizontal dependency relationship between the sub-levels; According to the object association relationship between modules at each level, an external traceability link between modules at each level is constructed, wherein modules at each level have a dependency relationship, and the external traceability link between modules at each level corresponds to the vertical dependency relationship between modules at each level; An event monitoring system is constructed based on the multiple hierarchical modules, the internal traceability link and the external traceability link.
2. The method for constructing an event monitoring system according to claim 1, characterized in that: The event monitoring system is constructed according to the hierarchical module, the internal traceability link and the external traceability link, including: Determine the cloud form type of the event monitoring system to be built based on user demand information; A hierarchical module that conforms to the cloud form type is selected from each hierarchical module, and an event monitoring system is constructed including the selected hierarchical module, an internal traceability link corresponding to the selected hierarchical module, and an external traceability link corresponding to the selected hierarchical module.
3. The method for constructing an event monitoring system according to claim 1 or 2, characterized in that: The resource attributes further include business attributes, application attributes, cloud service instance attributes and infrastructure attributes, and the multiple hierarchical modules further include: a business layer, an application layer, a cloud service instance layer and an infrastructure layer.
4. The method for constructing an event monitoring system according to claim 1 or 2, characterized in that: Also includes: A plurality of administrator candidates with different management permissions are set; the management permissions are used to manage a specified part or all of the hierarchical modules, and the event monitoring system also includes the plurality of administrator candidates.
5. The method for constructing an event monitoring system according to claim 1 or 2, characterized in that: Also includes: A plurality of event level identifiers are set for marking the urgency of an event; the event level identifiers include information of at least one element of color, text, shape and sound.
6. An event monitoring method, characterized in that: include: Monitor events of target objects through event monitoring system; The event monitoring system is constructed by the event monitoring system construction method according to any one of claims 1 to 5.
7. The event monitoring method according to claim 6, characterized in that: Also includes: When there are abnormal events in the events monitored by the target object, the target objects corresponding to the modules at each level in the event monitoring system are checked layer by layer according to the internal tracing link and the external tracing link in the event monitoring system to find the abnormal objects in each target object.
8. The event monitoring method according to claim 7, characterized in that: Also includes: Determine the impact scope of each abnormal object based on the association relationship between the abnormal objects; Determine the event level of each abnormal object according to the impact range; An event level identifier associated with the event level is output.
9. The event monitoring method according to claim 7, characterized in that: Also includes: In the process of checking layer by layer, at least one of the target object and the traceability path corresponding to the checked level module is displayed in real time through a visual interface; The traceability path displayed in real time is a part of the internal traceability link and the external traceability link.
10. The event monitoring method according to any one of claims 6 to 9, characterized in that: Also includes: When an abnormal event is detected in the events of the target object being monitored, sending an event message for prompting the abnormality to the first terminal device; The first terminal device is a terminal device of an administrator who has management authority over the abnormal object.
11. The event monitoring method according to any one of claims 7 to 9, characterized in that: Also includes: The data indicators of the abnormal object are analyzed to determine the cause of the abnormal event.
12. The event monitoring method according to any one of claims 7 to 9, characterized in that: Also includes: After the operation and maintenance of the abnormal event is completed, in response to the received replay request, the event monitoring system outputs the abnormal information and operation and maintenance information of the abnormal object.
13. The event monitoring method according to claim 12, characterized in that: The event monitoring system outputs the abnormal information and operation and maintenance information of the abnormal object, including at least one of the following processing: The event monitoring system outputs the abnormal information and operation and maintenance information of the corresponding abnormal object to the second terminal device; the second terminal device is a terminal device of an administrator who has management authority over all target objects; The event monitoring system outputs the abnormal information and operation and maintenance information of the corresponding abnormal object to the third terminal device; the third terminal device is a terminal device of an administrator who has management authority over some target objects.
14. A device for constructing an event monitoring system, characterized in that: include: A hierarchical construction module is used to construct multiple hierarchical modules corresponding to the monitored object according to various resource attributes of the monitored object; The resource attributes include cloud product attributes, and the multiple hierarchical modules include cloud product layers corresponding to multiple cloud products; An internal link construction module, used to construct an internal traceability link of each level module according to the object association relationship within each level module, wherein at least some of the level modules include multiple sub-levels with dependency relationships, and the internal traceability link of the part of the level modules corresponds to the horizontal dependency relationship between the sub-levels; The external link construction module is used to construct the external traceability links between the modules of each level according to the object association relationship between the modules of each level, wherein the modules of each level have a dependency relationship, and the external traceability links between the modules of each level correspond to the vertical dependency relationship between the modules of each level; A system building module is used to build an event monitoring system based on the multiple hierarchical modules, the internal tracing link and the external tracing link.
15. An event monitoring device, characterized in that: include: A monitoring module, used to monitor events of a target object through an event monitoring system; The event monitoring system is constructed by the event monitoring system construction method according to any one of claims 1 to 5.
16. An electronic device comprising a memory, a processor and a computer program stored in the memory, wherein the processor implements the method according to any one of claims 1 to 13 when executing the computer program.
17. A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the method according to any one of claims 1 to 13 is implemented.
