CN112860271B - New and old system switching method, device, equipment and storage medium - Google Patents
New and old system switching method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112860271B CN112860271B CN202110342609.7A CN202110342609A CN112860271B CN 112860271 B CN112860271 B CN 112860271B CN 202110342609 A CN202110342609 A CN 202110342609A CN 112860271 B CN112860271 B CN 112860271B
- Authority
- CN
- China
- Prior art keywords
- new call
- state
- abnormal
- new
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 230000002159 abnormal effect Effects 0.000 claims abstract description 87
- 238000012544 monitoring process Methods 0.000 claims abstract description 27
- 230000015654 memory Effects 0.000 claims description 30
- 238000001514 detection method Methods 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 9
- 230000005856 abnormality Effects 0.000 claims description 3
- 238000012360 testing method Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 12
- 238000004891 communication Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 230000005855 radiation Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Hardware Redundancy (AREA)
Abstract
Provided herein are a method, apparatus, device and storage medium for switching between a new system and an old system, wherein the method comprises: cutting the target interface of the target calling party according to the to-be-cut flow table to obtain a new call relation after cutting the flow; monitoring the success rate of a target calling party to call a target interface in the new calling relation in real time; monitoring a basic state corresponding to a target interface in the new call relation in real time; and determining and cutting back the interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation. The method provided by the invention can reduce the manpower consumption and realize automatic system switching.
Description
Technical Field
The present invention relates to the field of system switching, and in particular, to a method, an apparatus, a device, and a storage medium for switching between a new system and an old system.
Background
New and old system switching is a common item in the current localized wave. In large projects of banks, the switching process of new and old systems is very complex, such as the process of switching personal finance applications from an IBM host to a domestic development platform host core, and involves the switching of multiple interfaces of 108 channel application systems 4700. Because each interface corresponds to a plurality of calling parties (including bank counter, ATM, mobile phone bank and the like), each interface needs to cut in batches, the accumulated cutting flow scene exceeds 1 ten thousand times, and the scene that the old system needs to be cut back due to insufficient test or other problems exists in the switching process.
In the prior art, in the switching and back-switching processes of new and old systems, the switching or back-switching operation is executed after the condition of switching or back-switching is often judged manually. The process of judging by manpower consumes manpower, and the degree of automation and informatization is low. Therefore, a new and old system switching method is needed, which can reduce the manpower consumption and realize automatic system switching.
Disclosure of Invention
The embodiment of the invention aims to provide a method, a device, equipment and a storage medium for switching between a new system and an old system, so as to reduce labor consumption and realize automatic system switching.
To achieve the above object, in one aspect, an embodiment herein provides a method for switching between a new system and an old system, where the method includes:
cutting the target interface of the target calling party according to the to-be-cut flow table to obtain a new call relation after cutting the flow;
monitoring the success rate of a target calling party to call a target interface in the new calling relation in real time;
monitoring a basic state corresponding to a target interface in the new call relation in real time;
and determining and cutting back the interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation.
Preferably, the determining and cutting back the interface corresponding to the abnormal new call relationship according to the success rate of the new call relationship includes:
judging whether the success rate of the new call relationship is outside a confidence interval of the new call relationship and continuously exceeds a preset time period;
if the success rate of the new call relationship is outside the confidence interval of the new call relationship and continuously exceeds a preset time period, determining the new call relationship as an abnormal new call relationship, and cutting back an interface corresponding to the abnormal new call relationship.
Preferably, the determining and cutting back the interface corresponding to the abnormal new call relationship according to the success rate of the new call relationship further includes:
determining the number of abnormal new call relations corresponding to the same interface in a set time period;
judging whether the number is larger than a set number;
and if the number is larger than the set number, determining all new call relations corresponding to the interfaces as abnormal new call relations.
Preferably, the basic state corresponding to the target interface in the new call relationship includes: network state, fault domain state, CPU state, memory state and server heartbeat detection state.
Preferably, the determining and cutting back the interface corresponding to the abnormal new call relationship according to the basic state corresponding to the target interface in the new call relationship includes:
determining a state flag bit of each state corresponding to the target interface in the new call relation according to the network state, the fault domain state, the CPU state, the memory state and the server heartbeat detection state corresponding to the target interface in the new call relation;
judging whether an abnormal mark exists in all the state mark bits corresponding to the target interfaces in the new call relation;
if the abnormal mark exists, the new call relation is determined to be an abnormal new call relation, and the interface corresponding to the abnormal new call relation is cut back.
Preferably, determining the status flag bit of each status corresponding to the target interface in the new call relationship according to the network status, the fault domain status, the CPU status, the memory status and the server heartbeat detection status corresponding to the target interface in the new call relationship includes:
judging whether an abnormal state exists in the states according to a network state, a fault domain state, a CPU state, a memory state and a server heartbeat detection state corresponding to the target interface in the new call relation, wherein the abnormal state continuously exceeds a calibration time period;
if an abnormal state exists in the states and the abnormality continues to exceed a calibrated time period, determining a state flag bit corresponding to the state as an abnormal flag;
otherwise, defaulting the state flag bit corresponding to the state to be a normal flag.
Preferably, the determining and cutting back the interface corresponding to the abnormal new call relationship according to the basic state corresponding to the target interface in the new call relationship further includes:
and determining all new call relations which are the same as the interface called by the abnormal new call relation as abnormal new call relations.
In another aspect, an embodiment herein provides an apparatus for switching between a new system and an old system, where the apparatus includes:
and a tangential flow module: cutting the target interface of the target calling party according to the to-be-cut flow table to obtain a new call relation after cutting the flow;
the success rate monitoring module: monitoring the success rate of a target calling party to call a target interface in the new calling relation in real time;
the basic state monitoring module: monitoring a basic state corresponding to a target interface in the new call relation in real time;
and (3) a back cutting module: and determining and cutting back the interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation.
In yet another aspect, embodiments herein also provide a computer device including a memory, a processor, and a computer program stored on the memory, which when executed by the processor, performs instructions of any of the methods described above.
In yet another aspect, embodiments herein also provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor of a computer device, performs instructions of any of the methods described above.
As can be seen from the technical solutions provided in the embodiments herein, the new and old systems are switched by using a pre-established to-be-switched table, and by monitoring the success rate of calling the target interface by the target caller in the new call relationship and the basic state of the target interface in real time, the abnormal new call relationship is determined, and the interfaces thereof are switched back. The whole process is automatically cut and back cut through the system, manual judgment and intervention are not needed, the manpower consumption is reduced, and the degree of automation is high.
The foregoing and other objects, features and advantages will be apparent from the following more particular description of preferred embodiments, as illustrated in the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments herein or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments herein and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.
Fig. 1 is a schematic flow chart of a method for switching between a new system and an old system according to an embodiment of the present disclosure;
FIG. 2 is a schematic flow chart of an interface for determining an abnormal new call relationship according to a success rate according to an embodiment of the present disclosure;
FIG. 3 is another flow diagram of an interface for determining an exception new call relationship according to a success rate provided by embodiments herein;
FIG. 4 is a schematic flow chart of an interface for determining an abnormal new call relationship according to a basic state according to an embodiment of the present disclosure;
FIG. 5 is another flow diagram of an interface for determining an exception new call relationship according to a base state provided by embodiments herein;
fig. 6 is a schematic block diagram of an apparatus for switching between a new system and an old system according to an embodiment of the present disclosure;
fig. 7 shows a schematic structural diagram of a computer device provided in embodiments herein.
Description of the drawings:
100. a tangential flow module;
200. a success rate monitoring module;
300. a basic state monitoring module;
400. a back-cut module;
702. a computer device;
704. a processor;
706. a memory;
708. a driving mechanism;
710. an input/output module;
712. an input device;
714. an output device;
716. a presentation device;
718. a graphical user interface;
720. a network interface;
722. a communication link;
724. a communication bus.
Detailed Description
The following description of the embodiments of the present disclosure will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all embodiments of the disclosure. All other embodiments, based on the embodiments herein, which a person of ordinary skill in the art would obtain without undue burden, are within the scope of protection herein.
In the prior art, in the switching and back-switching processes of new and old systems, the switching or back-switching operation is executed after the condition of switching or back-switching is often judged manually. The process of judging by manpower consumes manpower, and the degree of automation and informatization is low.
In order to solve the above problems, embodiments herein provide a method for switching between a new system and an old system, which can reduce manpower consumption and realize automatic system switching. Fig. 1 is a schematic diagram of steps of a method for switching between a new system and an old system according to an embodiment herein, where the method includes steps as described in the examples or flowcharts, but may include more or less steps based on conventional or non-inventive labor. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When a system or apparatus product in practice is executed, it may be executed sequentially or in parallel according to the method shown in the embodiments or the drawings.
Referring to fig. 1, a method for switching between a new system and an old system, the method comprising:
s101: and cutting the target interface of the target calling party according to the to-be-cut flow table to obtain a new call relation after cutting the flow.
S102: and monitoring the success rate of the target calling party to call the target interface in the new calling relation in real time.
S103: and monitoring the basic state corresponding to the target interface in the new call relation in real time.
S104: and determining and cutting back the interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation.
And carrying out stream cutting of the new and old systems through a pre-established stream table to be cut, and determining an abnormal new call relation and cutting back the interface of the new and old systems by monitoring the success rate of calling the target interface by the target calling party in the new call relation and the basic state of the target interface in real time. The whole process is automatically cut and back cut through the system, manual judgment and intervention are not needed, the manpower consumption is reduced, and the degree of automation is high.
Before switching between the new system and the old system, firstly, a to-be-switched flow table is established, and the call relationship between the calling party and the interface in the old system and the call relationship between the calling party and the interface in the new system are recorded in the to-be-switched flow table. As shown in table 1, the call relationship between the caller and the interface in the new and old systems of the legal entity relationship query interface of legal entity is recorded, the first piece of data is the call relationship in the old system, and the second piece of data is the call relationship in the new system.
TABLE 1
After the tangential flow table is established, the calling party needs to be batched before the system is switched. In a calling relationship (one calling party calls one interface), all calling parties are divided into trial batches, a first batch and a second batch … … Nth batch, and the specific batch number can be determined according to the actual conditions of different systems. The first batch can cut only after the test point batch cuts successfully and runs continuously and successfully for a period of time, the second batch can cut only after the first batch cuts successfully and runs continuously and successfully for a period of time, and the third batch to the nth batch are the same and are not repeated.
Before system switching, all interfaces need to be subjected to function test and switch cut-flow test to check whether the interfaces are normal or not, and similarly, all calling parties also need to be subjected to function test and switch cut-flow test to check whether the calling parties are normal or not. When the tests of the interface and the calling party are passed, starting from the calling party of the test lot, the interface of the calling party is cut according to the to-be-cut table, and a new call relation (one calling party calls one interface in a new system) after the cutting is obtained. The new system has a plurality of interfaces A, B … …, and a plurality of calling parties 1 and 2 … … call the interfaces respectively to form a plurality of new calling relations, such as calling party 1 calls interface A, and calling party 1 calls interface B, which are two new calling relations.
Referring to fig. 2, in this embodiment, determining and cutting back an interface corresponding to the abnormal new call relationship according to the success rate of the new call relationship includes:
s201: judging whether the success rate of the new call relationship is outside the confidence interval of the new call relationship and continuously exceeds a preset time period.
S202: if the success rate of the new call relationship is outside the confidence interval of the new call relationship and continuously exceeds a preset time period, determining the new call relationship as an abnormal new call relationship, and cutting back an interface corresponding to the abnormal new call relationship.
Specifically, firstly, a confidence interval of a new call relationship is determined, the success rate of calling a target interface in an old system by a target calling party in the new call relationship is obtained, and the confidence interval is determined according to the success rate. The probability of successful call of the target caller in the old system in each period of time (which may be 1 hour) can be obtained as a success rate, and multiple times of obtaining multiple success rates of the target caller in the old system in a long period of time (which may be 24 hours) can be obtained. And obtaining a mean value X of the power, and obtaining a standard deviation S of the power, wherein a confidence interval is [ X-3 xS, X+3 xS ]. And monitoring the success rate of the new call relationship (in the new system) in real time, and when the power is outside the confidence interval and continuously exceeds a preset time period, the new call relationship is an abnormal new call relationship, wherein the preset time period can be set according to the actual working requirement.
In this way, when the power is outside the confidence interval for a long time, the target interface can be automatically switched back without manual intervention, and the degree of automation is high.
In addition, if the calling party in the abnormal new calling relation is a test point batch, only the interface corresponding to the test point batch is needed to be cut back; if the calling party in the abnormal new calling relation is the first batch, the test point batch and the interfaces corresponding to the first batch are required to be switched back, and the second batch to the Nth batch are the same, so that the repeated description is omitted. Because the problems which do not occur in the trial batch occur in the first batch or the nth batch, the method can prevent the problems from expanding as much as possible and ensure the stable and normal operation of the new system.
Referring to fig. 3, in this embodiment, the determining and cutting back the interface corresponding to the abnormal new call relationship according to the success rate of the new call relationship further includes:
s203: and determining the number of abnormal new call relations corresponding to the same interface in a set time period.
S204: and judging whether the number is larger than a set number.
S205: and if the number is larger than the set number, determining all new call relations corresponding to the interfaces as abnormal new call relations.
Specifically, the set time period and the set number can be determined according to the actual condition of the system, the set time period can be one day (24 hours), if a large number of abnormal new call relations (exceeding the set number) correspond to the same interface in one day, the interface is proved to have a possible fault, all the new call relations corresponding to the interface need to be determined as the abnormal new call relations, and all call relations are switched back. If the calling party in the abnormal new calling relation is a test point batch, only the interface corresponding to the test point batch is needed to be cut back; if the calling party in the abnormal new calling relation is the first batch, the test point batch and the interfaces corresponding to the first batch are required to be switched back, and the second batch to the Nth batch are the same, so that the repeated description is omitted. The interface itself may have problems, so that the interface problems can be prevented from being enlarged, the radiation range of the problems is reduced, and the new system can be stably operated.
In this embodiment, the basic state corresponding to the target interface in the new call relationship includes: network state, fault domain state, CPU state, memory state and server heartbeat detection state.
Referring to fig. 4, further, determining and cutting back an interface corresponding to an abnormal new call relationship according to the basic state corresponding to the target interface in the new call relationship includes:
s301: and determining a state flag bit of each state corresponding to the target interface in the new call relation according to the network state, the fault domain state, the CPU state, the memory state and the server heartbeat detection state corresponding to the target interface in the new call relation.
S302: and judging whether an abnormal mark exists in all the state mark bits corresponding to the target interfaces in the new call relation.
S303: if the abnormal mark exists, the new call relation is determined to be an abnormal new call relation, and the interface corresponding to the abnormal new call relation is cut back.
Further, determining a status flag bit of each status corresponding to the target interface in the new call relationship according to the network status, the fault domain status, the CPU status, the memory status and the server heartbeat detection status corresponding to the target interface in the new call relationship includes:
judging whether an abnormal state exists in the states according to a network state, a fault domain state, a CPU state, a memory state and a server heartbeat detection state corresponding to the target interface in the new call relation, wherein the abnormal state continuously exceeds a calibration time period;
if an abnormal state exists in the states and the abnormality continues to exceed a calibrated time period, determining a state flag bit corresponding to the state as an abnormal flag;
otherwise, defaulting the state flag bit corresponding to the state to be a normal flag.
Specifically, the network state of the area where the server in the new system to which the target interface belongs, the fault domain state where the new system container belongs, the server CPU state in the new system, the server memory state in the new system and the server heartbeat detection state in the new system are monitored in real time. The calibration time period can be set according to the specific condition of the system, and the state flag bits of the states are defaults to normal flags to indicate that the states are normal.
And when the network fails, such as a network break and the like, and the condition continuously exceeds a calibrated time period, setting a state flag bit corresponding to the network state as an abnormal flag. When the fault domain is abnormal, such as a hard disk storage fault and the like, and the condition continuously exceeds a calibrated time period, the flag bit corresponding to the fault domain state is set as an abnormal flag. When the CPU occupancy exceeds a first extremum (which may be set to 90% according to the system situation) and continues to exceed the calibrated period, the flag bit corresponding to the CPU state is set to an abnormal flag. And when the memory occupancy rate exceeds a second level (which can be set to 90% according to the system condition) and continuously exceeds a calibrated time period, setting a flag bit corresponding to the memory state as an abnormal flag. And when the heartbeat of the server detects disconnection and continuously exceeds a calibrated time period, setting the flag bit corresponding to the state of the server as an abnormal flag.
Referring to fig. 5, further, according to the basic state corresponding to the target interface in the new call relationship, determining and cutting back the interface corresponding to the abnormal new call relationship, further includes:
s304: and determining all new call relations which are the same as the interface called by the abnormal new call relation as abnormal new call relations.
Specifically, as long as one abnormal flag exists in all the status flag bits corresponding to the target interface, the new call relationship is determined to be an abnormal new call relationship, and the interface corresponding to the abnormal new call relationship is switched back. And determining all calling relations for calling the interface as abnormal new calling relations, and then cutting back all the interfaces. If the calling party in the abnormal new calling relation is a test point batch, only the interface corresponding to the test point batch is needed to be cut back; if the calling party in the abnormal new calling relation is the first batch, the test point batch and the interfaces corresponding to the first batch are required to be switched back, and the second batch to the Nth batch are the same, so that the repeated description is omitted.
Based on the above-mentioned method for switching between the new system and the old system, the embodiment of the present disclosure further provides a device for switching between the new system and the old system. The described devices may include systems (including distributed systems), software (applications), modules, components, servers, clients, etc. that employ the methods described in embodiments herein in combination with the necessary devices to implement the hardware. Based on the same innovative concepts, the embodiments herein provide for devices in one or more embodiments as described in the following examples. Since the implementation of the device for solving the problem is similar to the method, the implementation of the device in the embodiment herein may refer to the implementation of the foregoing method, and the repetition is not repeated. As used below, the term "unit" or "module" may be a combination of software and/or hardware that implements the intended function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
Specifically, fig. 6 is a schematic block diagram of an embodiment of an apparatus for switching between a new system and an old system according to the embodiment of the present disclosure, and referring to fig. 6, the apparatus for switching between a new system and an old system according to the embodiment of the present disclosure includes: a tangential flow module 100, a success rate monitoring module 200, a basic state monitoring module 300 and a back-tangential module 400.
The tangential flow module 100: cutting the target interface of the target calling party according to the to-be-cut flow table to obtain a new call relation after cutting the flow;
success rate monitoring module 200: monitoring the success rate of a target calling party to call a target interface in the new calling relation in real time;
basic state monitoring module 300: monitoring a basic state corresponding to a target interface in the new call relation in real time;
the back-cut module 400: and determining and cutting back the interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation.
In one embodiment herein, and with reference to FIG. 7, a computer device 702 is also provided. The computer device 702 may include one or more processors 704, such as one or more Central Processing Units (CPUs) or Graphics Processors (GPUs), each of which may implement one or more hardware threads. The computer device 702 may also comprise any memory 706 for storing any kind of information, such as code, settings, data, etc., and in a particular embodiment, a computer program on the memory 706 and executable on the processor 704, which computer program, when executed by the processor 704, may execute instructions according to the methods described above. For example, and without limitation, the memory 706 may include any one or more of the following combinations: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may store information using any technique. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 702. In one case, the computer device 702 can perform any of the operations of the associated instructions when the processor 704 executes the associated instructions stored in any memory or combination of memories. The computer device 702 also includes one or more drive mechanisms 708, such as a hard disk drive mechanism, an optical disk drive mechanism, and the like, for interacting with any memory.
The computer device 702 may also include an input/output module 710 (I/O) for receiving various inputs (via an input device 712) and for providing various outputs (via an output device 714). One particular output mechanism may include a presentation device 716 and an associated graphical user interface 718 (GUI). In other embodiments, input/output module 710 (I/O), input device 712, and output device 714 may not be included as just one computer device in a network. The computer device 702 can also include one or more network interfaces 720 for exchanging data with other devices via one or more communication links 722. One or more communication buses 724 couple the above-described components together.
Communication link 722 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the internet), a point-to-point connection, etc., or any combination thereof. Communication link 722 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.
Corresponding to the method in fig. 1-5, embodiments herein also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above method.
Embodiments herein also provide a computer readable instruction wherein the program therein causes the processor to perform the method as shown in fig. 1 to 5 when the processor executes the instruction.
It should be understood that, in the various embodiments herein, the sequence number of each process described above does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments herein.
It should also be understood that in embodiments herein, the term "and/or" is merely one relationship that describes an associated object, meaning that three relationships may exist. For example, a and/or B may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices, or elements, or may be an electrical, mechanical, or other form of connection.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the elements may be selected according to actual needs to achieve the objectives of the embodiments herein.
In addition, each functional unit in the embodiments herein may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions herein are essentially or portions contributing to the prior art, or all or portions of the technical solutions may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments herein. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Specific examples are set forth herein to illustrate the principles and embodiments herein and are merely illustrative of the methods herein and their core ideas; also, as will be apparent to those of ordinary skill in the art in light of the teachings herein, many variations are possible in the specific embodiments and in the scope of use, and nothing in this specification should be construed as a limitation on the invention.
Claims (9)
1. A method for switching between a new system and an old system, the method comprising:
cutting the target interface of the target calling party according to the to-be-cut flow table to obtain a new call relation after cutting the flow;
monitoring the success rate of a target calling party to call a target interface in the new calling relation in real time;
monitoring a basic state corresponding to a target interface in the new call relation in real time;
determining and cutting back an interface corresponding to an abnormal new call relation according to the success rate of the new call relation or a basic state corresponding to a target interface in the new call relation;
the determining and cutting back the interface corresponding to the abnormal new call relation according to the success rate of the new call relation comprises the following steps:
judging whether the success rate of the new call relationship is outside a confidence interval of the new call relationship and continuously exceeds a preset time period;
if the success rate of the new call relationship is outside the confidence interval of the new call relationship and continuously exceeds a preset time period, determining the new call relationship as an abnormal new call relationship, and cutting back an interface corresponding to the abnormal new call relationship;
the method for determining the confidence interval of the new call relationship comprises the following steps:
the probability of success of calling the target calling party in the old system in a period of time is acquired for a plurality of times, and a plurality of success rates of the target calling party in the old system in a period of time are obtained;
and obtaining the average value X of the success rates and the standard deviation S of the success rates, and obtaining the confidence interval of [ X-3 xS, X+3 xS ].
2. The method for switching between a new system and an old system according to claim 1, wherein determining and switching back an interface corresponding to an abnormal new call relationship according to a success rate of the new call relationship, further comprises:
determining the number of abnormal new call relations corresponding to the same interface in a set time period;
judging whether the number is larger than a set number;
and if the number is larger than the set number, determining all new call relations corresponding to the interfaces as abnormal new call relations.
3. The method for switching between a new system and an old system according to claim 1, wherein the basic state corresponding to the target interface in the new call relationship includes: network state, fault domain state, CPU state, memory state and server heartbeat detection state.
4. The method for switching between a new system and an old system according to claim 3, wherein determining and switching back the interface corresponding to the abnormal new call relationship according to the basic state corresponding to the target interface in the new call relationship comprises:
determining a state flag bit of each state corresponding to the target interface in the new call relation according to the network state, the fault domain state, the CPU state, the memory state and the server heartbeat detection state corresponding to the target interface in the new call relation;
judging whether an abnormal mark exists in all the state mark bits corresponding to the target interfaces in the new call relation;
if the abnormal mark exists, the new call relation is determined to be an abnormal new call relation, and the interface corresponding to the abnormal new call relation is cut back.
5. The method for switching between a new system and an old system according to claim 4, wherein determining the status flag bit of each status corresponding to the target interface in the new call relationship according to the network status, the fault domain status, the CPU status, the memory status and the server heartbeat detection status corresponding to the target interface in the new call relationship comprises:
judging whether an abnormal state exists in the states according to a network state, a fault domain state, a CPU state, a memory state and a server heartbeat detection state corresponding to the target interface in the new call relation, wherein the abnormal state continuously exceeds a calibration time period;
if an abnormal state exists in the states and the abnormality continues to exceed a calibrated time period, determining a state flag bit corresponding to the state as an abnormal flag;
otherwise, defaulting the state flag bit corresponding to the state to be a normal flag.
6. The method for switching between a new system and an old system according to claim 3, wherein determining and switching back the interface corresponding to the abnormal new call relationship according to the basic state corresponding to the target interface in the new call relationship, further comprises:
and determining all new call relations which are the same as the interface called by the abnormal new call relation as abnormal new call relations.
7. An apparatus for switching between a new system and an old system, the apparatus comprising:
and a tangential flow module: cutting the target interface of the target calling party according to the to-be-cut flow table to obtain a new call relation after cutting the flow;
the success rate monitoring module: monitoring the success rate of a target calling party to call a target interface in the new calling relation in real time;
the basic state monitoring module: monitoring a basic state corresponding to a target interface in the new call relation in real time;
and (3) a back cutting module: determining and cutting back an interface corresponding to an abnormal new call relation according to the success rate of the new call relation or a basic state corresponding to a target interface in the new call relation;
the determining and cutting back the interface corresponding to the abnormal new call relation according to the success rate of the new call relation comprises the following steps:
judging whether the success rate of the new call relationship is outside a confidence interval of the new call relationship and continuously exceeds a preset time period;
if the success rate of the new call relationship is outside the confidence interval of the new call relationship and continuously exceeds a preset time period, determining the new call relationship as an abnormal new call relationship, and cutting back an interface corresponding to the abnormal new call relationship;
the method for determining the confidence interval of the new call relationship comprises the following steps:
the probability of success of calling the target calling party in the old system in a period of time is acquired for a plurality of times, and a plurality of success rates of the target calling party in the old system in a period of time are obtained;
and obtaining the average value X of the success rates and the standard deviation S of the success rates, and obtaining the confidence interval of [ X-3 xS, X+3 xS ].
8. A computer device comprising a memory, a processor, and a computer program stored on the memory, characterized in that the computer program, when being executed by the processor, performs the instructions of the method according to any of claims 1-6.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor of a computer device, executes instructions of the method according to any one of claims 1-6.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110342609.7A CN112860271B (en) | 2021-03-30 | 2021-03-30 | New and old system switching method, device, equipment and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110342609.7A CN112860271B (en) | 2021-03-30 | 2021-03-30 | New and old system switching method, device, equipment and storage medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CN112860271A CN112860271A (en) | 2021-05-28 |
CN112860271B true CN112860271B (en) | 2024-03-29 |
Family
ID=75993249
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110342609.7A Active CN112860271B (en) | 2021-03-30 | 2021-03-30 | New and old system switching method, device, equipment and storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN112860271B (en) |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109600384A (en) * | 2018-12-28 | 2019-04-09 | 江苏满运软件科技有限公司 | Flow switching method, system, equipment and storage medium in RPC interface upgrade |
CN109710447A (en) * | 2019-01-08 | 2019-05-03 | 网易无尾熊(杭州)科技有限公司 | For the method, apparatus of data access, medium and calculate equipment |
CN110298650A (en) * | 2019-05-21 | 2019-10-01 | 深圳壹账通智能科技有限公司 | Interface calls charging method, device, equipment and storage medium |
CN110737575A (en) * | 2018-07-20 | 2020-01-31 | 北京金山云网络技术有限公司 | interface testing method, device, electronic equipment and storage medium |
CN111343294A (en) * | 2020-02-14 | 2020-06-26 | 京东数字科技控股有限公司 | Network environment switching method, device, equipment and computer readable storage medium |
CN111679968A (en) * | 2020-04-28 | 2020-09-18 | 平安普惠企业管理有限公司 | Interface calling abnormity detection method and device, computer equipment and storage medium |
CN112346794A (en) * | 2020-10-21 | 2021-02-09 | 深圳鼎盛电脑科技有限公司 | Interface calling method, device, equipment and medium |
-
2021
- 2021-03-30 CN CN202110342609.7A patent/CN112860271B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110737575A (en) * | 2018-07-20 | 2020-01-31 | 北京金山云网络技术有限公司 | interface testing method, device, electronic equipment and storage medium |
CN109600384A (en) * | 2018-12-28 | 2019-04-09 | 江苏满运软件科技有限公司 | Flow switching method, system, equipment and storage medium in RPC interface upgrade |
CN109710447A (en) * | 2019-01-08 | 2019-05-03 | 网易无尾熊(杭州)科技有限公司 | For the method, apparatus of data access, medium and calculate equipment |
CN110298650A (en) * | 2019-05-21 | 2019-10-01 | 深圳壹账通智能科技有限公司 | Interface calls charging method, device, equipment and storage medium |
CN111343294A (en) * | 2020-02-14 | 2020-06-26 | 京东数字科技控股有限公司 | Network environment switching method, device, equipment and computer readable storage medium |
CN111679968A (en) * | 2020-04-28 | 2020-09-18 | 平安普惠企业管理有限公司 | Interface calling abnormity detection method and device, computer equipment and storage medium |
CN112346794A (en) * | 2020-10-21 | 2021-02-09 | 深圳鼎盛电脑科技有限公司 | Interface calling method, device, equipment and medium |
Also Published As
Publication number | Publication date |
---|---|
CN112860271A (en) | 2021-05-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2301197B1 (en) | Message management and suppression in a monitoring system | |
CN110175465A (en) | Log desensitization method, device, computer equipment and computer readable storage medium | |
CN112672357B (en) | Method and device for processing user account in service system and computer equipment | |
CN104967537A (en) | Alarm information pushing method and device | |
CN112346931A (en) | Raspberry pie-based private network service cluster monitoring alarm system, method and medium | |
CN112286770A (en) | Alarm notification method, device, computer equipment and storage medium | |
CN111246406A (en) | Short message sending method, system, storage medium and terminal equipment | |
CN114708717A (en) | Association alarm method and device for system monitoring | |
CN112860271B (en) | New and old system switching method, device, equipment and storage medium | |
CN113852637A (en) | Weak password detection method and device and electronic equipment | |
CN111062503B (en) | Power grid monitoring alarm processing method, system, terminal and storage medium | |
CN109600250B (en) | Service system fault notification method, device, electronic device and storage medium | |
CN115242621B (en) | Network private line monitoring method, device, equipment and computer readable storage medium | |
CN111367934A (en) | Data consistency checking method, device, server and medium | |
CN111159009A (en) | Pressure testing method and device for log service system | |
CN112187937B (en) | Unpairing method and device, terminal equipment and storage medium | |
CN111385167B (en) | Network connection recovery method, device, computer device and storage medium | |
CN114661507A (en) | Data processing method and device based on time-associated data and electronic equipment | |
CN109614246B (en) | Message processing method and device and message processing server | |
CN112069027A (en) | Interface data processing method and device, electronic equipment and storage medium | |
CN111953569A (en) | State information reporting method, device, equipment and medium | |
CN107783852B (en) | Dump file generation method and terminal | |
CN111049877A (en) | Big data external output method and device and data open platform | |
CN117251769B (en) | Abnormal data identification method, device, equipment and medium based on monitoring component | |
CN115118673B (en) | Service traffic migration method, device, equipment and computer readable storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |