CN112235138B - Server access monitoring method and device, proxy server and storage medium - Google Patents
Server access monitoring method and device, proxy server and storage medium Download PDFInfo
- Publication number
- CN112235138B CN112235138B CN202011085039.XA CN202011085039A CN112235138B CN 112235138 B CN112235138 B CN 112235138B CN 202011085039 A CN202011085039 A CN 202011085039A CN 112235138 B CN112235138 B CN 112235138B
- Authority
- CN
- China
- Prior art keywords
- internet protocol
- access
- protocol address
- access result
- slave
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The application provides a server access monitoring method and device, a proxy server and a storage medium, and relates to the technical field of Internet. In the present application, first, a first access result for accessing a target server based on a main internet protocol address is obtained. And secondly, if the first access result is access failure, accessing the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result. Then, a failure type of the first access result is determined based on the at least one second access result, wherein the failure type includes a primary internet protocol address error. Based on the method, the problem that the failure type is difficult to effectively determine when the access to the server fails in the prior art can be solved.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method and apparatus for monitoring server access, a proxy server, and a storage medium.
Background
In the field of internet technology, in order to increase the response speed of a user to access a website (background server), a content delivery network (CDN, content Delivery Network) may be used for proxy. In the prior art, a proxy node on a content distribution network generally directly attributes the cause of access failure to an internet protocol (IP, internet Protocol) address error when accessing a background server to acquire data. The inventor researches find that there are other reasons or types for the access failure of the background server, so that the problem that the failure type of the access failure of the server is difficult to effectively determine exists.
Disclosure of Invention
In view of the foregoing, an object of the present application is to provide a method and apparatus for monitoring access to a server, a proxy server, and a storage medium, so as to solve the problem that it is difficult to effectively determine the failure type when access to the server fails in the prior art.
In order to achieve the above purpose, the embodiment of the present application adopts the following technical scheme:
a server access monitoring method applied to a proxy server configured with a master internet protocol address and a slave internet protocol address, the method comprising:
obtaining a first access result of accessing a target server based on the main internet protocol address;
if the first access result is access failure, accessing the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result;
determining a failure type of the first access result based on the at least one second access result, wherein the failure type includes a primary internet protocol address error.
In a preferred option of the embodiment of the present application, in the method for monitoring server access, the step of accessing the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result includes:
for each of the at least one pre-configured slave internet protocol address, accessing the target server at least once based on the slave internet protocol address to obtain at least one initial access result corresponding to the slave internet protocol address;
determining a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address for each of the slave internet protocol addresses;
and taking the target access result of each slave internet protocol address as a second access result of the slave internet protocol address respectively to obtain at least one second access result.
In a preferred option of the embodiment of the present application, in the above server access monitoring method, the step of determining, for each of the slave internet protocol addresses, a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address includes:
for each of the slave internet protocol addresses, if at least one initial access result corresponding to the slave internet protocol address is an access failure, determining that a target access result of the slave internet protocol address is an access failure;
and for each slave internet protocol address, if one initial access result exists in at least one initial access result corresponding to the slave internet protocol address, determining that the target access result of the slave internet protocol address is access success.
In a preferred option of the embodiment of the present application, in the method for monitoring server access, the step of accessing the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result further includes:
accessing the target server at least once based on the main Internet protocol address to obtain at least one initial access result corresponding to the main Internet protocol address;
determining a target access result of the main internet protocol address based on at least one initial access result corresponding to the main internet protocol address;
and taking the target access result of the main Internet protocol address as a second access result of the main Internet protocol address to obtain at least one second access result.
In a preferred option of an embodiment of the present application, in the above server access monitoring method, the at least one second access result includes a second access result of revisiting the target server based on the primary internet protocol address, and the step of determining a failure type of the first access result based on the at least one second access result includes:
if the second access result of revisiting the target server based on the main internet protocol address is access failure and the second access result of revising the target server based on each of the auxiliary internet protocol addresses is access success, determining a main internet protocol address error;
and if the second access result of revisiting the target server based on the main internet protocol address is access failure and the second access result of revisiting the target server based on each of the auxiliary internet protocol addresses is access failure, determining that the machine room where the proxy server is located is failed or the target server is failed.
In a preferred option of the embodiment of the present application, in the method for monitoring server access, the step of determining the failure type of the first access result based on the at least one second access result further includes:
and if the access result of revisiting the target server based on the main internet protocol address is successful access, and the access result of revising the target server based on each auxiliary internet protocol address is successful access, determining that the main internet protocol address has no error, the machine room where the proxy server is located has no fault, and the target server has no overload and fault.
In a preferred option of the embodiment of the present application, in the method for monitoring server access, the step of determining the failure type of the first access result based on the at least one second access result further includes:
if the second access result of revisiting the target server based on the main internet protocol address is access failure and the second access result of revising the target server based on a plurality of the auxiliary internet protocol addresses is partial access failure, determining that the target server is overloaded;
and if the second access result of revisiting the target server based on the main internet protocol address is successful access, and the second access result of revisiting the target server based on a plurality of the slave internet protocol addresses is at least partial access failure, determining that the target server is overloaded.
The embodiment of the application also provides a server access monitoring device, which is applied to a proxy server, wherein the proxy server is configured with a master internet protocol address and a slave internet protocol address, and the device comprises:
a first access result obtaining module, configured to obtain a first access result of accessing a target server based on the main internet protocol address;
the second access result obtaining module is used for accessing the target server at least based on one slave internet protocol address when the first access result is access failure, so as to obtain at least one corresponding second access result;
an access failure type determination module for determining a failure type of the first access result based on the at least one second access result, the failure type comprising a primary internet protocol address error.
On the basis of the above, the embodiment of the application further provides a proxy server, which comprises:
a memory for storing a computer program;
and the processor is connected with the memory and is used for executing the computer program stored in the memory so as to realize the server access monitoring method.
On the basis of the above, the embodiment of the application also provides a computer readable storage medium, which stores a computer program, and when the computer program is executed, the server access monitoring method is realized.
The server access monitoring method and device, the proxy server and the storage medium provided by the application enable the target server to be accessed based on the slave internet protocol address when the access to the target server based on the master internet protocol address fails by configuring the master internet protocol address and the slave internet protocol address on the proxy server, so that the type (reason) of the access failure is determined based on the result of the access. Therefore, compared with the technical scheme that the reasons are assigned to the Internet protocol address errors directly when the access fails, the method and the device can determine the reasons of the access failure more effectively, solve the problem that the failure type is difficult to determine effectively when the access to the server fails in the prior art, enable the maintenance and the like to be performed in a targeted manner based on the determined reasons of the failure, and have higher practical value.
In order to make the above objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
Fig. 1 is a block diagram of a proxy server according to an embodiment of the present application.
Fig. 2 is a flow chart of a server access monitoring method according to an embodiment of the present application.
Fig. 3 is a flow chart illustrating the sub-steps included in step S120 in fig. 2.
Fig. 4 is a flow chart illustrating the sub-steps included in step S122 in fig. 3.
Fig. 5 is a flow chart illustrating other sub-steps included in step S120 in fig. 2.
Fig. 6 is a block diagram of a server access monitoring device according to an embodiment of the present application.
Icon: 10-a proxy server; 12-memory; 14-a processor; 100-server access monitoring device; 110-a first access result obtaining module; 120-a second access result obtaining module; 130-an access failure type determination module.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, which are generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, as provided in the accompanying drawings, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
As shown in fig. 1, an embodiment of the present application provides a proxy server 10 that may include a memory 12, a processor 14, and a server access monitoring device 100.
Wherein, the memory 12 and the processor 14 are directly or indirectly electrically connected to each other to realize data transmission or interaction. For example, electrical connection may be made to each other via one or more communication buses or signal lines. The server access monitoring device 100 comprises at least one software functional module which may be stored in the memory 12 in the form of software or firmware (firmware). The processor 14 is configured to execute an executable computer program stored in the memory 12, for example, a software function module and a computer program included in the server access monitoring apparatus 100, so as to implement a server access monitoring method provided in the embodiments of the present application.
Alternatively, the Memory 12 may be, but is not limited to, random access Memory (Random Access Memory, RAM), read Only Memory (ROM), programmable Read Only Memory (Programmable Read-Only Memory, PROM), erasable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.
Also, the processor 14 may be a general-purpose processor including a central processing unit (Central Processing Unit, CPU), a graphics processor (Graphics Processing Unit, GPU), and the like.
It will be appreciated that the architecture shown in fig. 1 is illustrative only, and that the proxy server 10 may also include more or fewer components than shown in fig. 1, or have a different configuration than shown in fig. 1, for example, may also include a communication unit for interacting with other devices (e.g., a target server).
With reference to fig. 2, the embodiment of the present application further provides a server access monitoring method, which can be applied to the proxy server 10. Wherein. The method steps defined by the flow related to the server access monitoring method may be implemented by the proxy server 10.
The specific flow shown in fig. 2 will be described in detail.
Step S110, obtaining a first access result of accessing the target server based on the main internet protocol address.
In this embodiment, the proxy server 10 is preconfigured with a main internet protocol address, and may access the target server (e.g., based on a request of a terminal device connected by communication) based on the main internet protocol address, so that a first access result of the access may be obtained.
And, when the first access result is an access failure, step S120 may be performed.
And step S120, accessing the target server based on at least one slave Internet protocol address to obtain at least one corresponding second access result.
In this embodiment, the proxy server 10 is further configured with a slave internet protocol address in advance, so that when the first access result is obtained based on step S110, and when the first access result is that the access fails, the proxy server 10 may access the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result.
Step S130, determining, based on the at least one second access result, a failure type of the first access result.
In this embodiment, after the at least one second access result is obtained based on step S120, the proxy server 10 may determine the foregoing failure type of access failure (i.e., the failure type of the first access result) when accessing the target server based on the primary internet protocol address based on the at least one second access result.
Wherein the failure type (failure cause) may include a primary internet protocol address error.
Based on the above method, by configuring the master internet protocol address and the slave internet protocol address on the proxy server 10, it is made possible to access the target server based on the slave internet protocol address when accessing the target server based on the master internet protocol address fails, thereby determining the type (cause) of access failure based on the result of the access. Therefore, compared with the technical scheme that the reasons are assigned to the Internet protocol address errors directly when the access fails, the method and the device can determine the reasons of the access failure more effectively, solve the problem that the failure type is difficult to determine effectively when the access to the server fails in the prior art, and enable the maintenance to be conducted in a targeted mode based on the determined reasons of the failure.
In the first aspect, it should be noted that, in step S110, a specific manner of obtaining the access result is not limited, and may be selected according to actual application requirements.
For example, in an alternative example, after each access to the target server by the proxy server 10 based on the main internet protocol address, the obtained first access result may be stored in a target database (e.g., a local database), so that the first access result may be obtained by performing a data reading operation on the target database.
It will be appreciated that, considering that there may be duplicate results in the first access result obtained by making the access, in some examples, the obtained first access result may also be subjected to a filtering process to filter the duplicate first access result, so as to avoid the problem of overloading the target database.
In the second aspect, it should be noted that, in step S120, a specific manner of obtaining the at least one second access result is not limited, and may be selected according to actual application requirements.
For example, in an alternative example, in conjunction with fig. 3, step S120 may include step S121, step S122, and step S123, as described in detail below.
Step S121, for each of the at least one pre-configured slave internet protocol address, performing at least one access to the target server based on the slave internet protocol address, to obtain at least one initial access result corresponding to the slave internet protocol address.
In this embodiment, when the first access result is obtained based on step S110, and when the first access result is an access failure, at least one initial access result corresponding to each of the at least one pre-configured slave internet protocol address may be obtained by accessing the target server at least once based on the slave internet protocol address. In this way, at least one initial access result corresponding to each of the secondary internet protocol addresses may be obtained.
Step S122, for each of the slave internet protocol addresses, determining a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address.
In this embodiment, after the initial access result is obtained based on step S122, the target access result of the slave internet protocol address may also be determined for each of the slave internet protocol addresses based on at least one initial access result corresponding to the slave internet protocol address. Thus, each target access result corresponding to the slave internet protocol address can be obtained.
Step S123, taking each target access result of the slave internet protocol address as a second access result of the slave internet protocol address, to obtain at least one second access result.
In this embodiment, after the target access result is obtained based on step S122, the target access result corresponding to each of the slave internet protocol addresses may be respectively used as the second access result of the slave internet protocol address. In this way, at least one second access result may be obtained for at least one of the slave internet protocol addresses.
Alternatively, in the above example, the specific manner of obtaining the at least one initial access result based on step S121 is not limited, and may be selected according to actual application requirements.
For example, in an alternative example, for each of the slave internet protocol addresses, the target server may be accessed once based on the slave internet protocol address, to obtain an initial access result corresponding to the slave internet protocol address.
For another alternative example, for each of the secondary internet protocol addresses, the target server may be accessed multiple times (e.g., 3 times, etc.) based on the secondary internet protocol address, to obtain multiple initial access results corresponding to the secondary internet protocol address.
Alternatively, in the above example, the specific manner of determining the target access result based on step S122 is not limited, and may be selected according to actual application requirements.
For example, in an alternative example, if the initial access result corresponding to each slave internet protocol address is one, the initial access result may be taken as the target access result.
For another example, in another alternative example, in conjunction with fig. 4, step S122 may include step S122a and step S122b, as described in detail below.
In step S122a, for each of the secondary internet protocol addresses, if at least one initial access result corresponding to the secondary internet protocol address is an access failure, the target access result of the secondary internet protocol address is determined to be an access failure.
In this embodiment, after obtaining at least one initial access result corresponding to each of the slave internet protocol addresses based on step S121, it may be determined whether each initial access result is an access failure, and thus, if each initial access result corresponding to one of the slave internet protocol addresses is an access failure, it may be determined that the target access result of the slave internet protocol address is an access failure.
Step S122b, for each of the secondary internet protocol addresses, if there is an initial access result in at least one initial access result corresponding to the secondary internet protocol address that is an access success, determining that the target access result of the secondary internet protocol address is an access success.
In this embodiment, after obtaining at least one initial access result corresponding to each of the secondary internet protocol addresses based on step S121, it may be determined whether one initial access result exists in the at least one initial access result corresponding to each of the secondary internet protocol addresses as an access success, and thus, if one initial access result exists in the at least one initial access result corresponding to each of the secondary internet protocol addresses as an access success, it may be determined that the target access result of each of the secondary internet protocol addresses is an access success.
On the basis of the above example, it should also be noted that, for the step S120, the step S120 may further include other steps. For example, in an alternative example, the target server may be accessed again based on the main internet protocol address, and based on this, step S120 may further include step S124, step S125, and step S126, which are described below.
And step S124, accessing the target server at least once based on the main Internet protocol address to obtain at least one initial access result corresponding to the main Internet protocol address.
In this embodiment, when the first access result is obtained based on step S110, and the first access result is an access failure, at least one access may be performed on the target server again based on the main internet protocol address, so as to obtain at least one initial access result corresponding to the main internet protocol address, that is, one initial access result may be obtained for each access.
Step S125, determining a target access result of the main internet protocol address based on at least one initial access result corresponding to the main internet protocol address.
In this embodiment, after obtaining at least one initial access result corresponding to the primary internet protocol address based on step S124, a target access result of the primary internet protocol address may be determined based on the at least one initial access result. For example, in one alternative example:
if at least one initial access result corresponding to the main internet protocol address is access failure, determining that a target access result of the main internet protocol address is access failure; and if one initial access result exists in at least one initial access result corresponding to the main internet protocol address, determining that the target access result of the main internet protocol address is the access success.
And step S126, taking the target access result of the main Internet protocol address as a second access result of the main Internet protocol address to obtain at least one second access result.
In this embodiment, after determining the target access result of the primary internet protocol address based on step S125, the target access result may be used as the second access result of the primary internet protocol address, thereby obtaining a second access result.
In a third aspect, it should be noted that, in step S130, a specific manner of determining the failure type of the first access result is not limited, and for example, there may be different choices based on whether the at least one second access result obtained includes a second access result for revisiting the target server based on the primary internet protocol address.
Based on this, in an alternative example, the at least one second access result comprises a second access result of revisiting the target server based on the primary internet protocol address, and thus, step S130 may comprise the sub-steps of:
if the second access result of revising the target server based on the master internet protocol address is access failure and the second access result of accessing the target server based on each of the slave internet protocol addresses is access success, determining a master internet protocol address error (determining that the master internet protocol address is wrong because only the second access result of the master internet protocol address is access failure, indicating that the master internet protocol address has a problem, such as being blocked, etc.);
if the second access result of revisiting the target server based on the master internet protocol address is an access failure, and the second access result of revisiting the target server based on each slave internet protocol address is an access failure, determining that the machine room where the proxy server 10 is located or the target server is faulty (the second access result of the master internet protocol address and the slave internet protocol address are both access failures, because all internet protocol address errors are less likely, it may be determined that the failure type is a machine room fault or a target server fault where the proxy server 10 is located, and a specific type may send notification information to a management server of the content distribution network where the proxy server 10 is located through the proxy server 10, so that the management server accesses the target server through proxy servers 10 of different machine rooms, thereby determining whether the machine room where the proxy server 10 is located is faulty or the target server is faulty).
In the above example, the second access result of revisiting the target server based on the main internet protocol address is access failure, so when the second access result is that the access is successful, the specific failure type determining rule is not limited, and the selection can be performed according to the actual application requirement.
For example, in an alternative example, step S130 may include the sub-steps of:
if the access result of revisiting the target server based on the master internet protocol address is that the access is successful, and the access result of revisiting the target server based on each slave internet protocol address is that the access is successful, determining that the master internet protocol address is error-free, the machine room where the proxy server 10 is located is error-free, the target server is overload-free and has a fault (i.e. the first access result may be counted by mistake, or the fault error has been recovered).
Also, in some examples, in order to obtain more accurate results, the second access result obtained based on the accessing the target server from the internet protocol address may be plural, so step S130 may include the following sub-steps:
if the second access result of revisiting the target server based on the master internet protocol address is an access failure and the second access result of revisiting the target server based on a plurality of slave internet protocol addresses is a partial access failure, determining that the target server is overloaded (because not all the second access results are access failures, indicating that there is less possibility of an error in the internet protocol address, the failure type may be determined as the target server overload);
if the second access result of revisiting the target server based on the master internet protocol address is successful access, and the second access result of revisiting the target server based on a plurality of the slave internet protocol addresses is at least partial access failure, determining that the target server is overloaded (because not all the second access results are access failures, indicating that there is less possibility of an error in the internet protocol address, the failure type may be determined to be the target server overload).
It will be appreciated that in the above example, the specific relationship between the master internet protocol address and the slave internet protocol address is not limited, and may refer to the master internet protocol address and the slave internet protocol address being different internet protocol addresses, or may refer to the master internet protocol address and the slave internet protocol address being different internet protocol addresses belonging to the same network segment (e.g., in one network segment, the first internet protocol address may be the master internet protocol address, and the other internet protocol addresses may be the slave internet protocol addresses).
In connection with fig. 6, the embodiment of the present application further provides a server access monitoring apparatus 100, which is applicable to the proxy server 10. The server access monitoring apparatus 100 includes a first access result obtaining module 110, a second access result obtaining module 120, and an access failure type determining module 130.
The first access result obtaining module 110 may be configured to obtain a first access result of accessing a target server based on the primary internet protocol address. In this embodiment, the first access result obtaining module 110 may be used to perform step S110 shown in fig. 2, and the description of step S110 may be referred to as to the relevant content of the first access result obtaining module 110.
The second access result obtaining module 120 may be configured to, when the first access result is an access failure, access the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result. In this embodiment, the second access result obtaining module 120 may be used to perform step S120 shown in fig. 2, and the description of step S120 may be referred to above with respect to the relevant content of the second access result obtaining module 120.
The access failure type determining module 130 may be configured to determine a failure type of the first access result based on the at least one second access result, where the failure type includes a primary internet protocol address error. In this embodiment, the access failure type determining module 130 may be used to perform step S130 shown in fig. 2, and the description of step S130 may be referred to above with respect to the relevant content of the access failure type determining module 130.
In an embodiment of the present application, corresponding to the above-mentioned server access monitoring method, a computer readable storage medium is further provided, where a computer program is stored in the computer readable storage medium, and the computer program executes each step of the above-mentioned server access monitoring method when running.
The steps executed when the computer program runs are not described in detail herein, and the explanation of the server access monitoring method can be referred to in the foregoing.
In summary, the server access monitoring method and device, the proxy server and the storage medium provided by the application, by configuring the master internet protocol address and the slave internet protocol address on the proxy server, the target server can be accessed based on the slave internet protocol address when the access to the target server based on the master internet protocol address fails, and the type (reason) of the access failure can be determined based on the result of the access. Therefore, compared with the technical scheme that the reasons are assigned to the Internet protocol address errors directly when the access fails, the method and the device can determine the reasons of the access failure more effectively, solve the problem that the failure type is difficult to determine effectively when the access to the server fails in the prior art, enable the maintenance to be performed in a targeted manner based on the determined reasons of the failure, and have higher practical value.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus and method embodiments described above are merely illustrative, for example, flow diagrams and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, an electronic device, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. 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. It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the same, but rather, various modifications and variations may be made by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.
Claims (8)
1. A server access monitoring method, applied to a proxy server configured with a master internet protocol address and a slave internet protocol address, comprising:
obtaining a first access result of accessing a target server based on the main internet protocol address;
if the first access result is that the access fails, at least one access is performed on the target server based on the slave internet protocol address for each of a plurality of preset slave internet protocol addresses, so as to obtain at least one initial access result corresponding to the slave internet protocol address;
determining a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address for each of the slave internet protocol addresses;
taking the target access result of each slave internet protocol address as a second access result of the slave internet protocol address respectively;
accessing the target server at least once based on the main Internet protocol address to obtain at least one initial access result corresponding to the main Internet protocol address;
determining a target access result of the main internet protocol address based on at least one initial access result corresponding to the main internet protocol address;
taking the target access result of the main Internet protocol address as a second access result of the main Internet protocol address;
determining a failure type of the first access result based on the second access result of each of the secondary internet protocol addresses and the second access result of the primary internet protocol address, wherein the failure type includes a primary internet protocol address error and a target server overload;
the step of determining the failure type of the first access result based on the second access result of each of the slave internet protocol addresses and the second access result of the master internet protocol address includes:
if the second access result of accessing the target server based on the master internet protocol address is access failure and the second access result of accessing the target server based on each slave internet protocol address is access success, determining that the master internet protocol address is wrong;
and if the second access result of accessing the target server based on the main internet protocol address is access failure and the second access result of accessing the target server based on a plurality of the auxiliary internet protocol addresses is partial access failure, determining that the target server is overloaded.
2. The server access monitoring method according to claim 1, wherein the step of determining, for each of the slave internet protocol addresses, a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address, comprises:
for each of the slave internet protocol addresses, if at least one initial access result corresponding to the slave internet protocol address is an access failure, determining that a target access result of the slave internet protocol address is an access failure;
and for each slave internet protocol address, if one initial access result exists in at least one initial access result corresponding to the slave internet protocol address, determining that the target access result of the slave internet protocol address is access success.
3. The server access monitoring method according to any one of claims 1-2, wherein the step of determining the failure type of the first access result based on the second access result of each of the slave internet protocol addresses and the second access result of the master internet protocol address further comprises:
and if the second access result of accessing the target server based on the master internet protocol address is access failure and the second access result of accessing the target server based on each slave internet protocol address is access failure, determining that the machine room where the proxy server is located or the target server is in failure.
4. The server access monitoring method according to claim 3, wherein the step of determining the failure type of the first access result based on the second access result of each of the slave internet protocol addresses and the second access result of the master internet protocol address further comprises:
and if the access result of accessing the target server based on the main internet protocol address is successful and the access result of accessing the target server based on each of the auxiliary internet protocol addresses is successful, determining that the main internet protocol address has no error, the machine room where the proxy server is located has no fault, and the target server has no overload and fault.
5. The server access monitoring method according to claim 3, wherein the step of determining the failure type of the first access result based on the second access result of each of the slave internet protocol addresses and the second access result of the master internet protocol address further comprises:
and if the second access result of accessing the target server based on the main internet protocol address is successful access, and the second access result of accessing the target server based on a plurality of the auxiliary internet protocol addresses is at least partial access failure, determining that the target server is overloaded.
6. A server access monitoring apparatus for use with a proxy server configured with a master internet protocol address and a slave internet protocol address, the apparatus comprising:
a first access result obtaining module, configured to obtain a first access result of accessing a target server based on the main internet protocol address;
the second access result obtaining module is used for accessing the target server at least once based on the slave internet protocol address for each of a plurality of preset slave internet protocol addresses when the first access result is access failure, and obtaining at least one initial access result corresponding to the slave internet protocol address; determining a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address for each of the slave internet protocol addresses; taking the target access result of each slave internet protocol address as a second access result of the slave internet protocol address respectively; accessing the target server at least once based on the main Internet protocol address to obtain at least one initial access result corresponding to the main Internet protocol address; determining a target access result of the main internet protocol address based on at least one initial access result corresponding to the main internet protocol address; taking the target access result of the main Internet protocol address as a second access result of the main Internet protocol address;
an access failure type determining module, configured to determine a failure type of the first access result based on a second access result of each of the secondary internet protocol addresses and a second access result of the primary internet protocol address, where the failure type includes a primary internet protocol address error and a target server overload;
the access failure type determining module is specifically configured to determine a primary internet protocol address error if a second access result of accessing the target server based on the primary internet protocol address is an access failure, and if a second access result of accessing the target server based on each of the secondary internet protocol addresses is an access success; and if the second access result of accessing the target server based on the main internet protocol address is access failure and the second access result of accessing the target server based on a plurality of the auxiliary internet protocol addresses is partial access failure, determining that the target server is overloaded.
7. A proxy server, comprising:
a memory for storing a computer program;
a processor coupled to the memory for executing a computer program stored in the memory for implementing the server access monitoring method according to any one of claims 1-5.
8. A computer readable storage medium storing a computer program, characterized in that the computer program, when executed, implements the server access monitoring method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011085039.XA CN112235138B (en) | 2020-10-12 | 2020-10-12 | Server access monitoring method and device, proxy server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011085039.XA CN112235138B (en) | 2020-10-12 | 2020-10-12 | Server access monitoring method and device, proxy server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112235138A CN112235138A (en) | 2021-01-15 |
| CN112235138B true CN112235138B (en) | 2023-06-02 |
Family
ID=74112063
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011085039.XA Active CN112235138B (en) | 2020-10-12 | 2020-10-12 | Server access monitoring method and device, proxy server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112235138B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102214223A (en) * | 2011-06-15 | 2011-10-12 | 奇智软件（北京）有限公司 | Method and system for browser access control |
| CN109347766A (en) * | 2018-12-07 | 2019-02-15 | 网宿科技股份有限公司 | A kind of method and device of scheduling of resource |
| CN110224996A (en) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Network Access Method, device, computer equipment and the storage medium of application program |
| CN110995542A (en) * | 2019-12-16 | 2020-04-10 | 金蝶智慧科技(深圳)有限公司 | Network state detection method, system and related equipment |
| CN111343630A (en) * | 2020-03-07 | 2020-06-26 | 山东浪潮通软信息科技有限公司 | Network connection state detection method, computer device, and storage medium |
-
2020
- 2020-10-12 CN CN202011085039.XA patent/CN112235138B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102214223A (en) * | 2011-06-15 | 2011-10-12 | 奇智软件（北京）有限公司 | Method and system for browser access control |
| CN109347766A (en) * | 2018-12-07 | 2019-02-15 | 网宿科技股份有限公司 | A kind of method and device of scheduling of resource |
| CN110224996A (en) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Network Access Method, device, computer equipment and the storage medium of application program |
| CN110995542A (en) * | 2019-12-16 | 2020-04-10 | 金蝶智慧科技(深圳)有限公司 | Network state detection method, system and related equipment |
| CN111343630A (en) * | 2020-03-07 | 2020-06-26 | 山东浪潮通软信息科技有限公司 | Network connection state detection method, computer device, and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112235138A (en) | 2021-01-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110036600B (en) | Network health data convergence service | |
| CN110036599B (en) | Programming interface for network health information | |
| US6718376B1 (en) | Managing recovery of service components and notification of service errors and failures | |
| EP3352433A1 (en) | Node connection method and distributed computing system | |
| CN110535692B (en) | Fault processing method and device, computer equipment, storage medium and storage system | |
| US7370102B1 (en) | Managing recovery of service components and notification of service errors and failures | |
| CN110932933B (en) | Network condition monitoring method, computing device and computer storage medium | |
| CN113472607B (en) | Application program network environment detection method, device, equipment and storage medium | |
| CN107682172B (en) | Control center device, service system processing method and medium | |
| CN114172794A (en) | Network fault positioning method and server | |
| CN113141412B (en) | Domain name switching method, system, device, equipment and storage medium | |
| CN112202631A (en) | Resource access method, device and system, electronic equipment and storage medium | |
| CN112818307A (en) | User operation processing method, system, device and computer readable storage medium | |
| CN110933191B (en) | IP address obtaining method and device, upper computer and storage medium | |
| CN112235138B (en) | Server access monitoring method and device, proxy server and storage medium | |
| CN110737565A (en) | data monitoring method, device, electronic equipment and storage medium | |
| CN109324914B (en) | Service calling method, service calling device and central server | |
| CN111414247A (en) | Server switching method, device, management node and storage medium | |
| CN113596195B (en) | Public IP address management method, device, main node and storage medium | |
| CN110635958B (en) | Network fault diagnosis method, device and storage medium | |
| EP3607767A1 (en) | Network fault discovery | |
| CN114168383A (en) | Application state monitoring restart tool, method, medium and equipment | |
| CN111130941B (en) | Network error detection method and device and computer readable storage medium | |
| CN115514733A (en) | Configuration method and configuration device for domain name resolution service (DNS) | |
| CN112242027B (en) | Express delivery cabinet fault processing method and device, fault processing equipment and 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 |