WO2020015092A1 - Procédé et appareil de surveillance d'instance, dispositif terminal et support - Google Patents

Procédé et appareil de surveillance d'instance, dispositif terminal et support Download PDF

Info

Publication number
WO2020015092A1
WO2020015092A1 PCT/CN2018/105056 CN2018105056W WO2020015092A1 WO 2020015092 A1 WO2020015092 A1 WO 2020015092A1 CN 2018105056 W CN2018105056 W CN 2018105056W WO 2020015092 A1 WO2020015092 A1 WO 2020015092A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
alarm
newly created
instance
created instance
Prior art date
Application number
PCT/CN2018/105056
Other languages
English (en)
Chinese (zh)
Inventor
林水明
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2020015092A1 publication Critical patent/WO2020015092A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting

Definitions

  • the present application belongs to the field of monitoring technology, and in particular, relates to an example monitoring method, device, terminal device, and medium.
  • the monitoring system does not know what type of instance it is, nor can it know that the default alarm policy for this type of instance can How to configure it will bring a lot of restrictions to the automatic alarm configuration of the monitored instance, which will increase the user's operation and maintenance costs.
  • the embodiments of the present application provide an instance monitoring method, device, terminal device, and medium to solve the problem that the monitored instance does not have a type attribute, cannot implement automatic alarm configuration, and increases the operation and maintenance cost of the user.
  • a first aspect of the embodiments of the present application provides an instance monitoring method, including:
  • the preset alarm policy including an alarm condition
  • alarm data includes the monitoring type and monitoring data of the newly created instance.
  • a second aspect of the embodiments of the present application provides an example monitoring apparatus, including:
  • An instance obtaining module configured to obtain a newly created instance, where the newly created instance is configured with a corresponding monitoring type
  • An association module configured to associate the newly created instance with a preset alarm policy of the monitoring type stored in a monitoring system according to the monitoring type corresponding to the newly created instance, the preset alarm policy Including alarm conditions;
  • a judging module configured to determine, after the association, whether the newly created instance meets the alarm conditions in the alarm policy according to the alarm policy of the newly created instance during running;
  • An alarm module is configured to trigger an automatic alarm function and obtain alarm data when the alarm conditions in the alarm policy are met, where the alarm data includes the monitoring type and monitoring data of the newly created instance.
  • a terminal device including a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, and the processor executes the processor.
  • the computer-readable instructions implement the following steps:
  • the preset alarm policy including an alarm condition
  • alarm data includes the monitoring type and monitoring data of the newly created instance.
  • a computer-readable storage medium stores computer-readable instructions, and the computer-readable instructions implement the following steps when executed by at least one processor:
  • the preset alarm policy including an alarm condition
  • alarm data includes the monitoring type and monitoring data of the newly created instance.
  • the embodiment of the present application first obtains a newly created instance, the newly created instance is configured with a corresponding monitoring type, and then according to the monitoring type corresponding to the newly created instance, the newly created instance and the monitoring system are Associate the stored preset alarm policy of the monitoring type, the preset alarm policy includes alarm conditions, and implement automatic alarm configuration. After the association, the newly created instance is determined according to the alarm policy of the newly created instance. Whether the alarm conditions in the alarm policy are met during operation, and if the alarm conditions in the alarm policy are met, an automatic alarm function is triggered and alarm data is obtained, and the alarm data includes the newly created The monitoring type and monitoring data of the instance to realize the automatic monitoring of the newly created instance.
  • FIG. 1 is a schematic flowchart of an example monitoring method provided by this application
  • FIG. 2 is a schematic flowchart of another embodiment of an example monitoring method provided by the present application.
  • FIG. 3 is a schematic flowchart of still another embodiment of an example monitoring method provided by the present application.
  • FIG. 4 is a schematic flowchart of still another embodiment of an example monitoring method provided by the present application.
  • FIG. 5 is a structural block diagram of an example monitoring device according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 1 is a schematic flowchart of an example monitoring method according to an embodiment of the present application.
  • the example monitoring method may include steps S101 to S104:
  • the monitoring type may include at least one of the following: a host class, a physical machine class, a load balancer class, a database class, and the like.
  • Each instance is configured with a corresponding monitoring type when it is created. Instance, you can get the monitoring type corresponding to the newly created instance.
  • each newly created instance can be registered in the monitoring system.
  • Each newly created instance needs to register instance information when registering.
  • the instance information may include an ID (identity identification number), an instance name, Instance type, tenant ID using the newly created instance, area information of the newly created instance, and readable name, here the instance type is the monitoring type, and the newly created instance is obtained by obtaining the instance information of the newly created instance The monitoring type of the instance.
  • the method may include: obtaining a monitoring type of an existing instance monitored by the monitoring system, and performing a predefined alarm configuration on the monitoring type; wherein the predefined alarm configuration includes At least one of the following: preset reportable monitoring items, reportable instance names, and preset alarm policies; the preset reportable monitoring items include at least one of the following: CPU, memory, and disk space.
  • the existing instance and the newly created instance may include at least one of the following: cloud host, physical machine, load balancer, database, and the predefined alarm configuration corresponding to the monitoring type may include: cloud host alarm configuration , Physical machine alarm configuration, load balancer alarm configuration, database alarm configuration, etc.
  • different monitoring types can correspond to different preset reportable monitoring items.
  • the corresponding preset reportable monitoring items in cloud host monitoring can include: CPU, memory, disk space, disk inode (index node, used to store basic information of files and directories, including time, file name, user And groups, etc.); each monitoring type can monitor multiple instances, and the different instances monitored correspond to unused instance names, but the instance names of the created instances are globally unique, and they are also unique in the system.
  • All the monitoring types in the monitoring system are pre-defined alarm configuration, and the monitoring type of the newly created instance is matched with the corresponding monitoring type configured by the predefined alarm, so that the newly created instance is monitored with the type in the monitoring system. , Automatically configure alarm policies.
  • S102 according to the monitoring type corresponding to the newly created instance, associate the newly created instance with a preset alarm policy of the monitoring type stored in a monitoring system, the preset alarm Policies include alert conditions.
  • the operation portal when a new instance is created on the web portal, the operation portal is different. According to the portal, it is possible to obtain what type of monitoring the newly created instance belongs to, so that the newly created instance is deleted.
  • the monitoring system carries the monitoring type when monitoring.
  • the initialization interface of the monitoring system is called. If the monitoring type of the newly created instance is host monitoring, the host monitoring interface is called to initialize the host alarm policy. If the monitoring type of the newly created instance is For one of physical machine monitoring, load balancer monitoring, and database monitoring, the application monitoring interface is called to initialize the instance alarm policy of the application class.
  • the initialization interface a file of the predefined alarm configuration in the monitoring system Copy to the newly created instance, and associate the newly created instance with a preset alarm policy of the monitoring type stored in a monitoring system.
  • FIG. 2 is a schematic flowchart of another embodiment of an instance monitoring method.
  • FIG. 2 shows that the newly created instance is stored in the monitoring system in S102.
  • the association of the preset alarm policies of the monitoring type may include steps S201 to S203:
  • S202 Acquire a file of the predefined alarm configuration corresponding to the monitoring type according to a preset mapping table
  • S203 Obtain the preset alarm policy from the file of the predefined alarm configuration, and copy the preset alarm policy to the newly created instance.
  • the newly created instance carries the monitoring type
  • the monitoring type carries an identifier.
  • a lookup from a monitoring system is consistent with the monitoring type carried by the newly created instance.
  • Monitoring type In the monitoring system, each of the monitoring type and the corresponding predefined alarm configuration file stores the preset mapping table, and according to the monitoring type, the corresponding preset mapping table can be obtained.
  • the monitoring type corresponding to the host is host monitoring.
  • the host monitoring identifier is used to find the host monitoring consistent with the monitoring type corresponding to the host from the monitoring system identifier.
  • a mapping table is set to obtain a file of the predefined alarm configuration corresponding to host monitoring, wherein the preset mapping table may be a character mapping table, a key in the character mapping table is a monitoring type identifier, and a value is the preset Defines the address of the alarm configuration file. Acquiring the preset alarm policy monitored by the host from the file of the predefined alarm configuration, and copying the preset alarm policy to the newly created instance to implement the newly created instance and monitoring Association of preset alarm policies of the monitoring type stored in the system.
  • the preset alarm strategy may include at least one of the following: indicators of monitoring items, additional attributes of the indicators, maximum number of warnings, alarm priority, statistical functions, comparison operators, alarm thresholds, alarm remarks, and effective alarm policies
  • the alarm policy of the newly created instance may be a preset alarm policy corresponding to the monitoring type of the newly created instance or a modified preset alarm policy.
  • the alarm policy of the instance can be modified by the tenant of the newly created instance, specifically: sending a modification signal of the predefined alarm configuration in the newly created instance to the tenant of the newly created instance, and receiving all The modified predefined alarm configuration sent by the tenant is described, and the alarm policy of the newly created instance is obtained from the modified predefined alarm configuration.
  • each instance can be shared by multiple tenants, but each tenant is predefined with a namespace.
  • the configuration data for the newly created instance may include: APP ID, tenant ID, instance name, monitoring type, area information of the instance (the address where the instance was created), and a readable name (the instance name that can be changed) )
  • the monitoring data may include monitoring data of preset reportable monitoring items or data of the preset alarm strategy, or the monitoring data may include modified preset reportable Monitoring data of the monitoring item or data of the preset alarm strategy after modification. Therefore, each instance corresponds to a tenant, and the tenant can only modify the configuration data corresponding to the tenant.
  • the alarm policy of the newly created instance determine whether the newly created instance meets the alarm conditions in the alarm strategy during the running process.
  • the newly created instance is monitored as a host, it is determined whether the host meets the alarm conditions during the running process.
  • step S104 if the alarm conditions in the alarm policy are met, an automatic alarm function is triggered, and alarm data is obtained, where the alarm data includes a monitoring type and monitoring data of the newly created instance.
  • an alarm signal is automatically sent to the monitoring system and alarm data is obtained, where different types of monitoring correspond to different preset reportable monitoring item.
  • the newly created instance is further configured with a corresponding instance name; after obtaining the alarm data, the monitoring data corresponding to the newly created instance is filtered from the alarm data, and according to the The corresponding instance name reports the filtered monitoring data to a tenant corresponding to the newly created instance; wherein the monitoring data includes monitoring data of the preset reportable monitoring items and the preset alarm policy
  • the monitoring data of the preset reportable monitoring items includes at least one of the following: CPU usage, memory usage, and disk space usage.
  • the data of the preset alarm policy includes the maximum number of warnings and the severity level. .
  • the corresponding monitoring type is a host type
  • the corresponding preset reportable monitoring item may include a CPU usage rate
  • the alarm data is filtered out from the alarm data.
  • the monitoring data corresponding to the host, the monitoring data corresponding to the host may include monitoring data (CPU usage rate) of a preset reportable monitoring item corresponding to the host and data of a preset alarm policy (maximum warning times) And severity levels).
  • the data is processed, and the tenant may be a user.
  • FIG. 3 is a schematic flowchart of still another embodiment of an instance monitoring method.
  • the instance monitoring method may further include steps S301 to S302:
  • S301 classify and configure the monitoring type of the existing instance, and configure an attribute identifier, where the attribute identifier includes a host type monitoring identifier and an application type monitoring identifier, and the monitoring attributes corresponding to the attribute identifier include host type monitoring and application type monitoring;
  • the monitoring type of the existing instance is classified and an attribute identifier is configured.
  • the monitoring attributes corresponding to the attribute identifier can be mainly divided into host-type monitoring and application-type monitoring.
  • the host-type monitoring may include: Host type
  • the application type monitoring may include at least one of the following types of monitoring: physical machine type, load balancer type, and database type.
  • the attribute identifier corresponding to the monitoring type the predefined alarm configuration is respectively performed on the host type monitoring and the application type monitoring. If the newly created instance is associated with a preset alarm policy in the predefined alarm configuration, it may directly Find a monitoring attribute corresponding to the newly created instance, copy a preset alarm policy corresponding to the monitoring attribute to the newly created instance, and complete the association.
  • FIG. 4 is a schematic flowchart of still another embodiment of an example monitoring method.
  • FIG. 4 shows the pre-defined alarm configuration for the monitoring attribute according to the attribute identification in S302, which may include: Steps S401 to S403:
  • the newly created instance carrying the attribute identifier is acquired, and based on the attribute identifier, it is determined whether the monitoring system has the attribute identifier that is consistent with the newly created instance, for example, When the newly created instance is a host, the corresponding monitoring type is host class, and the corresponding monitoring attribute is host class monitoring. According to the attribute identifier carried by the host, it is compared with all attribute identifiers in the monitoring system.
  • the embodiment of the present application first obtains a newly created instance, the newly created instance is configured with a corresponding monitoring type, and then according to the monitoring type corresponding to the newly created instance, the newly created instance is The instance is associated with a preset type of alarm policy of the monitoring type stored in the monitoring system.
  • the preset alarm policy includes alarm conditions to implement automatic alarm configuration. After the association, it determines the location of the alarm according to the alarm policy of the newly created instance. Describes whether the newly created instance meets the alarm conditions in the alarm policy during operation. If the alarm conditions in the alarm policy are met, an automatic alarm function is triggered, and alarm data is obtained.
  • the alarm data The monitoring type and monitoring data of the newly created instance are included to realize automatic monitoring of the newly created instance.
  • FIG. 5 shows a structural block diagram of an example monitoring apparatus provided by an embodiment of the present application. For convenience of explanation, only the parts related to this embodiment are shown.
  • the device includes:
  • An instance obtaining module 501 is configured to obtain a newly created instance, where the newly created instance is configured with a corresponding monitoring type;
  • An association module 502 configured to associate the newly created instance with a preset alarm policy of the monitoring type stored in a monitoring system according to the monitoring type corresponding to the newly created instance, the preset alarm
  • the strategy includes alarm conditions
  • a judging module 503, configured to determine, after association, whether the newly created instance meets the alarm conditions in the alarm policy according to an alarm policy of the newly created instance;
  • the alarm module 504 is configured to trigger an automatic alarm function and obtain alarm data when the alarm conditions in the alarm policy are met, where the alarm data includes a monitoring type and monitoring data of the newly created instance.
  • the instance monitoring device may further include: a first alarm configuration module, configured to: before the acquiring a newly created instance, acquire a monitoring type of an existing instance monitored by the monitoring system, and perform monitoring on the monitoring Pre-defined alarm configuration of the type; wherein the pre-defined alarm configuration includes at least one of the following: a preset reportable monitoring item, a reportable instance name, a preset alarm policy, and the preset reportable monitoring Items include at least one of the following: CPU, memory, disk space.
  • a first alarm configuration module configured to: before the acquiring a newly created instance, acquire a monitoring type of an existing instance monitored by the monitoring system, and perform monitoring on the monitoring Pre-defined alarm configuration of the type; wherein the pre-defined alarm configuration includes at least one of the following: a preset reportable monitoring item, a reportable instance name, a preset alarm policy, and the preset reportable monitoring Items include at least one of the following: CPU, memory, disk space.
  • the association module 502 includes:
  • a searching unit configured to search for the monitoring type corresponding to the monitoring system according to the monitoring type corresponding to the newly created instance
  • An obtaining unit configured to obtain a file of the predefined alarm configuration corresponding to the monitoring type according to a preset mapping table
  • the association unit obtains the preset alarm policy from the file of the predefined alarm configuration, and copies the preset alarm policy to the newly created instance.
  • the newly created instance is further configured with a corresponding instance name
  • the device further includes a monitoring data filtering module for filtering the alarm data from the new alarm data after obtaining the alarm data.
  • the monitoring data corresponding to the created instance and reporting the filtered monitoring data to a tenant corresponding to the newly created instance according to the corresponding instance name;
  • the monitoring data includes monitoring data of the preset reportable monitoring items and data of the preset alarm policy, and monitoring data of the preset reportable monitoring items includes at least one of the following: CPU usage Rate, memory usage rate, disk space usage rate, and the data of the preset alarm strategy includes the maximum number of warnings and the severity level.
  • the instance monitoring apparatus further includes: an attribute configuration module, configured to classify the monitoring type of the existing instance and configure an attribute identifier, where the attribute identifier includes a host-type monitoring identifier and an application-type monitoring identifier, and The monitoring attributes corresponding to the attribute identifiers include host-type monitoring and application-type monitoring;
  • a second alarm configuration module is configured to perform the predefined alarm configuration on the monitoring attribute according to the attribute identifier.
  • the second alarm configuration module includes:
  • An attribute identifier search unit configured to obtain the newly created instance, and find whether the attribute identifier that is consistent with the newly created instance exists in the monitoring system according to the attribute identifier carried by the newly created instance ;
  • An alarm configuration unit configured to obtain a file of the predefined alarm configuration corresponding to the attribute identifier consistent with the newly created instance when the attribute identifier consistent with the newly created instance exists, and A preset alarm policy in a file of a predefined alarm configuration is copied to the newly created instance;
  • a creating unit configured to create a new monitoring type and monitoring attribute in the monitoring system when there is no attribute identifier consistent with the newly created instance, and configure the new monitoring type and the newly created
  • the instance carries a consistent attribute identifier, and configures a new predefined alarm configuration file for the new monitoring attribute according to the newly created instance.
  • FIG. 6 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 6 of this embodiment includes a processor 60 and a memory 61.
  • the memory 61 stores computer-readable instructions 62 that can be run on the processor 60, such as an example monitoring method program. .
  • the processor 60 executes the computer-readable instructions 62, the steps in the foregoing embodiments of the method for monitoring each instance are implemented, for example, steps 101 to 104 shown in FIG. 1.
  • the processor 60 executes the computer-readable instructions 62
  • the functions of each module / unit in the foregoing device embodiments are implemented, for example, the functions of the units 501 to 504 shown in FIG. 5.
  • the computer-readable instructions 62 may be divided into one or more modules / units, the one or more modules / units are stored in the memory 61 and executed by the processor 60, To complete this application.
  • the one or more modules / units may be a series of computer-readable instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer-readable instructions 62 in the terminal device 6.
  • the terminal device 6 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server.
  • the terminal device may include, but is not limited to, a processor 60 and a memory 61.
  • FIG. 6 is only an example of the terminal device 6 and does not constitute a limitation on the terminal device 6. It may include more or fewer components than shown in the figure, or combine some components or different components.
  • the terminal device may further include an input / output device, a network access device, a bus, and the like.
  • the memory 61 may be an internal storage unit of the terminal device 6, such as a hard disk or a memory of the terminal device 6.
  • the memory 61 may also be an external storage device of the terminal device 6, such as a plug-in hard disk, a smart media card (SMC), and a secure digital (SD) provided on the terminal device 6. Card, flash card, etc. Further, the memory 61 may further include both an internal storage unit of the terminal device 6 and an external storage device.
  • the memory 61 is configured to store the computer-readable instructions and other programs and data required by the terminal device.
  • the memory 61 may also be used to temporarily store data that has been output or is to be output.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit.
  • the integrated unit When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially a part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium. , Including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • the foregoing storage media include: U disks, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

La présente invention se rapporte au domaine de la technologie de surveillance, et fournit un procédé et un appareil de surveillance d'instance, un dispositif terminal et un support. Le procédé de surveillance d'instance consiste : à obtenir une instance nouvellement créée, ladite instance nouvellement créée étant configurée avec un type de surveillance correspondant ; selon le type de surveillance correspondant à l'instance nouvellement créée, à associer l'instance nouvellement créée à une politique d'alarme prédéfinie du type de surveillance mémorisée dans un système de surveillance, la politique d'alarme prédéfinie comprenant une condition d'alarme ; après l'association, en fonction de la politique d'alarme de l'instance nouvellement créée, déterminer si l'instance nouvellement créée satisfait la condition d'alarme dans la politique d'alarme pendant un processus d'opération ; si la condition d'alarme dans la politique d'alarme est satisfaite, déclencher une fonction d'alarme automatique, et obtenir des données d'alarme, lesdites données d'alarme comprenant le type de surveillance et des données de surveillance de l'instance nouvellement créée.
PCT/CN2018/105056 2018-07-18 2018-09-11 Procédé et appareil de surveillance d'instance, dispositif terminal et support WO2020015092A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810788598.3 2018-07-18
CN201810788598.3A CN109240876B (zh) 2018-07-18 2018-07-18 实例监控方法、计算机可读存储介质和终端设备

Publications (1)

Publication Number Publication Date
WO2020015092A1 true WO2020015092A1 (fr) 2020-01-23

Family

ID=65072045

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/105056 WO2020015092A1 (fr) 2018-07-18 2018-09-11 Procédé et appareil de surveillance d'instance, dispositif terminal et support

Country Status (2)

Country Link
CN (1) CN109240876B (fr)
WO (1) WO2020015092A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112019386A (zh) * 2020-08-28 2020-12-01 北京浪潮数据技术有限公司 一种基于云平台的分布式集群告警方法、装置及设备
CN113064800A (zh) * 2021-04-19 2021-07-02 上海安畅网络科技股份有限公司 一种预警方法、装置、电子设备及可读存储介质
CN114067524A (zh) * 2021-11-23 2022-02-18 安徽富煌科技股份有限公司 一种策略恢复方案的电子站牌安全保护系统
CN117155772A (zh) * 2023-10-27 2023-12-01 广州嘉为科技有限公司 一种告警信息丰富方法、装置、设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112532404B (zh) * 2019-09-17 2023-09-22 中国移动通信集团广东有限公司 一种数据监控方法、装置及电子设备
CN110708197B (zh) * 2019-09-27 2022-10-11 招商局金融科技有限公司 监控装置、监控装置的监控策略的设置方法及存储介质
CN111193609B (zh) * 2019-11-20 2021-09-28 腾讯科技（深圳）有限公司 应用异常的反馈方法、装置及应用异常的监控系统

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080263556A1 (en) * 2007-04-17 2008-10-23 Michael Zoll Real-time system exception monitoring tool
CN104065510A (zh) * 2014-06-27 2014-09-24 北京思特奇信息技术股份有限公司 一种基于PetriNet的系统运维监控方法及系统
CN104252485A (zh) * 2013-06-29 2014-12-31 北京新媒传信科技有限公司 一种数据库管理平台
CN104408059A (zh) * 2014-10-29 2015-03-11 中国建设银行股份有限公司 一种故障处理的方法及装置
CN106936620A (zh) * 2015-12-31 2017-07-07 北京神州泰岳软件股份有限公司 一种告警事件的处理方法和处理装置
CN108259193A (zh) * 2016-12-28 2018-07-06 华为技术有限公司 一种网络管理方法、网络管理系统和网元管理系统
CN108270726A (zh) * 2016-12-30 2018-07-10 杭州华为数字技术有限公司 应用实例部署方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106681882A (zh) * 2015-11-06 2017-05-17 上海瑞致软件有限公司 基于Apriori算法的IT服务集中监控管理系统
CN107562599A (zh) * 2017-08-04 2018-01-09 无锡天脉聚源传媒科技有限公司 一种参数检测方法及装置
CN108011880A (zh) * 2017-12-04 2018-05-08 郑州云海信息技术有限公司 云数据系统中监控的管理方法和计算机可读存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080263556A1 (en) * 2007-04-17 2008-10-23 Michael Zoll Real-time system exception monitoring tool
CN104252485A (zh) * 2013-06-29 2014-12-31 北京新媒传信科技有限公司 一种数据库管理平台
CN104065510A (zh) * 2014-06-27 2014-09-24 北京思特奇信息技术股份有限公司 一种基于PetriNet的系统运维监控方法及系统
CN104408059A (zh) * 2014-10-29 2015-03-11 中国建设银行股份有限公司 一种故障处理的方法及装置
CN106936620A (zh) * 2015-12-31 2017-07-07 北京神州泰岳软件股份有限公司 一种告警事件的处理方法和处理装置
CN108259193A (zh) * 2016-12-28 2018-07-06 华为技术有限公司 一种网络管理方法、网络管理系统和网元管理系统
CN108270726A (zh) * 2016-12-30 2018-07-10 杭州华为数字技术有限公司 应用实例部署方法及装置

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112019386A (zh) * 2020-08-28 2020-12-01 北京浪潮数据技术有限公司 一种基于云平台的分布式集群告警方法、装置及设备
CN112019386B (zh) * 2020-08-28 2022-12-06 北京浪潮数据技术有限公司 一种基于云平台的分布式集群告警方法、装置及设备
CN113064800A (zh) * 2021-04-19 2021-07-02 上海安畅网络科技股份有限公司 一种预警方法、装置、电子设备及可读存储介质
CN113064800B (zh) * 2021-04-19 2023-03-24 上海安畅网络科技股份有限公司 一种预警方法、装置、电子设备及可读存储介质
CN114067524A (zh) * 2021-11-23 2022-02-18 安徽富煌科技股份有限公司 一种策略恢复方案的电子站牌安全保护系统
CN117155772A (zh) * 2023-10-27 2023-12-01 广州嘉为科技有限公司 一种告警信息丰富方法、装置、设备及存储介质
CN117155772B (zh) * 2023-10-27 2024-01-30 广州嘉为科技有限公司 一种告警信息丰富方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN109240876A (zh) 2019-01-18
CN109240876B (zh) 2022-05-27

Similar Documents

Publication Publication Date Title
WO2020015092A1 (fr) Procédé et appareil de surveillance d'instance, dispositif terminal et support
EP2933973B1 (fr) Procédé, appareil et système de protection de données
US7636919B2 (en) User-centric policy creation and enforcement to manage visually notified state changes of disparate applications
WO2021012568A1 (fr) Procédé de traitement de données et dispositif associé
WO2021051878A1 (fr) Procédé et appareil d'acquisition de ressources en nuage sur la base d'une permission d'un utilisateur et dispositif informatique
CN110795257A (zh) 处理多集群作业记录的方法、装置、设备及存储介质
US9430330B1 (en) System and method for managing environment metadata during data backups to a storage system
EP3488346B1 (fr) Détection d'anomalie à l'aide de séquences d'appels système
JP4807173B2 (ja) セキュリティ管理システムおよびその方法
US20220138188A1 (en) Generic scheduling
CN111597270A (zh) 数据同步方法、装置、设备及计算机存储介质
US20150278543A1 (en) System and Method for Optimizing Storage of File System Access Control Lists
US20100162349A1 (en) Content protection device, content protection method, and computer readable medium
JP7207009B2 (ja) 異常検知装置、異常検知方法および異常検知プログラム
WO2020015098A1 (fr) Procédé de gestion de données, dispositif terminal, et support
CN110855525A (zh) 流量统计方法、电子设备、系统及介质
US20130060758A1 (en) Graph authorization
WO2023273529A1 (fr) Procédé et appareil de surveillance de journal de maintenance, et support de stockage et dispositif électronique
US11588678B2 (en) Generating incident response action recommendations using anonymized action implementation data
CN115580522A (zh) 一种容器云平台运行状态的监控方法及装置
WO2023087278A1 (fr) Procédé et appareil de détermination de permission de plateforme en nuage, équipement terminal et support de stockage
CN106557263B (zh) 用于在数据块删除中检查伪共享的方法及设备
CN114860432A (zh) 一种内存故障的信息确定方法及装置
JP7173165B2 (ja) 履歴管理装置、履歴管理方法及びプログラム
KR100906449B1 (ko) 데이터베이스 툴 식별 장치 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18927110

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18927110

Country of ref document: EP

Kind code of ref document: A1