CN112506740A - Cloud alarm method, electronic equipment, storage medium and cloud alarm device - Google Patents
Cloud alarm method, electronic equipment, storage medium and cloud alarm device Download PDFInfo
- Publication number
- CN112506740A CN112506740A CN202011413495.2A CN202011413495A CN112506740A CN 112506740 A CN112506740 A CN 112506740A CN 202011413495 A CN202011413495 A CN 202011413495A CN 112506740 A CN112506740 A CN 112506740A
- Authority
- CN
- China
- Prior art keywords
- tag
- item
- label
- value
- alarm
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000004891 communication Methods 0.000 claims description 18
- 230000002159 abnormal effect Effects 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 8
- 230000005856 abnormality Effects 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 2
- 230000008569 process Effects 0.000 description 10
- 230000009471 action Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000010845 search algorithm Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to a cloud alarm method, an electronic device, a storage medium and a cloud alarm device, wherein the method comprises the following steps: when an alarm event exists, determining a tag value of at least one tag item based on the alarm event, wherein the at least one tag item has a dependency relationship; and when the target tag value exists in the tag values of the at least one tag item, sending alarm information to a user. When an alarm event exists, the tag value of at least one tag item can be determined based on the alarm event, and when a target tag value exists in the tag value of at least one tag item, alarm information containing the target tag value is sent to a user, so that the user can know the abnormity of resources on the cloud platform in time, and the smooth operation of the cloud platform is ensured.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a cloud alarm method, an electronic device, a storage medium, and a cloud alarm apparatus.
Background
With the rapid development of cloud computing technology, more and more hardware resources and software resources of internet application providers are provided to users in a service form through a cloud platform, so that the stability of the resources on the cloud platform is more and more emphasized by people. In order to ensure the smooth operation of the cloud platform, when the resources on the cloud platform are in an abnormal condition, how to alarm the user based on the abnormal condition becomes an urgent problem to be solved.
Disclosure of Invention
The application provides a cloud alarm method, an electronic device, a storage medium and a cloud alarm device, which are used for alarming a user using resources on a cloud platform when the resources on the cloud platform are abnormal, and specifically comprise the following steps:
in a first aspect, a cloud alarm method is provided, which is characterized by comprising:
when an alarm event exists, determining a tag value of at least one tag item based on the alarm event, wherein the at least one tag item has a dependency relationship;
when a target tag value exists in the tag values of the at least one tag item, sending alarm information to a user;
the alarm information comprises the target tag value, the alarm information is used for indicating that the resource in the cloud platform has an abnormality corresponding to the alarm event, and the target tag value is a tag value preset by the user.
In a second aspect, an electronic device is provided, which includes: the system comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus; the memory for storing a computer program; the processor is configured to execute the program stored in the memory, and implement the cloud alarm method according to any one of the first aspect.
In a third aspect, a computer-readable storage medium is provided, wherein a computer program is stored, and when being executed by a processor, the computer program implements the cloud alarm method according to any one of the first aspect.
In a fourth aspect, a cloud alarm device is provided, which includes:
a determining unit, configured to determine, when there is an alarm event, a tag value of at least one tag item based on the alarm event, the at least one tag item having a dependency relationship;
the sending unit is used for sending alarm information to a user when a target tag value exists in the tag values of the at least one tag item;
the alarm information comprises the target tag value, and the alarm information is used for indicating that the resource in the cloud platform has an abnormal target tag value corresponding to the alarm event, wherein the abnormal target tag value is a tag value preset by the user.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages:
according to the technical scheme, when an alarm event exists, the tag value of at least one tag item can be determined based on the alarm event, and when a target tag value exists in the tag value of at least one tag item, alarm information containing the target tag value is sent to a user, so that the user can know abnormality of resources on the cloud platform in time, and smooth operation of the cloud platform is further guaranteed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a schematic flow chart of a cloud alarm method in an embodiment of the present application;
fig. 2 is a schematic flow chart of a cloud alarm method in an embodiment of the present application;
FIG. 3 is a schematic structural diagram of a tag topology according to an embodiment of the present application;
fig. 4 is a schematic flow chart of a cloud alarm method in an embodiment of the present application;
fig. 5 is a schematic flow chart of a cloud alarm method in an embodiment of the present application;
fig. 6 is a schematic flow chart of a cloud alarm method in an embodiment of the present application;
FIG. 7 is a schematic structural diagram of an electronic device in an embodiment of the present application;
fig. 8 is a schematic structural diagram of a cloud alarm device in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
The embodiment of the application provides a cloud alarm method, which is applied to an alarm system and comprises the following steps as shown in fig. 1:
In the embodiment of the application, a general label library is built in the alarm system in advance, and the general label library comprises at least one general label item. Wherein the at least one tag item is derived based on the at least one generic tag item in the generic tag library.
In practical application, the universal tag library can be obtained by collecting the requirements of users. The user's requirement includes the label item commonly used in the alarm event, and the commonly used label item is used as at least one general label item.
The alarm system in the embodiment of the application can establish communication connection with hardware services and/or software services on the cloud platform side, and when the hardware services or the software services have faults, the failed hardware services or the software services can send alarm events to the alarm system.
In practice, the alarm event includes, but is not limited to, a fault code.
For example, when the alarm event is a fault code, since different hardware services or software services have faults and the corresponding fault codes are different, the alarm system may determine, according to the fault code, a service system in which the corresponding hardware service or software service is located, so that the tag value of at least one tag item may be determined from the service systems.
And 102, when a target tag value exists in the tag values of at least one tag item, sending alarm information to a user.
The alarm information comprises a target tag value, the alarm information is used for indicating that the resource in the cloud platform has an abnormality corresponding to the alarm event, and the target tag value is a tag value preset by a user.
In the embodiment of the application, a user can preset label values of multiple dimensions to an alarm system in advance, and when a target label value exists in the label values of at least one label item, alarm information is sent to the user. Namely, when a fault of a tag value according with a user preset dimension occurs on the cloud platform, alarm information is sent to the user.
According to the technical scheme, when an alarm event exists, the tag value of at least one tag item can be determined based on the alarm event, and when a target tag value exists in the tag value of at least one tag item, alarm information containing the target tag value is sent to a user, so that the user can know abnormality of resources on the cloud platform in time, and smooth operation of the cloud platform is further guaranteed.
Optionally, as an embodiment, when there is an alarm event, and the tag value of at least one tag item is determined based on the alarm event, as shown in fig. 2, step 101 may include the following steps:
In the embodiment of the present application, the identified first tag entry includes, but is not limited to, an IP address.
Wherein the second label item having a dependency relationship with the first label may include a label item having a direct dependency relationship with the first label and a label item having an indirect relationship with the first label.
In the embodiment of the application, the label topological structure is a topological structure which is constructed in advance according to the dependency relationship of at least one universal label item.
In this embodiment of the application, the identified first tag item may be a source tag item in a tag topological structure, or may be any tag item except for the source tag item in the tag topological structure. The source label item is a first layer label item in a label topological structure, and the first layer label item comprises at least one label item.
When the identified first tag item is a source tag item in the tag topology, the number of the at least one tag item in step 101 is the same as the number of the general tag items in the general tag library.
When the identified first tag item is any tag item except the source tag item in the tag topology structure, the number of the at least one tag item in step 101 is smaller than the number of the general tag items in the general tag library.
In practical applications, as shown in fig. 3, the label topology may be a directed acyclic graph. Regarding the dependency relationship between different tag entries, in fig. 3, taking an instanceState tag entry as an example, the tag entries having a dependency relationship with the instanceState tag entry are three tag entries of service, port and IPv4, that is, the tag entry needs to be obtained by depending on three tag entries of service, port and IPv 4.
In the embodiment of the application, a service system of a hardware service or a software service generating an alarm event can be determined according to the alarm event, so that the tag values of a first tag item and a second tag item for describing the alarm event can be determined from the service system.
Optionally, as another embodiment, when there is an alarm event, and the tag value of at least one tag item is determined based on the alarm event, as shown in fig. 4, step 101 may include the following steps:
The source label item is a first layer label item in the label topological structure, and the first layer label item comprises at least one label item.
In practical applications, the source tag in the tag topology includes, but is not limited to, a timestamp tag.
And 402, acquiring a third label item which has a dependency relationship with the source label item in the label topological structure.
In this embodiment, when an alarm event exists, a default is made to obtain a tag value of at least one tag item from a source tag item in a tag topology.
In this embodiment, since the default is to obtain the tag value of at least one tag item from the source tag item in the tag topology, the number of the at least one tag item is the same as the number of the general tag items in the general tag library.
In practical application, after the alarm system receives an alarm event, the alarm event can flow in from a source label item of the general label library, and a breadth-first search algorithm is used for flowing through all label items in the general label library, so that the label value of at least one label item is obtained.
Optionally, in this embodiment of the application, a user may add a tag item to the tag topology according to a need of the user, and when a tag value of the added tag item can be obtained based on an alarm event, the user may add the tag item to the tag topology by calling an interface opened to the user by the alarm system.
As shown in fig. 5, fig. 5 is an implementation process for adding a tag item to a tag topology by a user calling an interface opened by an alarm system to the user, where the implementation process includes the following steps:
The label request comprises a fourth label item needing to be added and a fifth label item having a dependency relationship with the fourth label item, wherein the fifth label item is an existing label item in a label topological structure.
It should be noted that the fifth tag item includes at least one tag item, that is, the fifth tag item may be one tag item, or may include at least two tag items.
In practical application, the specific implementation that the user calls the interface to add the fourth tag item to the tag topological structure may be that the alarm system displays the tag topological structure to the user through the display interface according to a tag request of the user, the alarm system controls to enable the fifth tag item in the tag topological structure displayed to the user to be edited according to the fifth tag item carried in the tag request, and the user edits the fifth tag item in the tag topological structure to enable the fourth tag item to depend on the fifth tag item.
Optionally, in another embodiment of the present application, when a user adds a tag item to a tag topology according to a need of the user, if a tag value of the added tag item cannot be obtained based on an alarm event, the user needs to add a tag to the tag topology by using a developer of the alarm system.
As shown in fig. 6, fig. 6 is an implementation process of adding a tag item to a tag topology by a developer of an alarm system, where the implementation process includes the following steps:
When the tag value of the sixth tag item which needs to be added cannot be obtained from the alarm event, a preset address for obtaining the tag value of the sixth tag item needs to be indicated to the alarm system, so that when the tag value of the sixth tag item needs to be obtained, the alarm system can obtain the tag value of the sixth tag item from the preset address.
In the embodiment of the present application, the preset address includes, but is not limited to, a storage address of the configuration management database.
And step 602, updating the label topological structure by using the sixth label item and the seventh label item.
In another embodiment of the present application, when the step of adding the tag entry to the tag topology occurs after step 102, updated alarm information may also be sent to the user based on the updated tag topology.
Alternatively, when the tag value predetermined by the user includes a target value of the fourth tag item, the tag value of the fourth tag item may be determined based on the alarm event, and when the tag value of the fourth tag is the same as the target value of the fourth tag item, updated alarm information may be sent to the user according to the tag value of the fourth tag item, where the updated alarm information includes the tag value of the fourth tag item and the target tag value.
The process of determining the tag value of the fourth tag item based on the alarm event is the same as the process of determining the tag value of at least one tag item based on the alarm event in the above embodiments, and therefore, the description is not repeated here.
Alternatively, when the tag value predetermined by the user includes a target value of a sixth tag item, the tag value of the sixth tag item may be determined based on the alarm event, and when the tag value of the sixth tag item is the same as the target value of the sixth tag item, updated alarm information may be sent to the user according to the tag value of the sixth tag item, where the updated alarm information includes the tag value of the sixth tag item and the target tag value.
It is understood that the tag value of the sixth tag entry is acquired based on the preset address.
Based on the same concept, an embodiment of the present application further provides an electronic device, as shown in fig. 7, the electronic device mainly includes: a processor 701, a communication interface 702, a memory 703 and a communication bus 704, wherein the processor 701, the communication interface 702 and the memory 703 are in communication with each other via the communication bus 704. The memory 703 stores a program executable by the processor 701, and the processor 701 executes the program stored in the memory 703 to implement the following steps:
when an alarm event exists, determining a tag value of at least one tag item based on the alarm event, wherein the at least one tag item has a dependency relationship;
when a target tag value exists in the tag values of at least one tag item, sending alarm information to a user;
the alarm information comprises a target tag value, the alarm information is used for indicating that the resource in the cloud platform has an abnormality corresponding to the alarm event, and the target tag value is a tag value preset by a user.
The communication bus 704 mentioned in the above electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 704 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus.
The communication interface 702 is used for communication between the above-described electronic apparatus and other apparatuses.
The Memory 703 may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Alternatively, the memory may be at least one memory device located remotely from the processor 701.
The Processor 701 may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like, or may be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic devices, discrete gates or transistor logic devices, and discrete hardware components.
In yet another embodiment of the present application, there is also provided a computer-readable storage medium having stored therein a computer program which, when run on a computer, causes the computer to execute the cloud alarm method described in the above embodiment.
Based on the same concept, the embodiment of the present application further provides a cloud alarm device, as shown in fig. 8, the device includes:
a determining unit 801, configured to determine, when there is an alarm event, a tag value of at least one tag item based on the alarm event, where the at least one tag item has a dependency relationship;
a sending unit 802, configured to send alarm information to a user when a target tag value exists in tag values of at least one tag item;
the alarm information comprises a target tag value, and the alarm information is used for indicating that the resource in the cloud platform has an abnormal target tag value corresponding to the alarm event as a tag value preset by a user.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may 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 loaded and executed on a computer, cause the processes or functions according to the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wirelessly (e.g., infrared, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The available media may be magnetic media (e.g., floppy disks, hard disks, tapes, etc.), optical media (e.g., DVDs), or semiconductor media (e.g., solid state drives), among others.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A cloud alarm method, comprising:
when an alarm event exists, determining a tag value of at least one tag item based on the alarm event, wherein the at least one tag item has a dependency relationship;
when a target tag value exists in the tag values of the at least one tag item, sending alarm information to a user;
the alarm information comprises the target tag value, the alarm information is used for indicating that the resource in the cloud platform has an abnormality corresponding to the alarm event, and the target tag value is a tag value preset by the user.
2. The method of claim 1, wherein determining a tag value for at least one tag item based on an alarm event when the alarm event is present comprises:
when an alarm event exists, identifying a first tag item according to information carried by the alarm event;
acquiring a second label item which has a dependency relationship with the first label item in the label topological structure;
and determining the label values of the first label item and the second label item according to the alarm event, and taking the label values of the first label item and the second label item as the label value of the at least one label item.
3. The method of claim 1, wherein determining a tag value for at least one tag item based on an alarm event when the alarm event is present comprises:
when an alarm event exists, acquiring a label topological structure, wherein the label topological structure comprises a source label item;
acquiring a third label item which has a dependency relationship with the source label item in the label topological structure;
and determining the label values of the source label item and the third label item according to the alarm event, and taking the label values of the source label item and the third label item as the label value of the at least one label item.
4. The method according to claim 2 or 3, wherein when the target tag value exists in the tag values of the at least one tag item, after sending alarm information to the user, the method further comprises:
receiving a tag request from the user, where the tag request includes a fourth tag item to be added and a fifth tag item having a dependency relationship with the fourth tag item, and the fifth tag item is an existing tag item in the tag topology structure;
updating the tag topology with the fourth tag entry and the fifth tag entry in response to the tag request.
5. The method of claim 4, wherein after sending an alert message to the user when the target tag value exists in the tag values of the at least one tag item, further comprising:
determining a tag value of the fourth tag item based on the alarm event when the user-predetermined tag value includes a target value of the fourth tag item;
and when the label value of the fourth label is the same as the target value of the fourth label item, updating the alarm information according to the label value of the fourth label item, and sending updated alarm information to the user, wherein the updated alarm information comprises the label value of the fourth label item and the target label value.
6. The method according to claim 2 or 3, wherein when the target tag value exists in the tag values of the at least one tag item, after sending alarm information to the user, the method further comprises:
acquiring a sixth tag item to be added, a preset address for acquiring a tag value of the sixth tag item, and a seventh tag item having a dependency relationship with the sixth tag item, where the seventh tag item is an existing tag item in the tag topology structure;
updating the tag topology with the sixth tag entry and the seventh tag entry.
7. The method of claim 6, wherein after sending an alert message to the user when the target tag value exists in the tag values of the at least one tag item, further comprising:
when the tag value predetermined by the user comprises the target value of the sixth tag item, acquiring the tag value of the sixth tag item from the preset address;
when the label value of the sixth label item is the same as the target value of the sixth label item, updating the alarm information according to the label value of the sixth label item, and sending updated alarm information to the user, wherein the updated alarm information comprises the label value of the sixth label item and the target label value.
8. An electronic device, comprising: the system comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus; the memory for storing a computer program; the processor, configured to execute the program stored in the memory, and implement the cloud alarm method according to any one of claims 1 to 7.
9. A computer-readable storage medium, characterized in that a computer program is stored, which when executed by a processor implements the cloud alarm method of any of claims 1 to 7.
10. A cloud alarm device, comprising:
a determining unit, configured to determine, when there is an alarm event, a tag value of at least one tag item based on the alarm event, the at least one tag item having a dependency relationship;
the sending unit is used for sending alarm information to a user when a target tag value exists in the tag values of the at least one tag item;
the alarm information comprises the target tag value, and the alarm information is used for indicating that the resource in the cloud platform has an abnormal target tag value corresponding to the alarm event, wherein the abnormal target tag value is a tag value preset by the user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011413495.2A CN112506740A (en) | 2020-12-04 | 2020-12-04 | Cloud alarm method, electronic equipment, storage medium and cloud alarm device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011413495.2A CN112506740A (en) | 2020-12-04 | 2020-12-04 | Cloud alarm method, electronic equipment, storage medium and cloud alarm device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112506740A true CN112506740A (en) | 2021-03-16 |
Family
ID=74970538
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011413495.2A Pending CN112506740A (en) | 2020-12-04 | 2020-12-04 | Cloud alarm method, electronic equipment, storage medium and cloud alarm device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112506740A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108171265A (en) * | 2017-12-26 | 2018-06-15 | 北京奇艺世纪科技有限公司 | A kind of label preparation method, device and electronic equipment |
| CN108959034A (en) * | 2018-07-05 | 2018-12-07 | 北京木瓜移动科技股份有限公司 | A kind of monitoring alarm method, device, electronic equipment and storage medium |
| CN110888985A (en) * | 2019-12-06 | 2020-03-17 | 北京奇艺世纪科技有限公司 | Alarm information processing method and device, electronic equipment and storage medium |
| CN111008109A (en) * | 2019-12-06 | 2020-04-14 | 北京奇艺世纪科技有限公司 | Monitoring data processing method and device, electronic equipment and storage medium |
-
2020
- 2020-12-04 CN CN202011413495.2A patent/CN112506740A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108171265A (en) * | 2017-12-26 | 2018-06-15 | 北京奇艺世纪科技有限公司 | A kind of label preparation method, device and electronic equipment |
| CN108959034A (en) * | 2018-07-05 | 2018-12-07 | 北京木瓜移动科技股份有限公司 | A kind of monitoring alarm method, device, electronic equipment and storage medium |
| CN110888985A (en) * | 2019-12-06 | 2020-03-17 | 北京奇艺世纪科技有限公司 | Alarm information processing method and device, electronic equipment and storage medium |
| CN111008109A (en) * | 2019-12-06 | 2020-04-14 | 北京奇艺世纪科技有限公司 | Monitoring data processing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11539578B2 (en) | Generating actionable alert messages for resolving incidents in an information technology environment | |
| CN108322351B (en) | Method and device for generating topological graph and method and device for determining faults | |
| US10860406B2 (en) | Information processing device and monitoring method | |
| US20160103750A1 (en) | Application programming interface monitoring tool notification and escalation method and system | |
| JP5162656B2 (en) | How to derive a web service interface from form metadata and table metadata | |
| CN110765422A (en) | Parameter checking method and device | |
| KR20090007566A (en) | Model-based event processing | |
| CN112905323B (en) | Data processing method, device, electronic equipment and storage medium | |
| US8775607B2 (en) | Identifying stray assets in a computing enviroment and responsively taking resolution actions | |
| CN111953558A (en) | Sensitive information monitoring method and device, electronic equipment and storage medium | |
| WO2023165226A1 (en) | Application resource backup method and apparatus, electronic device, and storage medium | |
| EP3671512B1 (en) | Automated software vulnerability determination | |
| CN112115103A (en) | File address display method and device, electronic equipment and readable storage medium | |
| CN115037653B (en) | Service flow monitoring method, device, electronic equipment and storage medium | |
| CN110674153A (en) | Data consistency detection method and device and electronic equipment | |
| CN112506740A (en) | Cloud alarm method, electronic equipment, storage medium and cloud alarm device | |
| CN110795646A (en) | Request processing method and device, electronic equipment and computer-readable storage medium | |
| CN113778780B (en) | Application stability determining method and device, electronic equipment and storage medium | |
| CN111124712A (en) | Event notification method, device, server and storage medium | |
| CN112667447B (en) | Data restoration method and device | |
| CN113420037B (en) | Asset data real-time changing method and device | |
| CN113347220B (en) | Inter-service data sharing method, device, server and medium | |
| US20220414618A1 (en) | Management and aggregation of ticket data from multiple sources | |
| CN110909171B (en) | Data scheduling method, device, terminal and storage medium | |
| CN117032777A (en) | Low-code platform configuration method, device, electronic equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |