CN112948733A

CN112948733A - Interface maintenance method, device, computing equipment and medium

Info

Publication number: CN112948733A
Application number: CN202110208148.4A
Authority: CN
Inventors: 丁骏; 汪高平; 包扬; 林德智; 陈光通; 王紫琦; 刘之安
Original assignee: Hangzhou Netease Cloud Music Technology Co Ltd
Current assignee: Hangzhou Netease Cloud Music Technology Co Ltd
Priority date: 2021-02-24
Filing date: 2021-02-24
Publication date: 2021-06-11
Anticipated expiration: 2041-02-24
Also published as: CN112948733B

Abstract

The embodiment of the disclosure provides an interface maintenance method, an interface maintenance device, computing equipment and a medium. The method comprises the following steps: responding to a page request of a page, and extracting a URL (uniform resource locator) of the page and interface information corresponding to the URL from the page request; determining interface level information of each interface in the interface information, wherein the interface level information is level information defined according to the function of the interface in a service scene; and determining a necessary interface set corresponding to the page based on the interface level information and the interface information. According to the technical scheme of the embodiment of the disclosure, the necessary interfaces can be maintained automatically, so that the efficiency and the accuracy of interface maintenance are improved, and the labor cost and the time cost of interface maintenance are reduced.

Description

Interface maintenance method, device, computing equipment and medium

Technical Field

Embodiments of the present disclosure relate to the field of computer technologies, and in particular, to an interface maintenance method, an interface maintenance apparatus, a computing device, and a medium.

Background

This section is intended to provide a background or context to the embodiments of the disclosure recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.

After a service system or an application system is online, in the case of a large-flow high-concurrency scene, the system may be unstable or may fail. Therefore, ensuring the stability and functional availability of the service interface of the service system is an important link in the maintenance process after the system is on-line, and the overall availability of the service interface of the service system and the availability of the basic function when a fault occurs need to be ensured.

In the related technical scheme, the code of the business system is manually combed, the requested interface under the appointed page is found, an interface document is formed, and the overall availability of the business interface of the business system and the availability of the basic function when the fault occurs are maintained according to the interface document.

Disclosure of Invention

However, in the above technical solution, the way of forming the interface document by manual combing not only requires high labor cost and time cost, but also has low efficiency and accuracy for maintaining the service interface at a later stage.

Therefore, an improved interface maintenance method is highly needed to improve the efficiency and accuracy of interface maintenance and reduce the labor cost and time cost.

In a first aspect of the embodiments of the present disclosure, there is provided an interface maintenance method, including: responding to a page request of a page, and extracting a Uniform Resource Locator (URL) of the page and interface information corresponding to the URL from the page request; determining interface level information of each interface in the interface information, wherein the interface level information is level information defined according to the function of the interface in a service scene; and determining a necessary interface set corresponding to the page based on the interface level information and the interface information.

In some example embodiments of the present disclosure, the method further comprises: generating a page base map corresponding to the necessary interface set according to the page information of the page corresponding to each interface in the necessary interface set; determining current interface information corresponding to a URL of the page in response to a current page request for the page; generating a current page map corresponding to the current interface information based on the page information of the page corresponding to each interface in the current interface information; and determining the similarity between the current page map and the page base map, and giving an alarm when the similarity between the current page map and the page base map is lower than a first preset threshold value.

In some example embodiments of the present disclosure, the method further comprises: generating a blank page image corresponding to the page size of the page; and determining the similarity between the current page map and the blank page map, and giving an alarm when the similarity between the current page map and the blank page map is higher than a second preset threshold value.

In some example embodiments of the present disclosure, the extracting the URL of the page from the page request includes: analyzing the page request to obtain at least one URL corresponding to the page; acquiring a domain name corresponding to each URL in the at least one URL, and determining whether the domain name is in a pre-configured domain name list; if the domain name list is in the domain name list, taking the corresponding URL as the URL of the page; and if the URL is not in the domain name list, filtering out the corresponding URL.

In some example embodiments of the present disclosure, the extracting, from the page request, interface information corresponding to the URL includes: extracting interface information corresponding to the URL of the page from the page request according to the extracted URL of the page; generating a message based on the URL of the page and interface information corresponding to the URL, wherein the message comprises KEY pairs, the KEY of each KEY pair is the URL, and the VALUE VALUE is an interface name in the interface information; and sending the message to a message queue.

In some example embodiments of the present disclosure, the method further comprises: if monitoring that the message queue receives a new message, acquiring a URL (uniform resource locator) of a page and corresponding interface information from the new message; and storing the URL of the page and the corresponding interface into a database.

In some example embodiments of the present disclosure, the method further comprises: verifying whether each basic service function under the service scene is normal or not based on the necessary interface set; and if the basic service functions are normal, determining that the necessary interface set is a correct necessary interface set.

In some example embodiments of the present disclosure, the method further comprises: responding to a current page request of the page, and extracting current interface information corresponding to the URL of the page from the current page request; and if the current interface information does not exist in the database, storing the current interface information.

In a second aspect of embodiments of the present disclosure, there is provided an interface maintenance apparatus, including: the request response module is used for responding to a page request of a page, and extracting a Uniform Resource Locator (URL) of the page and interface information corresponding to the URL from the page request; the level information determining module is used for determining interface level information of each interface in the interface information, wherein the interface level information is level information defined according to the function of the interface in a service scene; and the necessary interface determining module is used for determining a necessary interface set corresponding to the page based on the interface level information and the interface information.

In some example embodiments of the present disclosure, the apparatus further comprises: the base map generation module is used for generating a page base map corresponding to the necessary interface set according to the page information of the page corresponding to each interface in the necessary interface set; a current interface determining module, configured to determine, in response to a current page request for the page, current interface information corresponding to a URL of the page; a current graph generating module, configured to generate a current page graph corresponding to the current interface information based on page information of the page corresponding to each interface in the current interface information; the first comparison module is used for determining the similarity between the current page map and the page base map and giving an alarm when the similarity between the current page map and the page base map is lower than a first preset threshold value.

In some example embodiments of the present disclosure, the apparatus further comprises: the blank map generating module is used for generating a blank page map corresponding to the page size of the page; and the second comparison module is used for determining the similarity between the current page image and the blank page image and giving an alarm when the similarity between the current page image and the blank page image is higher than a second preset threshold value.

In some example embodiments of the present disclosure, the request response module is further configured to: analyzing the page request to obtain at least one URL corresponding to the page; acquiring a domain name corresponding to each URL in the at least one URL, and determining whether the domain name is in a pre-configured domain name list; if the domain name list is in the domain name list, taking the corresponding URL as the URL of the page; and if the URL is not in the domain name list, filtering out the corresponding URL.

In some example embodiments of the present disclosure, the request response module is further configured to: extracting interface information corresponding to the URL of the page from the page request according to the extracted URL of the page; generating a message based on the URL of the page and interface information corresponding to the URL, wherein the message comprises KEY pairs, the KEY of each KEY pair is the URL, and the VALUE VALUE is an interface name in the interface information; and sending the message to a message queue.

In some example embodiments of the present disclosure, the apparatus further comprises: the monitoring processing module is used for acquiring the URL of the page and the corresponding interface information from the new message if the message queue is monitored to receive the new message; and the storage module is used for storing the URL of the page and the corresponding interface into a database.

In some example embodiments of the present disclosure, the apparatus further comprises: the function verification module is used for verifying whether each basic service function under the service scene is normal or not based on the necessary interface set; and the verification result processing module is used for determining the necessary interface set as a correct necessary interface set if each basic service function is normal.

In some example embodiments of the present disclosure, the apparatus further comprises: the extraction module is used for responding to a current page request of the page and extracting current interface information corresponding to the URL of the page from the current page request; and the updating module is used for storing the current interface information if the current interface information does not exist in the database.

In a third aspect of embodiments of the present disclosure, there is provided a computing device comprising: a processor and a memory, the memory storing executable instructions, the processor being configured to invoke the memory-stored executable instructions to perform the method of any of the first aspects described above.

In a fourth aspect of embodiments of the present disclosure, there is provided a medium having stored thereon a program which, when executed by a processor, implements the method as described in any one of the above first aspects.

According to the technical scheme of the embodiment of the disclosure, on one hand, the URL of the page and the interface information corresponding to the URL are extracted from the page request, and the mapping relation between the URL and the interface can be automatically obtained; on the other hand, a necessary interface set corresponding to the page is determined based on the interface level information and the interface information, so that necessary interface data depended on by the page can be automatically reported, and the necessary interface is conveniently and automatically maintained; on the other hand, the necessary interfaces can be maintained automatically, so that the efficiency and the accuracy of interface maintenance are improved, and the labor cost and the time cost of interface maintenance are reduced.

Drawings

The above and other objects, features and advantages of exemplary embodiments of the present disclosure will become readily apparent from the following detailed description read in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which:

fig. 1 schematically shows a schematic diagram of an application scenario of an interface maintenance method according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow diagram of an interface maintenance method according to some embodiments of the present disclosure;

FIG. 3 schematically illustrates a flow chart applying interface maintenance methods according to further embodiments of the present disclosure;

FIG. 4 schematically illustrates a flow diagram of an interface maintenance method according to further embodiments of the present disclosure;

FIG. 5 schematically illustrates an architectural diagram of necessary interface set validation, according to some embodiments of the present disclosure;

FIG. 6 schematically shows a schematic diagram of page comparisons according to some embodiments of the present disclosure;

FIG. 7 schematically shows a schematic diagram of page alignments according to further embodiments of the present disclosure;

FIG. 8 schematically illustrates a schematic diagram of a computer-readable storage medium, according to some embodiments of the present disclosure;

FIG. 9 schematically illustrates a block diagram of an interface maintenance device, according to some embodiments of the present disclosure;

FIG. 10 schematically illustrates a block diagram of a computing device, in accordance with some embodiments of the present disclosure.

In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

Detailed Description

The principles and spirit of the present disclosure will be described below with reference to a number of exemplary embodiments. It is understood that these embodiments are given solely for the purpose of enabling those skilled in the art to better understand and to practice the present disclosure, and are not intended to limit the scope of the present disclosure in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

As will be appreciated by one skilled in the art, embodiments of the present disclosure may be embodied as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

According to an embodiment of the disclosure, an interface maintenance method, an interface maintenance device, a computing device and a medium are provided.

In this context, it is to be understood that the terms referred to:

the necessary interface sets are: the interface set of the service core function range, also called as the minimum interface set, takes the service entry as a starting point, comprises the complete operation process of the user, and can support the use experience of the core function of the user.

Http Header: the field is used for transmitting additional information in an HTTP (Hyper Text Transfer Protocol) request or response, is used for accurately describing the behavior of a resource, a server or a client which is being acquired, and defines specific operation parameters in an HTTP transaction.

Http refer: is part of the Http Header and represents the previous page visited by the browser, and the link that may be considered the previously visited page takes the browser to the current page. When a browser sends a request to a web server, it typically takes a refer to the server which tells the server which page the web page is linked from, and the server can therefore obtain some information for processing.

A gateway: the "gateway" connecting one network to another can accept HTTP interface requests, mainly to do some pre-processing of non-service attributes.

Message queue: the container of the message is saved during the transmission of the message.

Moreover, any number of elements in the drawings are by way of example and not by way of limitation, and any nomenclature is used solely for differentiation and not by way of limitation.

The principles and spirit of the present disclosure are explained in detail below with reference to several representative embodiments of the present disclosure.

Summary of The Invention

The inventor finds that, in order to solve the problem that the efficiency and accuracy of the maintenance of the service interface in the later period are low, in one technical scheme, the information of the page and the interface is transmitted through the parameters of the service interface, and the service interface is maintained at the server side according to the information transmitted by the parameters. However, in this technical solution, a field needs to be reserved for the service interface to transmit information of a mapping relationship between a page and a dependent interface thereof, which brings additional obstacle points to service development, and if the service interface needs to be upgraded or updated in a later period, more uncontrollable/unstable factors are brought by the reserved field, which increases a risk of improper maintenance of the service interface.

Based on the above, the basic idea of the present disclosure is: responding to a page request of a page, and extracting a URL (uniform resource locator) of the page and interface information corresponding to the URL from the page request; determining interface level information of each interface in the interface information, wherein the interface level information is level information defined according to the function of the interface in a service scene; and determining a necessary interface set corresponding to the page based on the interface level information and the interface information. According to the technical scheme of the embodiment of the disclosure, on one hand, the URL of the page and the interface information corresponding to the URL are extracted from the page request, and the mapping relation between the URL and the interface can be automatically obtained; on the other hand, a necessary interface set corresponding to the page is determined based on the interface level information and the interface information, so that necessary interface data depended on by the page can be automatically reported, and the necessary interface is conveniently and automatically maintained; on the other hand, the necessary interfaces can be maintained automatically, so that the efficiency and the accuracy of interface maintenance are improved, and the labor cost and the time cost of interface maintenance are reduced.

Having described the general principles of the present disclosure, various non-limiting embodiments of the present disclosure are described in detail below.

Application scene overview

It should be noted that the following application scenarios are merely illustrated to facilitate understanding of the spirit and principles of the present disclosure, and embodiments of the present disclosure are not limited in this respect. Rather, embodiments of the present disclosure may be applied to any scenario where applicable.

Fig. 1 schematically shows a schematic diagram of an application scenario of an interface maintenance method according to an embodiment of the present disclosure.

Referring to fig. 1, the application scenario may include: at least one client terminal 110 and a server terminal 120, wherein the client terminal 110 is installed with a plurality of applications, such as a shopping application, a music application, a news application, etc. The client terminal 110 and the server terminal 120 communicate with each other through a network 130. Taking a music application scenario as an example, a user opens a music application installed on the client 110, clicks a page corresponding to a certain page on the music application, for example, a song ranking list plate, and sends a page request of the page to the server 120, and the server 120, in response to the page request of the page, extracts a URL of the page and interface information corresponding to the URL from the page request.

The client 110 may be a mobile phone, a tablet computer, a desktop computer, a portable notebook computer, or a vehicle-mounted terminal. The server side 120 may be a physical server including independent hosts, or a virtual server carried by a host cluster, or a cloud server. The Network 130 may be a wired Network or a wireless Network, for example, the Network 130 may be a PSTN (Public Switched Telephone Network) or the internet.

Exemplary method

In combination with the above application scenario, an interface maintenance method according to an exemplary embodiment of the present disclosure is described below with reference to fig. 2. The execution subject of the interface maintenance method provided by the embodiment of the present disclosure may be a device having a calculation processing function, such as the server 120 in fig. 1. It should be noted that the above application scenarios are merely illustrative for the convenience of understanding the spirit and principles of the present disclosure, and embodiments of the present disclosure are not limited in this respect. Rather, embodiments of the present disclosure may be applied to any scenario where applicable.

Referring to fig. 2, in step S210, in response to a page request for a page, a URL of the page and interface information corresponding to the URL are extracted from the page request.

In an example embodiment, the page may be a page of an application, such as a music application, a shopping application, or the like. The application program client side responds to the clicking operation of the user on the page of the application program and sends a page request corresponding to the page to the server through an HTTP (Hyper Text Transfer Protocol).

In an example embodiment, the page request contains URL information of the page and corresponding interface information. According to the HTTP protocol, the URL information may be included in the referrer field of the header of the HTTP message. The page request may correspond to one or more interfaces of the HTTP protocol, and taking the page as a ranking list page of the music application as an example, the page request of the ranking list page may correspond to a new song list interface, a hot song list interface, a popularity list interface, and the like.

Further, in an example embodiment, the server responds to the page request, parses the page request, and extracts the URL of the corresponding page and the interface information corresponding to the URL from the page request. Taking the page request as an HTTP request as an example, the server may parse the page request according to an HTTP protocol, extract a corresponding URL from a referrer field of the HTTP message, and extract interface information corresponding to the URL through a regular expression. For example, let the page request contain the URL "http:// music.163.com/api/query/infouserID ═ 123", which is obtained by the expression request. getHeaders (). get ("refer"); and matching the character string 'api' through the regular expression to obtain corresponding interface information, namely 'api/query/info'.

In step S220, interface level information of each interface in the interface information is determined, where the interface level information is level information defined according to a function of the interface in a service scenario.

In an example embodiment, the interface level information is level information defined according to the degree of importance of the function of the interface in the traffic scene. Taking a cash desk page as an example, the interface level includes three levels of P0, P1 and P2, and the level P0 > the level P1 > the level P2, the higher the interface level is, the more important the function of the interface in a business scene is, the interface corresponding to the cash desk page includes a commodity display interface, a ordering interface, a collection interface, a shopping cart adding interface, and the like, wherein the commodity display interface and the ordering interface are more important, the level of the commodity display interface and the ordering interface can be defined as the level P0, the level of the shopping cart adding interface is defined as the level P1, and the level of the collection interface is defined as the level P2.

Further, in the present exemplary embodiment, the level information of each interface is stored in advance in the database, and the interface level information of each interface is queried from the database according to the identification information of each interface. For example, the interface corresponding to the checkout counter page includes a commodity display interface, i.e., interface1, a bill ordering interface, i.e., interface2, a collection interface, i.e., interface3, and a shopping cart interface, i.e., interface4, and the level information of the corresponding interface is queried from the database according to the identification information of each interface.

In addition, in some example embodiments, the number of times that the user uses the interface corresponding to the page may be counted according to the historical user behavior data of the predetermined time period corresponding to the page, the interfaces corresponding to the page may be sorted according to the number of times of use, and the level of the interface may be defined according to the sorting result. Taking a ranking list page with a page as a music application as an example, the three interfaces are ranked according to the use times of the user using the hot song list interface, the popularity list interface and the new song list interface, and the ranks of the three interfaces are defined according to the ranking result, for example, the hot song list interface is in the P0 rank, the new song list interface is in the P1 rank, and the popularity list interface is in the P2 rank.

In step S230, a necessary interface set corresponding to the page is determined based on the interface level information and the interface information.

In an example embodiment, the interfaces are screened based on the interface level information of each interface in the interface information, a target interface with a level higher than a predetermined threshold is obtained, and the target interface is used as a necessary interface set corresponding to a page. For example, if the level information of the interface is 3 levels, the interface with the highest level may be used as the necessary interface of the page.

Taking the cash register page as an example, the levels of the commodity display interface and the ordering interface are P0 level, the level of the shopping cart adding interface is P1 level, and the level of the collection interface is P2 level. The commodity display interface (level P0) and the order placing interface (level P0) are used as interfaces in the necessary interface set of the cash desk page.

According to the technical solution in the example embodiment of fig. 2, on one hand, the URL of the page and the interface information corresponding to the URL are extracted from the page request, and the mapping relationship between the URL and the interface can be automatically obtained; on the other hand, a necessary interface set corresponding to the page is determined based on the interface level information and the interface information, so that necessary interface data depended on by the page can be automatically reported, and the necessary interface is conveniently and automatically maintained; on the other hand, the necessary interfaces can be maintained automatically, so that the efficiency and the accuracy of interface maintenance are improved, and the labor cost and the time cost of interface maintenance are reduced.

In addition, after the interface comes online, the interface may be updated. In an example embodiment, in response to a current page request for a page, current interface information corresponding to a URL of the page is extracted from the current page request; and if the current interface information does not exist in the database, storing the current interface information. For example, after each service interface of the service system is on-line, the service is continuously provided to the user, and since the operation paths of different users on the page are different, some interfaces may not be acquired at the first time, and thus, scenarios and interface updates may occur. At this time, if the collected current interface does not exist in the database, the current interface is added to a necessary interface set stored in the database in an incremental updating mode. After the incremental update is completed, the maintainer is reminded that the necessary interface set is changed and needs to be verified, so that the integrity and the availability of the updated necessary interface set are guaranteed.

Fig. 3 schematically illustrates a flow diagram to which interface maintenance methods according to further embodiments of the present disclosure are applied.

Referring to fig. 3, in step S310, the client 310 transmits a page request to the gateway 315.

In an example embodiment, in response to a user click operation on a page of an application of the client 310, the client 310 may send a page request to the gateway 315, the page request including an interface requesting several HTTP protocols. At this time, according to the characteristics of the HTTP protocol, the URL information of the current page is automatically filled in the referrer field of the HTTP header, and the referrer field information is transmitted to the server 320 providing the interface. In this exemplary embodiment, the page request is not directly requested to the server 320 providing the interface, but is first requested to the gateway 315, and after the gateway 315 performs some pre-processing of non-business logic (such as permission check, audit information record, routing query), the page request is routed to the corresponding server 320 providing the interface.

In step S315, the gateway 315 filters out invalid domain names.

In an exemplary embodiment, at the gateway 315 layer, the data of the referrer field in the HTTP header is parsed to obtain the original URL of the page, and then filtering is performed to obtain the required interface data, and unnecessary discarding is performed.

For example, the domain name information of the page to be maintained is configured in the configuration file in advance, for example, the domain name information in the configuration file may include: music.163.com; qa.igeme.163.com. Acquiring a domain name of a page URL, comparing the acquired domain name with the domain name in a configuration file in terms of similarity, and if the similarity is greater than a preset threshold value, determining that the domain name is in the configuration file and reserving the URL corresponding to the domain name; and if the domain name is determined not to be in the configuration file, discarding the URL corresponding to the domain name.

In step S320, the message generation server 325 sends a message containing the URL and the corresponding interface name to the message queue 330.

In an exemplary embodiment, the message generation server 325 sends a message to the message queue 330 with the URL as key and the interface name as value. For example, let the reserved URL of the page be "http:// music.163. com/mypage? 123 'of userID, 123' of page dependency interface, 123 'of http:// music.163.com/api/query/info userID, and then constructing a message body of { "pageId': "music.163. com/mypage", "uri": and the api/query/info is used for sending the message body to a message queue.

In step S325, the message listening server 335 subscribes to the listening message queue 330.

In an example embodiment, at message listening server 335, the message listening side, listens for previously issued messages and reads the messages.

In step S330, the message is parsed to obtain the URL and the interface name, and stored in the database 340.

In an exemplary embodiment, the URL and interface name are parsed and the results of the parsing are then stored in database 340. At this time, all interface lists depended on by one page can be obtained through the page request corresponding to the page.

In step S335, level information of the interface is determined.

In the present exemplary embodiment, the level information of each interface is stored in advance in the database, and the interface level information 345 of each interface is queried from the database according to the identification information of each interface. For example, the interfaces include interface1, interface2, interface3, and interface4, and the level information 345 of the corresponding interface, i.e., interface 1(P1), interface 2(P1), interface 3(P0), and interface 4(P0), is queried from the database according to the identification information of each interface.

In step S340, a necessary interface set is determined according to the interface level information.

In the exemplary embodiment, the interfaces are screened based on the interface level information of each interface in the interface information, and a target interface with a level higher than a predetermined threshold is obtained, and the target interface is used as a necessary interface set 350 corresponding to the page. For example, if the level information of the interfaces is 3 levels P0, P1, and P2, and the level P0 > P1 > P2, the higher the level of the interface is, the more important the function of the interface in the service scene is, the interface with the highest level, i.e., the level P0, may be used as the interface in the necessary interface set 350 of the page, i.e., interface 3(P0) and interface 4(P0) may be used as the interface in the necessary interface set corresponding to the URL.

According to the technical scheme in the example embodiment of fig. 3, on one hand, invalid URLs are filtered out through the gateway, and the accuracy of maintaining a necessary interface set of a page can be improved; on the other hand, the mapping relation information of the page and the interface is reported through the message queue, so that the interface list on which the page depends can be automatically and efficiently reported, and the efficiency of interface maintenance is further improved.

Fig. 4 schematically illustrates a flow diagram of an interface maintenance method according to further embodiments of the present disclosure.

Referring to fig. 4, in step S410, a page request sent by a client is received.

In an example embodiment, the page request may include a page URL and interface information on which the page depends. For example, let the page request contain the page URL "http:// music.163.com/mypageuserID ═ 123", and may also include the page request interface "http:// music.163.com/api/query/infouserID ═ 123".

In step S415, the page URL and the corresponding domain name are acquired.

In an example embodiment, the URL of the page and the domain name corresponding to the URL are obtained through an expression request.getheads (). get ("refer"), for example, the URL "http:// music.163.com/mypageuserID ═ 123", and the corresponding domain name is music.163. com.

In step S420, the configuration file is read.

In an example embodiment, the configuration file is configured with domain name information of a page to be maintained, and whether to reserve a URL for subsequent operations can be determined through the domain name information in the configuration file. For example, the domain name information in the configuration file may include: music.163.com; qa.igeme.163.com.

In step S425, it is determined whether the acquired domain name is in the profile. If not, go to step S430; if it is in the configuration file, proceed to step S435.

In an example embodiment, the obtained domain name may be compared with a domain name in a configuration file for similarity, and if the similarity is greater than a predetermined threshold, it is determined that the domain name is in the configuration file.

In step S430, the URL corresponding to the domain name is discarded.

In step S435, the URL corresponding to the domain name is retained.

In step S440, a message is constructed and sent to a message queue.

In an example embodiment, a message is constructed from a page URL and corresponding interface information and sent to a message queue. For example, if the reserved page URL is "http:// music.163.com/mypageuserID ═ 123", and the page dependent interface is "http:// music.163.com/api/query/infouserID ═ 123", then the message body constructed is { "pageId": "music.163. com/mypage", "uri": and the api/query/info is used for sending the message body to a message queue.

In step S445, the messages in the message queue are listened to.

In step S450, the monitored message is parsed to obtain the URL and the interface name, and the URL and the interface name are stored in the database.

In an example embodiment, the intercepted message is parsed to obtain the pageId and uri in the message body, and the pageId and uri are stored in the database as unique keys in the database, such as a primary key, a URL, and an interface name. Table 2 below shows page URLs, interface names, and interface level information stored in the database.

TABLE 2 Page URL, interface name, and interface level information

Through the steps, the automatic reporting of the interface is completed, and the dependency relationship between the page and the interface can be stored. Further, the interface level definition information can be utilized to obtain the interface necessary set corresponding to the page.

According to the technical scheme in the example embodiment of fig. 4, on one hand, invalid URLs are filtered out through the configuration file, and the accuracy of maintaining a necessary interface set of a page can be improved; on the other hand, the mapping relation information of the page and the interface is reported through the message queue, so that the interface list on which the page depends can be automatically and efficiently reported, and the efficiency of interface maintenance is further improved.

Fig. 5 schematically illustrates an architectural diagram of necessary interface set validation, according to some embodiments of the present disclosure.

After obtaining the necessary interface set, the current necessary interface set needs to be verified to ensure that the interfaces included in the necessary interface set can meet the service requirements. Therefore, in the exemplary embodiment, based on the necessary interface set, it is verified whether each basic service function in the service scenario is normal; and if the functions of all the basic services are normal, determining the necessary interface set as a correct necessary interface set.

Referring to fig. 5, a client 310 sends a page request to a gateway 315, and the gateway 315 limits access rights of a non-P0 interface of a specified user (e.g., a member user) in the service scenario based on a "black and white list" function, and at this time, verifies whether each basic service function in the service scenario is normal; and if the functions of all the basic services are normal, determining the necessary interface set as a correct necessary interface set. For example, a member list and a P0 interface list such as userId, interface3 and interface4 may be configured in a configuration file, and the gateway may limit the access right of a specified user (e.g., a member user) to a non-P0 interface in the service scenario according to the configuration file, determine whether the functions of the specified user accessing the P0 interface, i.e., interface3 and interface4, are normal, and determine that the necessary interface set is a correct necessary interface set if the functions of each interface are normal.

According to the technical solution in the example embodiment of fig. 5, the validity and availability of the necessary interface set can be determined by verifying the function of the necessary interface set.

In addition, under the condition that the functions of the necessary interface set are ensured to be correct, daily polling on the interfaces within the range of the necessary interface set is required. On the user level, the service function of the service interface is presented in a page form, and the change of the interface service can cause the change of the page presentation, on one hand, the page condition that page elements are relatively fixed needs to be inspected; on the other hand, in business logic, the page does not allow the whole page to have a white screen, and the white screen inspection needs to be performed on the condition that page elements change frequently. Therefore, in the example embodiment, on one hand, a page base map corresponding to the necessary interface set is generated according to the page information of the page corresponding to each interface in the necessary interface set; in response to a current page request for a page, determining current interface information corresponding to a URL of the page; generating a current page map corresponding to the current interface information based on the page information of the page corresponding to each interface in the current interface information; and determining the similarity between the current page map and the page base map, and giving an alarm when the similarity between the current page map and the page base map is lower than a first preset threshold value. On the other hand, generating a blank page map corresponding to the page size of the page; and determining the similarity between the current page image and the blank page image, and giving an alarm when the similarity between the current page image and the blank page image is higher than a second preset threshold value.

For example, in the process of polling a necessary interface set, an opencv framework is adopted, and polling is performed by using a scheme of picture comparison. Inspection can be performed by:

(1) and obtaining a page base map by using the page information of the page corresponding to the necessary interface set.

(2) A blank page of the same size as the page is generated and may be referred to as a white map.

(3) And configuring a polling task and starting polling.

And (3) inspection flow: when the polling task is triggered, obtaining a current page image according to page information corresponding to a necessary interface set of the current page, comparing the current page image with a page base image aiming at a relatively fixed page, and alarming when the similarity is lower than a preset threshold value; and aiming at the page with frequently changed and large content change, comparing the current page image with the white image, and alarming when the similarity is higher than a certain threshold.

FIG. 6 schematically shows a schematic diagram of page comparisons according to some embodiments of the present disclosure.

Referring to fig. 6, the page alignment diagram is a schematic diagram of "page shape is relatively fixed". FIG. 6 is a bottom view of a page as a basis for verification; and the left image is the current page image of the current inspection, the difference degree between the current page image and the page bottom image is judged to be 15.17, and an abnormal alarm is given when the difference degree exceeds a preset threshold value. Referring to FIG. 6, the current page map has more immediate renewal controls than the page base map.

FIG. 7 schematically shows a schematic diagram of page alignments, according to further embodiments of the present disclosure.

Referring to fig. 7, the diagram is a schematic diagram of page comparison of "page form is changed frequently", since a bottom image of a page is a white image and is not shown in fig. 7, a current page image is on the left, and it is determined that a difference value between the current page image and the bottom image of the page is 0.17 and is smaller than a predetermined threshold value, and an alarm is performed. Referring to fig. 7, the current page view has one more line of text than the page base view, and it is determined that the current page view is not much different from the white map and the user may not see anything.

By polling the page, the interface can be accurately presented on the client, and the effectiveness and the usability of a necessary interface set are further ensured.

Exemplary Medium

Having described the methods of the exemplary embodiments of the present disclosure, the media of the exemplary embodiments of the present disclosure are described next.

In some possible embodiments, aspects of the present disclosure may also be implemented as a medium having stored thereon program code for implementing steps in an interface maintenance method according to various exemplary embodiments of the present disclosure described in the above-mentioned "exemplary method" section of this specification when the program code is executed by a processor of a device.

In some possible embodiments, the program code is executable by a processor of the device to perform the following steps: step S210, responding to a page request for the page, and extracting the URL of the page and interface information corresponding to the URL from the page request; step S220, determining interface level information of each interface in the interface information, wherein the interface level information is level information defined according to the function of the interface in a service scene; step S230, determining a necessary interface set corresponding to the page based on the interface level information and the interface information.

Referring to fig. 8, a program product 800 for implementing the above-described data processing method according to an embodiment of the present disclosure is described, which may employ a portable compact disc read only memory and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto.

It should be noted that: the above-mentioned medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory, a read only memory, an erasable programmable read only memory, an optical fiber, a portable compact disk read only memory, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take a variety of forms, including, but not limited to: an electromagnetic signal, an optical signal, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, optical fiber cable, radio frequency signals, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device over any kind of network, including a local area network or a wide area network, or may be connected to an external computing device (e.g., over the internet using an internet service provider).

Exemplary devices

Having described the media of the exemplary embodiment of the present disclosure, the interface maintenance device of the exemplary embodiment of the present disclosure is explained next with reference to fig. 9.

Referring to fig. 9, the interface maintenance apparatus 900 includes: a request response module 910, configured to, in response to a page request for a page, extract a uniform resource locator URL of the page and interface information corresponding to the URL from the page request; a level information determining module 920, configured to determine interface level information of each interface in the interface information, where the interface level information is level information defined according to a function of the interface in a service scenario; a necessary interface determining module 930, configured to determine a necessary interface set corresponding to the page based on the interface level information and the interface information.

In some example embodiments of the present disclosure, the apparatus 900 further comprises: the base map generation module is used for generating a page base map corresponding to the necessary interface set according to the page information of the page corresponding to each interface in the necessary interface set; a current interface determining module, configured to determine, in response to a current page request for the page, current interface information corresponding to a URL of the page; a current graph generating module, configured to generate a current page graph corresponding to the current interface information based on page information of the page corresponding to each interface in the current interface information; the first comparison module is used for determining the similarity between the current page map and the page base map and giving an alarm when the similarity between the current page map and the page base map is lower than a first preset threshold value.

In some example embodiments of the present disclosure, the apparatus 900 further comprises: the blank map generating module is used for generating a blank page map corresponding to the page size of the page; and the second comparison module is used for determining the similarity between the current page image and the blank page image and giving an alarm when the similarity between the current page image and the blank page image is higher than a second preset threshold value.

In some example embodiments of the present disclosure, the request response module 910 is further configured to: analyzing the page request to obtain at least one URL corresponding to the page; acquiring a domain name corresponding to each URL in the at least one URL, and determining whether the domain name is in a pre-configured domain name list; if the domain name list is in the domain name list, taking the corresponding URL as the URL of the page; and if the URL is not in the domain name list, filtering out the corresponding URL.

In some example embodiments of the present disclosure, the request response module 910 is further configured to: extracting interface information corresponding to the URL of the page from the page request according to the extracted URL of the page; generating a message based on the URL of the page and interface information corresponding to the URL, wherein the message comprises KEY pairs, the KEY of each KEY pair is the URL, and the VALUE VALUE is an interface name in the interface information; and sending the message to a message queue.

In some example embodiments of the present disclosure, the apparatus 900 further comprises: the monitoring processing module is used for acquiring the URL of the page and the corresponding interface information from the new message if the message queue is monitored to receive the new message; and the storage module is used for storing the URL of the page and the corresponding interface into a database.

In some example embodiments of the present disclosure, the apparatus 900 further comprises: the function verification module is used for verifying whether each basic service function under the service scene is normal or not based on the necessary interface set; and the verification result processing module is used for determining the necessary interface set as a correct necessary interface set if each basic service function is normal.

In some example embodiments of the present disclosure, the apparatus 900 further comprises: the extraction module is used for responding to a current page request of the page and extracting current interface information corresponding to the URL of the page from the current page request; and the updating module is used for storing the current interface information if the current interface information does not exist in the database.

Exemplary computing device

Having described the methods, media, and apparatus of the exemplary embodiments of the present disclosure, a computing device in accordance with another exemplary embodiment of the present disclosure is described next.

As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or program product. Accordingly, various aspects of the present disclosure may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

In some possible embodiments, a computing device according to embodiments of the present disclosure may include at least one processor, and at least one memory. Wherein the memory stores program code that, when executed by the processor, causes the processor to perform the steps in the interface maintenance method according to various exemplary embodiments of the present disclosure described in the "exemplary methods" section above in this specification. For example, the processor may execute step S210 shown in fig. 2, in response to a page request for a page, extracting a URL of the page and interface information corresponding to the URL from the page request; step S220, determining interface level information of each interface in the interface information, wherein the interface level information is level information defined according to the function of the interface in a service scene; step S230, determining a necessary interface set corresponding to the page based on the interface level information and the interface information. As another example, the processor may also perform the steps as shown in fig. 4.

An electronic device 1000 according to an example embodiment of the present disclosure is described below with reference to fig. 10. The electronic device 1000 shown in fig. 10 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 10, the electronic device 1000 is embodied in the form of a general purpose computing device. The components of the electronic device 1000 may include, but are not limited to: the at least one processing unit 1010, the at least one memory unit 1020, and a bus 1030 that couples various system components including the memory unit 1020 and the processing unit 1010.

Bus 1030 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures.

The storage unit 1020 may include a readable medium in the form of a volatile Memory, such as a RAM (Random Access Memory) 1021 and/or a cache Memory 1022, and may further include a ROM (Read-Only Memory) 1023.

Storage unit 1020 may also include a program/utility 1025 having a set (at least one) of program modules 1024, such program modules 1024 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

The electronic device 1000 may also communicate with one or more external devices 1040 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 1000, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 1000 to communicate with one or more other computing devices. Such communication may occur through input/output (I/O) interfaces 1050. Also, the electronic device 1000 may communicate with one or more networks (e.g., a local area network, a wide area network, and/or a public network, such as the Internet) through the network adapter 1060. As shown, the network adapter 1060 communicates with the other modules of the electronic device 1000 over the bus 1030. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with the electronic device 1000, including but not limited to: microcode, device drivers, Redundant processing units, external disk drive Arrays, RAID (Redundant array of Independent Disks) systems, tape drives, and data backup storage systems, among others.

It should be noted that although in the above detailed description several units or sub-units of the interface maintenance device are mentioned, such a division is only exemplary and not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Further, while the operations of the disclosed methods are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

While the spirit and principles of the present disclosure have been described with reference to several particular embodiments, it is to be understood that the present disclosure is not limited to the particular embodiments disclosed, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. The disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. An interface maintenance method, comprising:

responding to a page request of a page, and extracting a Uniform Resource Locator (URL) of the page and interface information corresponding to the URL from the page request;

determining interface level information of each interface in the interface information, wherein the interface level information is level information defined according to the function of the interface in a service scene;

and determining a necessary interface set corresponding to the page based on the interface level information and the interface information.

2. The method of claim 1, further comprising:

generating a page base map corresponding to the necessary interface set according to the page information of the page corresponding to each interface in the necessary interface set;

determining current interface information corresponding to a URL of the page in response to a current page request for the page;

generating a current page map corresponding to the current interface information based on the page information of the page corresponding to each interface in the current interface information;

and determining the similarity between the current page map and the page base map, and giving an alarm when the similarity between the current page map and the page base map is lower than a first preset threshold value.

3. The method of claim 2, further comprising:

generating a blank page image corresponding to the page size of the page;

and determining the similarity between the current page map and the blank page map, and giving an alarm when the similarity between the current page map and the blank page map is higher than a second preset threshold value.

4. The method of claim 1, wherein extracting the URL of the page from the page request comprises:

analyzing the page request to obtain at least one URL corresponding to the page;

acquiring a domain name corresponding to each URL in the at least one URL, and determining whether the domain name is in a pre-configured domain name list;

if the domain name list is in the domain name list, taking the corresponding URL as the URL of the page;

and if the URL is not in the domain name list, filtering out the corresponding URL.

5. The method according to claim 4, wherein the extracting interface information corresponding to the URL from the page request includes:

extracting interface information corresponding to the URL of the page from the page request according to the extracted URL of the page;

generating a message based on the URL of the page and interface information corresponding to the URL, wherein the message comprises KEY pairs, the KEY of each KEY pair is the URL, and the VALUE VALUE is an interface name in the interface information;

and sending the message to a message queue.

6. The method of claim 5, further comprising:

if monitoring that the message queue receives a new message, acquiring a URL (uniform resource locator) of a page and corresponding interface information from the new message;

and storing the URL of the page and the corresponding interface into a database.

7. The method of claim 1, further comprising:

verifying whether each basic service function under the service scene is normal or not based on the necessary interface set;

and if the basic service functions are normal, determining that the necessary interface set is a correct necessary interface set.

8. An interface maintenance device, comprising:

the request response module is used for responding to a page request of a page, and extracting a Uniform Resource Locator (URL) of the page and interface information corresponding to the URL from the page request;

the level information determining module is used for determining interface level information of each interface in the interface information, wherein the interface level information is level information defined according to the function of the interface in a service scene;

and the necessary interface determining module is used for determining a necessary interface set corresponding to the page based on the interface level information and the interface information.

9. A computing device, comprising: a processor and a memory, the memory storing executable instructions, the processor to invoke the memory-stored executable instructions to perform the method of any of claims 1 to 7.

10. A medium having stored thereon a program which, when executed by a processor, carries out the method of any one of claims 1 to 7.