Event information early warning method, device and program product
Patent Information
- Application Number
- CN202411875020.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-18
- Publication Date
- 2025-05-23
AI Technical Summary
The existing system cannot send an error message to the user in a timely manner under abnormal circumstances, resulting in the user being unable to sense and handle the abnormal situation in a timely manner.
By introducing a query event listener and a timeout event listener in the monitoring system, the service status and event status of event information are queried in real time, and whether to send an early warning signal is determined based on the event status.
When the interaction has not reached the end state, send an error message to the user in a timely manner to ensure that the user can sense and handle abnormal situations in a timely manner and avoid the amplified impact of abnormal situations.
Smart Images
Figure CN120029846A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present disclosure relate to the field of business monitoring technology, and in particular to an early warning method, device, and program product for event information. Background Art
[0002] As the number of financial assets connected to the financial platform increases, the number of business nodes increases, and the number of abnormal situations in order processing increases. Compensation or alarms are required for abnormal situations. The existing system only captures abnormal logs for abnormal error reporting, and then configures alarm information to users through the fast component to complete the alarm function.
[0003] However, with the above alarm strategy, if no error is reported, the interaction cannot reach a final state, that is, it is always in processing. In this case, the user cannot perceive it, but this abnormal situation also needs to be perceived by the user.
[0004] Therefore, there is an urgent need for an early warning method for event information, which can send an error message to the user in a timely manner when the interaction has not reached a final state, and then prompt the user to handle it in a timely manner. Summary of the invention
[0005] In order to solve the above technical problems or at least partially solve the above technical problems, the embodiments of the present disclosure provide an event information early warning method, device and program product.
[0006] A first aspect of an embodiment of the present disclosure provides an early warning method for event information, which is applied to a monitoring system. The method includes:
[0007] Receiving a request for creating event information sent by a business system through a first interface, and creating the event information and the event state of the event information according to the request for creating the event information; the initial state of the event state is a confirmation state;
[0008] Broadcasting the event information to a query event listener and a timeout event listener; wherein the query event listener and the timeout event listener are configured in the monitoring system;
[0009] The query event listener queries the business status of the event information from a preset business interface; wherein the preset business interface is provided by the business system;
[0010] The timeout event listener queries the event status of the event information in parallel; wherein the event status is associated with the business status;
[0011] According to the event status, determine whether to send an early warning signal.
[0012] In one example, before the query event listener queries the service status of the event information from a preset service interface, the method further includes:
[0013] The query event listener calls a preset business interface, and if it is found that the event information has been sent by the business system to other systems, the event status is modified from the confirmed status to the processing status.
[0014] In one example, the query event listener queries the service status of the event information from a preset service interface, including:
[0015] The query event listener loads the query configuration information of the event information and obtains the query frequency in the query configuration information;
[0016] Obtaining a delay time corresponding to the event information from the first delay task, and determining a query time for the event information according to the delay time and the current time;
[0017] The service status of the event information is queried from a preset service interface at the query time and according to the query frequency.
[0018] In one example, after querying the service status of the event information from a preset service interface at the query time and at the query frequency, the method further includes:
[0019] If the query event listener queries the business status of the event information from the preset business interface and finds that the business status is final, and the event status is found to be in process, the event status is modified from in process to finished.
[0020] In one example, the timeout event listener queries the event status of the event information in parallel, including:
[0021] The timeout event listener loads the monitoring configuration information of the event information in parallel, and obtains the timeout duration in the monitoring configuration information;
[0022] In the second delay task, according to the timeout duration and the current time, a monitoring time of the event information is determined;
[0023] The event status of the event information is queried at the monitoring time.
[0024] In one example, after querying the event status of the event information at the listening time, the method further includes:
[0025] If it is found that the event status is being processed, the timeout event listener modifies the event status from being processed to timeout and not processed.
[0026] In one example, the method further includes:
[0027] If the query event listener queries the business status of the event information from the preset business interface and finds that the business status of the event is final, and the event status is found to be timed out and not processed, the event status is modified from timed out and not processed to ended.
[0028] In one example, after the query event listener queries the event information from the preset service interface and the service state is a final state, the method further includes:
[0029] Calling a second interface, and obtaining an event information end request from the business system through the second interface;
[0030] The event information is ended according to the event information end request; wherein the second interface is used by the business system to send the event information end request to the monitoring system.
[0031] In one example, determining whether to send an early warning signal according to the event status includes:
[0032] The scheduled task queries the event status;
[0033] If the event status is found to be timed out and not processed, a warning signal is sent;
[0034] If the event status is found to be in progress or changed from in progress to completed, no processing will be performed;
[0035] If it is found that the event status is changed from timeout and unprocessed to completed, the warning signal is cancelled.
[0036] A second aspect of the embodiments of the present disclosure provides an early warning device for event information, which is applied to a monitoring system, and includes:
[0037] A receiving module, configured to receive a request for creating event information sent by a business system through a first interface, and to create the event information and an event state of the event information according to the request for creating the event information; the initial state of the event state is a confirmation state;
[0038] A broadcast module, used for broadcasting the event information to a query event listener and a timeout event listener; wherein the query event listener and the timeout event listener are configured in the monitoring system;
[0039] A first query module, used for the query event listener to query the business status of the event information from a preset business interface; wherein the preset business interface is provided by the business system;
[0040] A second query module, used for the timeout event listener to query the event status of the event information in parallel; wherein the event status is associated with the business status;
[0041] The determination module is used to determine whether to send an early warning signal according to the event status.
[0042] A third aspect of an embodiment of the present disclosure provides an electronic device, comprising: a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the method of the first aspect above.
[0043] A fourth aspect of an embodiment of the present disclosure provides a computer program product, including a computer program, which implements the method described in the first aspect when executed by a processor.
[0044] The disclosed embodiment provides an event information early warning method, device and program product, which are applied to a monitoring system, and the method includes: receiving a request for creating event information sent by a business system through a first interface, and creating the event information and the event status of the event information according to the request for creating the event information; the initial state of the event status is a confirmation state; broadcasting the event information to a query event listener and a timeout event listener; wherein the query event listener and the timeout event listener are configured in the monitoring system; the query event listener queries the business status of the event information from a preset business interface; wherein the preset business interface is provided by the business system; the timeout event listener queries the event status of the event information in parallel; wherein the event status has an association relationship with the business status; and determining whether to send an early warning signal according to the event status. By adopting this technical solution, when the interaction has not reached the final state, an error message can be sent to the user in a timely manner, and the user can be prompted to handle it in a timely manner. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0046] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0047] Figure 1 It is a flowchart of an early warning method for event information provided by an embodiment of the present disclosure;
[0048] Figure 2 It is a schematic diagram of an architecture of an event information warning provided by an embodiment of the present disclosure;
[0049] Figure 3 It is a flowchart of an early warning method for event information provided by an embodiment of the present disclosure;
[0050] Figure 4 This is a flow diagram of an event information warning provided by an embodiment of the present disclosure;
[0051] Figure 5 It is a structural diagram of an early warning device for event information provided by an embodiment of the present disclosure;
[0052] Figure 6 It is a structural diagram of an early warning device for event information provided by an embodiment of the present disclosure;
[0053] Figure 7 It is a structural schematic diagram of an electronic device in an embodiment of the present disclosure. DETAILED DESCRIPTION
[0054] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.
[0055] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.
[0056] Figure 1 1 is a flow chart of an event information early warning method provided by an embodiment of the present disclosure. The method is applied to a monitoring system and can be executed by an electronic device. The electronic device can be exemplarily understood as a device such as a mobile phone, a tablet computer, a laptop computer, a desktop computer, a smart TV, etc. Figure 1 As shown, the method provided in this embodiment includes the following steps:
[0057] S101. Receive a request for creating event information sent by a business system through a first interface, and create event information and event status of the event information according to the request for creating event information; the initial status of the event status is a confirmation status.
[0058] In one example, event information is business information that is exchanged between a business system and other systems. Other systems may be payment systems or user systems. Event information may be audit information for fund lending. Specifically, event information may include at least one of the following: event ID, event ticket number, event type, business status, event status, event context information, application name, product code, and channel code.
[0059] In this embodiment, after the business system interacts with other systems, a request to create the interactive event information is sent to the monitoring system through the first interface. The first interface is an interface for the monitoring system to create events. After receiving the request to create the event information, the monitoring system creates the event information on the monitoring system according to the request to create the event information, and creates the event status of the event information. The event status is used to characterize the process status of the event information. The event status can be: confirmed, in process, timed out and ended. The initial state of the event status is the confirmed state, which can be recorded as CONFIRMED. If the event status is in process, it can be recorded as PROCESSING. If the event status is timed out and not processed, it can be recorded as PENDING.
[0060] S102: broadcast the event information to the query event listener and the timeout event listener; wherein the query event listener and the timeout event listener are configured in the monitoring system.
[0061] In one example, the query event listener is used to query the business status of the event information; the timeout event listener is used to query the event status of the event information; wherein the event status is associated with the business status.
[0062] In one example, the query event listener and the timeout event listener are configured in the monitoring system, and the two can be executed independently.
[0063] In one example, the query event listener can be implemented by a first code file, and the timeout event listener can be implemented by a second code file. The business status of the event information is used to characterize the state of interaction between the business system and other systems. Furthermore, the business status can be processing, success / failure. Among them, if the business status is processing, it can be recorded as PROCESSING. If the business status is success / failure, it can be recorded as SUCCESS / FAIL.
[0064] In this embodiment, the event status is associated with the business status. Specifically, if the business status is in processing, the corresponding event status is in processing or timeout. If the business status is in the final state, that is, success / failure, the corresponding event status is ended.
[0065] S103. The query event listener queries the business status of the event information from a preset business interface; wherein the preset business interface is provided by the business system.
[0066] In one example, the preset business interface is used to connect the business system and the monitoring system, and is specifically used for the monitoring system to query the business status of event information of the business system.
[0067] S104. The timeout event listener queries the event status of the event information in parallel; wherein the event status is associated with the business status.
[0068] In one example, the timeout event listener and the query event listener are executed in parallel. Furthermore, the event state is associated with the business state.
[0069] S105: Determine whether to send an early warning signal according to the event status.
[0070] In one example, the timeout event listener is used to query the event status, and after determining the event status, determine whether to send an early warning signal according to the event status.
[0071] To explain this embodiment more clearly, see Figure 2 A schematic diagram of the architecture of an event information warning is shown.
[0072] The disclosed embodiment provides an early warning method for event information, which is applied to a monitoring system, and the method includes: receiving a request for creating event information sent by a business system through a first interface, and creating event information and event status of the event information according to the request for creating event information; the initial state of the event status is a confirmation state; broadcasting the event information to a query event listener and a timeout event listener; wherein the query event listener and the timeout event listener are configured in the monitoring system; the query event listener queries the business status of the event information from a preset business interface; wherein the preset business interface is provided by the business system; the timeout event listener queries the event status of the event information in parallel; wherein the event status has an association with the business status; and determining whether to send an early warning signal according to the event status. By adopting this technical solution, when the interaction has not reached a final state, an error message can be sent to the user in a timely manner, and the user can be prompted to handle it in a timely manner.
[0073] Figure 3 This is a flow chart of an event information early warning method provided by an embodiment of the present disclosure. The embodiment of the present disclosure is optimized on the basis of the above embodiment, and the embodiment of the present disclosure can be combined with various optional solutions in one or more of the above embodiments.
[0074] like Figure 3As shown, the early warning method of the event information is applied to the monitoring system and may include the following steps:
[0075] S301. Receive a request for creating event information sent by a business system through a first interface, and create event information and event status of the event information according to the request for creating event information; the initial status of the event status is a confirmation status.
[0076] In an example, this step may refer to the content of step S101.
[0077] S302: broadcast the event information to the query event listener and the timeout event listener; wherein the query event listener and the timeout event listener are configured in the monitoring system.
[0078] In an example, this step may refer to the content of step S102.
[0079] S303, the query event listener calls the preset business interface, and if it is found that the event information has been sent by the business system to other systems, the event status is changed from the confirmed state to the processing state.
[0080] In one example, the preset business interface is provided by the business system. When the query event listener calls the preset business interface, it means that the event information has started to be processed, and the event status is modified from the confirmed state to the processing state.
[0081] S304: The query event listener queries the service status of the event information from a preset service interface.
[0082] In one example, the query event listener queries the business status of event information from a preset business interface, including:
[0083] Query the event listener, load the query configuration information of the event information, and obtain the query frequency in the query configuration information;
[0084] Obtaining the delay time corresponding to the event information from the first delay task, and determining the query time of the event information according to the delay time and the current time;
[0085] At the query time, the business status of the event information is queried from the preset business interface according to the query frequency.
[0086] In one example, the query configuration information corresponding to different event information is different. The query configuration information includes the query frequency, and the query frequencies corresponding to different event information are different. The first delay task can be a redission delay task. The delay times corresponding to different event information are different. For example, the delay time corresponding to event information A is 30 minutes. The current time is the time when the event information arrives at the first delay task, and the query time of the event information is the current time postponed by the delay time. For example, the current time corresponding to event information A is 13 o'clock, and the delay time corresponding to event information A is 30 minutes, then the query time of the event information is 13:30. Furthermore, the query event listener queries the business status of the event information from the preset business interface according to the query frequency at 13:30.
[0087] In one example, after querying the service status of the event information from the preset service interface at the query time according to the query frequency, the method further includes:
[0088] If the query event listener queries the business status of the event information from the preset business interface and the business status of the event is final, and the event status is found to be in process, the event status is modified from in process to finished.
[0089] In one example, if the query event listener queries the event information from the preset business interface and the business status is final, since the business status is in the final state, that is, success / failure, the corresponding event status is ended. And if the event status is found to be in progress, it means that the event status has changed at this time, and the event status is changed from in progress to ended.
[0090] In one example, after the query event listener queries the event information from the preset business interface for a business state that is a final state, the method further includes:
[0091] Calling the second interface, and obtaining the event information end request from the business system through the second interface;
[0092] The event information is ended according to the event information end request; wherein the second interface is used by the business system to send the event information end request to the monitoring system.
[0093] In one example, the second interface is used for the business system to send an event information end request to the monitoring system, wherein the second interface is an interface for the monitoring system to end events. If the business state of the query event listener querying the event information from the preset business interface is a terminal state, it means that the interaction between the business system and the other system has been completed, and then the second interface is called to obtain the event information end request from the business system through the second interface, and then the monitoring system ends the event information according to the event information end request.
[0094] S305: The timeout event listener queries the event status of the event information in parallel.
[0095] In one example, a timeout event listener queries the event status including:
[0096] The timeout event listener loads the listening configuration information of the event information in parallel and obtains the timeout duration in the listening configuration information;
[0097] In the second delay task, the monitoring time of the event information is determined according to the timeout duration and the current time;
[0098] Query the event status of event information during monitoring time.
[0099] In one example, different event information corresponds to different monitoring configuration information. The monitoring configuration information includes a timeout duration, which is used to indicate the event information response duration expected by the business system. If the timeout duration is exceeded, the business system considers that other systems have timed out in processing the event information response.
[0100] In one example, the second delay task may be a redis delay task. In the second delay task, the current time is delayed by the timeout duration to obtain the listening time of the event information, and then the event status is queried during the listening time.
[0101] In one example, after querying the event status of the event information at the listening time, the method further includes:
[0102] If the event status is found to be in processing, the timeout event listener will change the event status from in processing to timeout and unprocessed.
[0103] In one example, if the event status is found to be in process during the monitoring time, it indicates that other systems have timed out for processing the event information of the business system, and a timeout event listener is needed to change the event status from in process to timeout and unprocessed.
[0104] In one example, the method further includes:
[0105] If the query event listener queries the business status of the event information from the preset business interface and the business status of the event is final, and the event status is timed out and not processed, the event status is changed from timed out and not processed to ended.
[0106] In one example, since the business status is in a terminal state, that is, success / failure, the corresponding event status is ended. Therefore, when the event status is found to be timed out and not processed, the event status needs to be changed from timed out and not processed to ended.
[0107] In one example, after the query event listener queries the event information from the preset business interface for a business state that is a final state, the method further includes:
[0108] Calling the second interface, and obtaining the event information end request from the business system through the second interface;
[0109] The event information is ended according to the event information end request.
[0110] In one example, the second interface is used for the business system to send an event information end request to the monitoring system.
[0111] In one example, the second interface is used for the business system to send an event information end request to the monitoring system, wherein the second interface is an interface for the monitoring system to end events. If the business state of the query event listener querying the event information from the preset business interface is a terminal state, it means that the interaction between the business system and the other system has been completed, and then the second interface is called to obtain the event information end request from the business system through the second interface, and then the monitoring system ends the event information according to the event information end request.
[0112] S306: Scheduled task queries event status.
[0113] In one example, the scheduled task may be a xxljob task, which is preset. The event status is queried according to the scheduled frequency through the scheduled task.
[0114] S307: If the event status is found to be timed out and not processed, a warning signal is sent.
[0115] In one example, the warning signal may be sent to a mailbox or terminal device designated by the user, which is not limited here.
[0116] S308: If the event status is found to be in process or changed from in process to finished, no processing is performed.
[0117] In one example, if the event status is "processing", it means that the event information is still being processed and has not timed out. If the event status is changed from "processing" to "completed", it means that the event information has been processed within the timeout period, and no processing is performed, that is, no alarm signal is sent.
[0118] S309: If it is found that the event status is changed from timeout and unprocessed to completed, the warning signal is cancelled.
[0119] In one example, if the query finds that the event status has been changed from timeout and unprocessed to ended, since an alarm signal has been sent when the event status was timeout and unprocessed, the alarm signal needs to be canceled after the event status is changed from timeout and unprocessed to ended.
[0120] For a clearer explanation, see Figure 4 A schematic diagram of the flow of event information warning is shown.
[0121] The disclosed embodiment provides an early warning method for event information, which is applied to a monitoring system. The method includes: a query event listener calls a preset business interface to modify the event status from a confirmed state to a processing state, a query event listener queries the business status of the event information from a preset business interface, and a parallel timeout event listener queries the event status. At the same time, a scheduled task queries the event status. If the event status is found to be timed out and not processed, an early warning signal is sent. If the event status is found to be processing or modified from processing to finished, no processing is performed. If the event status is found to be modified from timed out and not processed to finished, the early warning signal is canceled. By adopting this technical solution, the processing timeliness of event information can be monitored, and timely alarms and compensation processing can be performed in abnormal situations to avoid the expansion of the impact of abnormal business operations.
[0122] Figure 5 1 is a schematic diagram of a structure of an early warning device for event information provided by an embodiment of the present disclosure, which is applied to a monitoring system. The early warning device for event information can be understood as the above-mentioned electronic device or a part of the functional modules in the above-mentioned electronic device. Figure 5 As shown, the early warning device 50 of the event information includes:
[0123] The receiving module 501 is used to receive a request for creating event information sent by the business system through the first interface, and create event information and event status of the event information according to the request for creating event information; the initial status of the event status is a confirmation status.
[0124] The broadcast module 502 is used to broadcast the event information to the query event listener and the timeout event listener; wherein the query event listener and the timeout event listener are configured in the monitoring system.
[0125] The first query module 503 is used to query the service status of the event listener querying the event information from the preset service interface; wherein the preset service interface is provided by the service system.
[0126] The second query module 504 is used for the timeout event listener to query the event status of the event information in parallel; wherein the event status is associated with the business status.
[0127] The determination module 505 is used to determine whether to send an early warning signal according to the event status.
[0128] The device provided in this embodiment can execute the method of any of the above embodiments, and its execution method and beneficial effects are similar, which will not be repeated here.
[0129] Figure 61 is a schematic diagram of a structure of an early warning device for event information provided by an embodiment of the present disclosure, which is applied to a monitoring system. The early warning device for event information can be understood as the above-mentioned electronic device or a part of the functional modules in the above-mentioned electronic device. Figure 6 As shown, the early warning device 60 of the event information includes:
[0130] The receiving module 601 is used to receive a request for creating event information sent by the business system through the first interface, and create event information and event status of the event information according to the request for creating event information; the initial status of the event status is a confirmation status.
[0131] The broadcast module 602 is used to broadcast event information to the query event listener and the timeout event listener; wherein the query event listener and the timeout event listener are configured in the monitoring system.
[0132] The first query module 603 is used to query the service status of the event listener querying the event information from the preset service interface; wherein the preset service interface is provided by the service system.
[0133] The second query module 604 is used for the timeout event listener to query the event status of the event information in parallel; wherein the event status is associated with the business status.
[0134] The determination module 605 is used to determine whether to send an early warning signal according to the event status.
[0135] In one example, before the first query module, the apparatus 60 further includes:
[0136] The first modification module 606 is used to query the event listener to call the preset business interface. If the event information is found to have been sent by the business system to other systems, the event status is modified from the confirmed state to the processing state.
[0137] In one example, the first query module 603 includes:
[0138] The first loading submodule is used to query the event listener, load the query configuration information of the event information, and obtain the query frequency in the query configuration information;
[0139] A first determination submodule is used to obtain a delay time corresponding to the event information from the first delay task, and determine a query time for the event information according to the delay time and the current time;
[0140] The first query submodule is used to query the service status of the event information from a preset service interface at a query time according to a query frequency.
[0141] In one example, after the first query submodule, the apparatus further includes:
[0142] The second query submodule is used to modify the event status from being processed to being finished if the business status of the event information queried by the query event listener from the preset business interface is a final state and the event status queried is being processed.
[0143] In one example, the second query module 604 includes:
[0144] The second loading submodule is used for the timeout event listener, which loads the listening configuration information of the event information in parallel and obtains the timeout duration in the listening configuration information;
[0145] A second determining submodule is used to determine the monitoring time of the event information according to the timeout duration and the current time in the second delay task;
[0146] The third query submodule is used to query the event status of the event information during the monitoring time.
[0147] In one example, after the third query submodule, the second query module 604 further includes:
[0148] The fourth query submodule is used to, if the event status is found to be in processing, the timeout event listener is used to modify the event status from in processing to timeout and unprocessed.
[0149] In one example, the apparatus 60 further includes:
[0150] The second modification module 607 is used to modify the event status from timeout and unprocessed to end if the business status of the event information queried by the query event listener from the preset business interface is terminal and the event status queried is timeout and unprocessed.
[0151] In one example, after the second modification module 607, the apparatus further includes:
[0152] The calling module 608 is used to call the second interface and obtain the event information end request from the business system through the second interface.
[0153] The ending module 609 is used to end the event information according to the event information end request.
[0154] In one example, the determination module 605 includes:
[0155] The fifth query submodule is used to query the event status of the scheduled task;
[0156] The sixth query submodule is used to send an early warning signal if the event status is found to be timed out and not processed;
[0157] The seventh query submodule is used for not processing if the event status is found to be in process or changed from in process to finished;
[0158] The eighth query submodule is used to cancel the warning signal if it is found that the event status is changed from timeout and unprocessed to ended.
[0159] The device provided in this embodiment can execute the method of any of the above embodiments, and its execution method and beneficial effects are similar, which will not be repeated here.
[0160] An embodiment of the present disclosure further provides an electronic device, which includes: a memory, in which a computer program is stored; and a processor, which is used to execute the computer program. When the computer program is executed by the processor, the method of any of the above embodiments can be implemented.
[0161] For example, Figure 7 Schematic diagram of the structure of an electronic device in the embodiment of the present disclosure. Figure 7 , which shows a schematic diagram of the structure of an electronic device 1000 suitable for implementing the embodiment of the present disclosure. The electronic device 1000 in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.
[0162] like Figure 7 As shown, the electronic device 1000 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1008 into a random access memory (RAM) 1003. In the RAM 1003, various programs and data required for the operation of the electronic device 1000 are also stored. The processing device 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.
[0163] Typically, the following devices may be connected to the I / O interface 1005: an input device 1006 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 1007 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1008 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 may allow the electronic device 1000 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 7The electronic device 1000 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.
[0164] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart may be implemented as a computer software program.
[0165] An embodiment of the present disclosure provides a computer program product, including a computer program, which implements the method described above when executed by a processor.
[0166] In such an embodiment, the computer program may be downloaded and installed from the network through the communication device 1009, or installed from the storage device 1008, or installed from the ROM 1002. When the computer program is executed by the processing device 1001, the above functions defined in the method of the embodiment of the present disclosure are performed.
[0167] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.
[0168] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.
[0169] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.
[0170] The above-mentioned computer-readable medium carries one or more programs. When the above-mentioned one or more programs are executed by the electronic device, the electronic device: receives a request for creating event information sent by the business system through the first interface, and creates event information and an event status of the event information according to the request for creating event information; the initial state of the event status is a confirmation state; the event information is broadcast to a query event listener and a timeout event listener; wherein the query event listener and the timeout event listener are configured in the monitoring system; the query event listener queries the business status of the event information from a preset business interface; wherein the preset business interface is provided by the business system; the timeout event listener queries the event status of the event information in parallel; wherein the event status and the business status have an associated relationship; and determines whether to send a warning signal according to the event status.
[0171] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving 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 may be connected to an external computer (e.g., through the Internet using an Internet service provider).
[0172] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented with a system of dedicated hardware that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0173] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware, wherein the name of a unit does not, in some cases, limit the unit itself.
[0174] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.
[0175] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection of one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0176] The embodiments of the present disclosure further provide a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method of any of the above embodiments can be implemented. The execution method and beneficial effects are similar and will not be repeated here.
[0177] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.
[0178] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for early warning of event information, characterized in that: Applied to a monitoring system, the method comprises: Receiving a request for creating event information sent by a business system through a first interface, and creating the event information and the event state of the event information according to the request for creating the event information; the initial state of the event state is a confirmation state; Broadcasting the event information to a query event listener and a timeout event listener; wherein the query event listener and the timeout event listener are configured in the monitoring system; The query event listener queries the business status of the event information from a preset business interface; wherein the preset business interface is provided by the business system; The timeout event listener queries the event status of the event information in parallel; wherein the event status is associated with the business status; Determine whether to send an early warning signal based on the event status.
2. The method according to claim 1, characterized in that Before the query event listener queries the service status of the event information from a preset service interface, the method further includes: The query event listener calls a preset business interface, and if it is found that the event information has been sent by the business system to other systems, the event status is modified from the confirmed status to the processing status.
3. The method according to claim 1, characterized in that The query event listener queries the service status of the event information from a preset service interface, including: The query event listener loads the query configuration information of the event information and obtains the query frequency in the query configuration information; Obtaining a delay time corresponding to the event information from the first delay task, and determining a query time for the event information according to the delay time and the current time; The service status of the event information is queried from a preset service interface at the query time and according to the query frequency.
4. The method according to claim 3, characterized in that After querying the service status of the event information from a preset service interface at the query time and according to the query frequency, the method further includes: If the query event listener queries the business status of the event information from the preset business interface and finds that the business status is final, and the event status is found to be in process, the event status is modified from in process to finished.
5. The method according to claim 1, characterized in that The timeout event listener queries the event status of the event information in parallel, including: The timeout event listener loads the monitoring configuration information of the event information in parallel, and obtains the timeout duration in the monitoring configuration information; In the second delay task, according to the timeout duration and the current time, a monitoring time of the event information is determined; The event status of the event information is queried at the monitoring time.
6. The method according to claim 5, characterized in that After querying the event status of the event information at the listening time, the method further includes: If it is found that the event status is being processed, the timeout event listener modifies the event status from being processed to timeout and not processed.
7. The method according to claim 6, characterized in that The method further comprises: If the query event listener queries the business status of the event information from the preset business interface and finds that the business status of the event is final, and the event status is found to be timed out and not processed, the event status is modified from timed out and not processed to ended.
8. The method according to claim 4 or 7, characterized in that: After the query event listener queries the event information from the preset service interface and the service state is a final state, the method further includes: Calling a second interface, and obtaining an event information end request from the business system through the second interface; The event information is ended according to the event information end request.
9. The method according to claim 1, characterized in that: The determining whether to send an early warning signal according to the event status includes: The scheduled task queries the event status; If the event status is found to be timed out and not processed, a warning signal is sent; If the event status is found to be in progress or changed from in progress to completed, no processing will be performed; If it is found that the event status is changed from timeout and unprocessed to completed, the warning signal is cancelled.
10. An electronic device, characterized in that: include: A processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the method according to any one of claims 1 to 9.
11. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 9.