CN111310043A

CN111310043A - Method and device for pushing information

Info

Publication number: CN111310043A
Application number: CN202010093060.8A
Authority: CN
Inventors: 王泽宇
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2020-02-14
Filing date: 2020-02-14
Publication date: 2020-06-19
Anticipated expiration: 2040-02-14
Also published as: CN111310043B

Abstract

The embodiment of the disclosure discloses a method and a device for pushing information. One embodiment of the method comprises: generating initial event information in response to detecting a fault or resource adjustment; supplementing time information and resource information based on the initial event information, and generating event information of system dimensionality; acquiring the corresponding relation between a client and a resource thereof, and matching the corresponding relation with the event information of the system dimension; determining the successfully matched client as a target client influenced by the event, and generating event information of the client dimension aiming at the target client; and pushing the event information of the client dimension to the target client. According to the implementation method, the problems in multiple aspects such as untimely time caused by artificial notification, meaningless disturbance caused by inaccurate notification range, invalid information caused by incomplete event information and the like can be effectively solved, and further the treatment efficiency and accuracy of the customer when the cloud service is abnormal can be effectively improved.

Description

Method and device for pushing information

Technical Field

The embodiment of the disclosure relates to the technical field of computers, in particular to a method and a device for pushing information.

Background

With the rapid development and landing of cloud computing, more and more enterprises build own services on public clouds and use various cloud services and components, and for the enterprises, the stability of the business of the enterprises depends on the system stability of the cloud services more and more; when the cloud service fails or is adjusted in plan, the service of the enterprise client can be influenced, and such information needs to be timely and accurately pushed to the enterprise client side, so that the client can be helped to quickly perceive accurate abnormal information, the corresponding adjustment and processing are accelerated, and the influence of the failure or adjustment of the cloud service on the client is reduced; if such messages fail to reach the client side, the fault handling decision of the client may be affected, and the fault influence is further expanded, and the brand public praise of the cloud computing manufacturer itself is also affected.

The existing common methods for notifying the customer of the public cloud service fault event information generally include the following two methods:

1. customer manager channels: before a fault occurs or planned adjustment is carried out, relevant contents can be synchronized to a customer manager by operation and maintenance or research and development personnel of cloud service, and then the customer manager informs each customer through communication tools such as telephone, WeChat and the like; the client is synchronized with the development of the event irregularly and for indefinite times; i.e. by providing event information to the client in a "person-to-person" manner. Because the customer manager contacts the customer manually, the condition that the notification is not timely or not available occurs, so that the fault information synchronization is delayed, and further the fault handling judgment of the customer can be influenced.

2. And (3) channel of the station: before a fault event occurs or planned adjustment is carried out, relevant content can be synchronized to after-sales support or relevant managers by operation and maintenance or research and development personnel of cloud service, and then event information is pushed to all customers through in-station information; typically a one-time notification, without much status updates and subsequent notifications. Because the information is sent by all the in-station information members, the clients which are possibly not affected by the fault or adjustment of the cloud service can be reminded and notified by the same, and additional interference can be caused to the clients

In the two methods, with the development of faults, the intermediate state and the final state are not updated timely and clearly, so that when a customer compares with own faults, the customer is not aligned due to the fact that clear time veins do not exist, and the customer is troubled, and the information also becomes invalid information, and the trust of the customer on a cloud service manufacturer is reduced.

Disclosure of Invention

The embodiment of the disclosure provides a method and a device for pushing information.

In a first aspect, an embodiment of the present disclosure provides a method for pushing information, including: generating initial event information in response to detecting a fault or resource adjustment; supplementing time information and resource information based on the initial event information, and generating event information of system dimensionality; acquiring the corresponding relation between a client and a resource thereof, and matching the corresponding relation with the event information of the system dimension; determining the successfully matched client as a target client influenced by the event, and generating event information of the client dimension aiming at the target client; and pushing the event information of the client dimension to the target client.

In some embodiments, the method further comprises: and receiving feedback information of the target customer to assist the cloud service side in relevant adjustment and response.

In some embodiments, after generating event information for the customer dimension of the target customer, the method further comprises: and if the target client is determined to have no push authority, filtering out the event information of the client dimension, and not pushing the event information to the target client.

In some embodiments, the method further comprises: and carrying out regular offline data mining and processing to generate the corresponding relation between the client and the resources of the client.

In some embodiments, the method further comprises: the event related information is displayed at the front end.

In some embodiments, generating event information for a customer dimension of a target customer comprises: generating state information according to the monitored data state; event information for the system dimension is adjusted into a form understood by the client and state information is added.

In a second aspect, an embodiment of the present disclosure provides an apparatus for pushing information, including: a generating unit configured to generate initial event information in response to detecting a failure or resource adjustment; a completion unit configured to generate event information of a system dimension based on the initial event information supplement time information and resource information; the matching unit is configured to acquire the corresponding relation between the client and the resource thereof and match the corresponding relation with the event information of the system dimension; the conversion unit is configured to determine the client successfully matched as a target client influenced by the event and generate event information of a client dimension aiming at the target client; a pushing unit configured to push event information of a client dimension to a target client.

In some embodiments, the apparatus further comprises a feedback unit configured to: and receiving feedback information of the target customer to assist the cloud service side in relevant adjustment and response.

In some embodiments, the apparatus further comprises a filtering unit configured to: after generating the event information of the client dimension aiming at the target client, if the target client is determined to have no push authority, filtering the event information of the client dimension, and not pushing the event information to the target client.

In some embodiments, the apparatus further comprises a digging unit configured to: and carrying out regular offline data mining and processing to generate the corresponding relation between the client and the resources of the client.

In some embodiments, the apparatus further comprises a display unit configured to: the event related information is displayed at the front end.

In some embodiments, the conversion unit is further configured to: generating state information according to the monitored data state; event information for the system dimension is adjusted into a form understood by the client and state information is added.

In a third aspect, an embodiment of the present disclosure provides an electronic device for pushing information, including: one or more processors; a storage device having one or more programs stored thereon which, when executed by one or more processors, cause the one or more processors to implement a method as in any one of the first aspects.

In a fourth aspect, embodiments of the disclosure provide a computer readable medium having a computer program stored thereon, wherein the program when executed by a processor implements a method as in any one of the first aspect.

The method and the device for pushing the information, provided by the embodiment of the disclosure, mainly aim at enterprise customers with services deployed in a public cloud environment, and effectively solve various problems such as untimely problem caused by artificial notification, meaningless disturbance problem caused by inaccurate notification range, information invalidity caused by incomplete event information and the like in a scene of how to quickly and accurately acquire related information when the public cloud service fails or is adjusted in a plan, so that the handling efficiency and the accuracy of the customers when the cloud service is abnormal can be effectively improved.

Drawings

Other features, objects and advantages of the disclosure will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:

FIG. 1 is an exemplary system architecture diagram in which one embodiment of the present disclosure may be applied;

FIG. 2 is a flow diagram for one embodiment of a method for pushing information, according to the present disclosure;

FIG. 3 is a schematic diagram of one application scenario of a method for pushing information according to the present disclosure;

FIG. 4 is a flow diagram of yet another embodiment of a method for pushing information according to the present disclosure;

FIG. 5 is a schematic block diagram illustrating one embodiment of an apparatus for pushing information in accordance with the present disclosure;

FIG. 6 is a schematic block diagram of a computer system suitable for use with an electronic device implementing embodiments of the present disclosure.

Detailed Description

The present disclosure is described in further detail below with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.

It should be noted that, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.

Fig. 1 shows an exemplary system architecture 100 to which embodiments of the disclosed method for pushing information or apparatus for pushing information may be applied.

As shown in fig. 1, the system architecture 100 may include client

terminal devices

101, 102, 103 and a server 104. The

terminal devices

101, 102, 103 and the server 104 are connected via a network. The network may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The client may use the

terminal devices

101, 102, 103 to interact with the server 104 over the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may have various communication client applications installed thereon, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.

The

terminal apparatuses

101, 102, and 103 may be hardware or software. When the

terminal devices

101, 102, 103 are hardware, they may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, mpeg compression standard Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, mpeg compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like. When the

terminal apparatuses

101, 102, 103 are software, they can be installed in the electronic apparatuses listed above. It may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services) or as a single piece of software or software module. And is not particularly limited herein.

The server 104 provides a whole set of solution for event management in a public cloud scenario, the specific content and state of event information are updated and managed by a fault management system at the back end, the event and the client are correspondingly managed by basic data of a client asset management system, the event is pushed to the client by the event management system, the client can check and pay attention to the event by a dashboard at the front end, and a peripheral management and automation flow tool is constructed to form an integral solution.

The main working mechanism and function of each link and module are as follows:

1. a fault management system: the system has the main functions of managing event information on the cloud service side, storing the event information into a fault management system in the form of an event when a cloud service fails or is adjusted in a plan mode (the form of the event at least comprises the content of the event, the time of the event and a resource (asset) list influenced by the event, wherein the content is provided when the monitoring system gives an alarm for an exception), and supporting automatic information entry (such as capturing relevant exceptions from the monitoring system) and manual entry and modification (such as adjustment in the plan and the like). The master control module is used for managing fault events and providing an API (application program interface), and the fault events can be automatically stored in a database through the master control module or manually input through the master control module; the information of the interaction with the database is the event data.

2. A customer asset management system: the system has the main functions that a user stores the corresponding relation between a client and a resource of the client, and when an event occurs, the mapping relation between the corresponding affected resource and the client needs to be acquired from the module to acquire an accurate user for pushing subsequent event information; because the related data volume is large, the part of contents is generated as a main part by regular off-line mining, a cache system is used for subsequent processes, and when an event with high real-time requirement is encountered, the event can be met through a real-time interface. The off-line calculation mainly includes that off-line convergence calculation is carried out on clients and corresponding resource (asset) information in each system to form a uniform data structure for subsequent query.

3. An event management system: the system is a core module in the whole event management scheme, and has the main functions of performing real-time calculation and mapping by combining the information of client assets after acquiring an event, finding out specific clients and affected resources affected by the event, generating corresponding event information, and pushing the event information to the clients for the clients to refer to and understand; when the event has a status update in the follow-up, the system can also update and push quickly.

Event matching is mainly to match events with clients, and the rough method is to match resources in event data (also called asset information (such as machine list, IP, and the like)) with the resources (assets) information of clients in client asset management, so as to find out the association matching between events and clients.

Event filtering mainly considers that not all events can be pushed to a client side, for example, some sensitive business information or internal information cannot be pushed directly, so that certain filtering is required.

The trigger is to push the event to the message pushing module after the event filtering is completed, so as to trigger the pushing of the event information.

The front end is a web interface which can be seen by a client and is used for viewing the pushed event information

It should be noted that the method for pushing information provided by the embodiment of the present disclosure is generally performed by the server 104, and accordingly, the apparatus for pushing information is generally disposed in the server 104.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

With continued reference to fig. 2, a flow 200 of one embodiment of a method for pushing information in accordance with the present disclosure is shown.

In response to detecting a fault or resource adjustment, initial event information is generated, step 201.

In this embodiment, an executing entity (for example, a server shown in fig. 1) of the method for pushing information may perform periodic offline data mining and processing by the client asset management system before an event occurs, so as to generate a corresponding relationship between an existing client and its asset. Because the information of { customer: resource } is stored in each system, for example, the virtual machine, storage, network, etc. of the cloud are different systems, such data can be in different places, and therefore offline calculation is required, that is, offline aggregate calculation is performed on the customer and corresponding resource and asset information in each system to form a uniform data structure.

When a fault event occurs, the fault can be discovered by the monitoring system and is alarmed, and the fault management system can automatically capture the fault.

When a regulation type event (such as 'program of xx cluster is expected to be upgraded at the next wednesday 0 point, and xx machine machines of the cluster interrupt service during upgrading') occurs, operation and maintenance of the cloud service or research and development personnel enter main information through an interface or an interface of a fault management system.

Step 202, supplementing time information and resource information based on the initial event information, and generating event information of system dimensions.

In this embodiment, the initial event information is incomplete and needs to be completed. When a fault event occurs, the monitoring system includes partial time information and resource information, the time information may not need to be supplemented, but in some scenarios, resource information needs to be supplemented (for example, in a virtual machine system, the monitoring finds that resources of a host machine are needed, but the resource information of the virtual machine needs to be supplemented, so that data interfacing with the asset management system can be facilitated). The fault management system adds information enrichment, such as adding time information, resource information and the like, in the storage of the fault management system in a structured mode.

When the adjustment event occurs, operation and maintenance personnel of the cloud service or research and development personnel input main information through an interface or an interface of the fault management system, the fault management system can automatically supplement other information such as time information, resource information and the like, and the information is also structurally stored in the storage of the fault management system.

Step 203, acquiring the corresponding relation between the client and the resource thereof, and matching the corresponding relation with the event information of the system dimension.

In this embodiment, the event management system matches the event information with the customer asset information to generate a corresponding relationship between the event, the customer, and the asset. Event matching is mainly to match events with clients, and the rough method is to match resources in event data (also called asset information (such as machine list, IP, and the like)) with the resources (assets) information of clients in client asset management, so as to find out the association matching between events and clients.

And step 204, determining the successfully matched client as a target client influenced by the event, and generating event information of the client dimension aiming at the target client.

In this embodiment, the event information for the system dimension is converted into a form that the client understands. And the relevant information of the target client is supplemented in a targeted manner, and the event information of the client dimension is generated.

Optionally, the state of the newly added event is updated, and the data is stored. The state is that according to the data state in the monitoring system, the states of events generated by the fault management system mainly include addition, operation, termination and termination; the non-new addition referred to herein is primarily the event that has terminated and ended. The state information is added to the event information for the customer dimension.

Step 205, pushing event information of the customer dimension to the target customer.

In this embodiment, the event push may send important information, such as occurrence of a fault, end of a fault, and the like, to the client in real time through a short message, an email, or the like; all information and updates related to the event are synchronized to the front end for display.

The front end of the event management can also perform event summarization within a period of time (for example, a fault of xx service occurs xx times in the last week, and adjustment of xx service occurs xx times), so that a customer can conveniently master the cloud service operation quality within the last period of time, and the customer can be helped to perform stability optimization of self service.

Through the above parts, a complete scheme of event information management can be realized, and by utilizing the scheme, the fault of the cloud service side and the in-plan adjustment can be accurately and timely synchronized to the client, so that the client can more comprehensively, timely and accurately master the service quality of the cloud used by the client, and the decision of the client on fault disposal can be accelerated.

With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the method for pushing information according to the present embodiment. In the application scenario of fig. 3, operation and maintenance personnel of the cloud service or research and development personnel enter the upgrade information through an interface or an interface of the fault management system to obtain initial event information "upgrade xx cluster program". The fault management system will automatically supplement other event information such as time information, resource information, etc. to generate system dimensions, "2/2020/19/24: 00 upgrade xx cluster programs, during which xx cluster machines of the cluster will be out of service ". The event management system can periodically and frequently (with minute granularity, for example, one time is read in 1 minute when the fault with high timeliness requirement is in, and one time is read in 5 minutes when the fault with low timeliness requirement is in) read the content from the fault management system, and carry out certain completion or adjustment on the data. The event management system matches the information with the client asset information to generate a corresponding relation among the event, the client and the asset, determines a target client needing to be pushed, and generates client dimension event information aiming at the target client, for example, different clients are different in affected resources. And then, information pushing is carried out according to a pushing mode preset by a client.

The method mainly aims at enterprise customers with services deployed in a public cloud environment, and when the public cloud service fails or is adjusted in a plan, the scene of how to quickly and accurately acquire relevant information can effectively solve various problems such as untimely problem caused by artificial notification, meaningless disturbance problem caused by inaccurate notification range, information invalidity caused by incomplete event information and the like, and further can effectively improve the handling efficiency and accuracy of the customers when the cloud service is abnormal.

With further reference to fig. 4, a flow 400 of yet another embodiment of a method for pushing information is shown. The flow 400 of the method for pushing information comprises the following steps:

in response to detecting a failure or resource adjustment, initial event information is generated, step 401.

Step 402, supplementing time information and resource information based on the initial event information, and generating event information of system dimension.

Step 403, obtaining the corresponding relationship between the client and the resource thereof, and matching the corresponding relationship with the event information of the system dimension.

Step 404, determining the successfully matched client as the target client affected by the event, and generating the event information of the client dimension for the target client.

The

steps

401 and 404 are substantially the same as the

steps

201 and 204, and therefore, the description thereof is omitted.

Step 405 determines whether the target client has push rights.

In this embodiment, some sensitive information or internal information cannot be pushed to the client at will, and it is necessary to confirm whether the client has corresponding rights. The confirmation can be carried out manually or according to the set client authority. For example, if the setup a client cannot receive the resource change information, it is not pushed. Event filtering mainly considers that not all events can be pushed to a client side, for example, some sensitive business information or internal information cannot be pushed directly, so that certain filtering is required.

Step 406, pushing event information for the customer dimension to the target customer.

Step 406 is substantially the same as step 205 and therefore will not be described again.

Step 407, receiving feedback information of the target customer to assist the cloud service side in relevant adjustment and handling.

In this embodiment, after the client receives the relevant information, the client may operate and manage the event through the front end of the event management, for example, the mark has no influence, the feedback suggestion and the like, and the information may also be fed back to the operation and maintenance or the research and development staff of the cloud service, so as to assist the cloud service side in performing relevant adjustment and handling. The main purpose of the mark is to give the operation and maintenance personnel on the cloud side knowledge, and if some customers consider that the fault or adjustment has no influence on the operation and maintenance personnel on the cloud side, the processing means of the operation and maintenance personnel on the cloud side may be different, and the priority may be reduced. The feedback suggestion mainly helps the cloud side operation and maintenance personnel to do different corresponding schemes.

As can be seen from fig. 4, compared with the embodiment corresponding to fig. 2, the flow 400 of the method for pushing information in the present embodiment embodies the step of filtering the event. Therefore, the scheme described in the embodiment can ensure that the internal information is not leaked while carrying out targeted push.

With further reference to fig. 5, as an implementation of the methods shown in the above-mentioned figures, the present disclosure provides an embodiment of an apparatus for pushing information, which corresponds to the method embodiment shown in fig. 2, and which is particularly applicable to various electronic devices.

As shown in fig. 5, the apparatus 500 for pushing information of the present embodiment includes: generating section 501, complementing section 502, matching section 503, converting section 504, and pushing section 505. Wherein, the generating unit 501 is configured to generate initial event information in response to detecting a failure or resource adjustment; a completion unit 502 configured to generate event information of a system dimension based on the initial event information supplement time information and resource information; a matching unit 503 configured to obtain a correspondence between a client and a resource thereof, and match the correspondence with event information of a system dimension; a conversion unit 504 configured to determine the client successfully matched as a target client affected by the event and generate event information of a client dimension for the target client; a pushing unit 505 configured to push the event information of the client dimension to the target client.

In this embodiment, specific processing of the generating unit 501, the complementing unit 502, the matching unit 503, the converting unit 504, and the pushing unit 505 of the apparatus 500 for pushing information may refer to step 201, step 202, step 203, step 204, and step 205 in the corresponding embodiment of fig. 2.

In some optional implementations of this embodiment, the apparatus 500 further comprises a feedback unit (not shown in the drawings) configured to: and receiving feedback information of the target customer to assist the cloud service side in relevant adjustment and response.

In some optional implementations of this embodiment, the apparatus 500 further comprises a filtering unit (not shown in the drawings) configured to: after generating the event information of the client dimension aiming at the target client, if the target client is determined to have no push authority, filtering the event information of the client dimension, and not pushing the event information to the target client.

In some optional implementations of this embodiment, the apparatus 500 further comprises a digging unit (not shown in the drawings) configured to: and carrying out regular offline data mining and processing to generate the corresponding relation between the client and the resources of the client.

In some optional implementations of this embodiment, the apparatus 500 further comprises a display unit (not shown in the drawings) configured to: the event related information is displayed at the front end.

In some optional implementations of this embodiment, the conversion unit is further configured to: generating state information according to the monitored data state; event information for the system dimension is adjusted into a form understood by the client and state information is added.

Referring now to fig. 6, a schematic diagram of an electronic device (e.g., the server or terminal device of fig. 1) 600 suitable for use in implementing embodiments of the present disclosure is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a fixed terminal such as a digital TV, a desktop computer, and the like. The terminal device/server shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 6, electronic device 600 may include a processing means (e.g., central processing unit, graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 illustrates an electronic device 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided. Each block shown in fig. 6 may represent one device or may represent multiple devices as desired.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of embodiments of the present disclosure. It should be noted that the computer readable medium described in the embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In embodiments of the disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In embodiments of the present disclosure, however, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: generating initial event information in response to detecting a fault or resource adjustment; supplementing time information and resource information based on the initial event information, and generating event information of system dimensionality; acquiring the corresponding relation between a client and a resource thereof, and matching the corresponding relation with the event information of the system dimension; determining the successfully matched client as a target client influenced by the event, and generating event information of the client dimension aiming at the target client; and pushing the event information of the client dimension to the target client.

Computer program code for carrying out operations for embodiments of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor comprises a generating unit, a completion unit, a matching unit, a conversion unit and a pushing unit. Where the names of these units do not in some cases constitute a limitation on the units themselves, for example, a generating unit may also be described as a "unit that generates initial event information in response to detecting a failure or resource adjustment".

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is possible without departing from the inventive concept. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Claims

1. A method for pushing information, comprising:

generating initial event information in response to detecting a fault or resource adjustment;

supplementing time information and resource information based on the initial event information, and generating event information of system dimensionality;

acquiring a corresponding relation between a client and a resource thereof, and matching the corresponding relation with the event information of the system dimension;

determining the successfully matched client as a target client influenced by the event, and generating event information of a client dimension aiming at the target client;

and pushing the event information of the client dimension to the target client.

2. The method of claim 1, wherein the method further comprises:

and receiving feedback information of the target customer to assist the cloud service side in relevant adjustment and response.

3. The method of claim 1, wherein after generating event information for a customer dimension of the target customer, the method further comprises:

and if the target client is determined to have no push authority, filtering out the event information of the client dimension, and not pushing the event information to the target client.

4. The method of claim 1, wherein the method further comprises:

and carrying out regular offline data mining and processing to generate the corresponding relation between the client and the resources of the client.

5. The method of claim 1, wherein the method further comprises:

the event related information is displayed at the front end.

6. The method of any of claims 1-5, wherein the generating event information for a customer dimension of the target customer comprises:

generating state information according to the monitored data state;

event information for the system dimension is adapted to a form understood by the customer and the state information is added.

7. An apparatus for pushing information, comprising:

a generating unit configured to generate initial event information in response to detecting a failure or resource adjustment;

a completion unit configured to generate event information of a system dimension based on the initial event information supplement time information and resource information;

the matching unit is configured to acquire the corresponding relation between the client and the resource thereof and match the corresponding relation with the event information of the system dimension;

the conversion unit is configured to determine the client successfully matched as a target client influenced by the event and generate event information of a client dimension aiming at the target client;

a pushing unit configured to push event information of the client dimension to the target client.

8. The apparatus of claim 7, wherein the apparatus further comprises a feedback unit configured to:

9. The apparatus of claim 7, wherein the apparatus further comprises a filtering unit configured to:

after generating the event information of the client dimension aiming at the target client, if the target client is determined to have no push authority, filtering the event information of the client dimension, and not pushing the event information to the target client.

10. The apparatus of claim 7, wherein the apparatus further comprises a digging unit configured to:

11. The apparatus of claim 7, wherein the apparatus further comprises a display unit configured to:

the event related information is displayed at the front end.

12. The apparatus of one of claims 7-11, wherein the conversion unit is further configured to:

generating state information according to the monitored data state;

13. An electronic device for pushing information, comprising:

one or more processors;

a storage device having one or more programs stored thereon,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-6.

14. A computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 1-6.