WO2014044130A1 - 业务巡检方法和系统、计算机存储介质 - Google Patents

业务巡检方法和系统、计算机存储介质 Download PDF

Info

Publication number
WO2014044130A1
WO2014044130A1 PCT/CN2013/083198 CN2013083198W WO2014044130A1 WO 2014044130 A1 WO2014044130 A1 WO 2014044130A1 CN 2013083198 W CN2013083198 W CN 2013083198W WO 2014044130 A1 WO2014044130 A1 WO 2014044130A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
service
service inspection
inspection item
item
Prior art date
Application number
PCT/CN2013/083198
Other languages
English (en)
French (fr)
Inventor
李星
徐伟
沈武魁
许文英
徐盎
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Priority to IN1263DEN2015 priority Critical patent/IN2015DN01263A/en
Priority to RU2014136486A priority patent/RU2607991C2/ru
Priority to KR1020147033870A priority patent/KR101482651B1/ko
Priority to CA 2866308 priority patent/CA2866308A1/en
Priority to US14/395,667 priority patent/US20150081625A1/en
Priority to JP2015523409A priority patent/JP5782585B1/ja
Publication of WO2014044130A1 publication Critical patent/WO2014044130A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/006—Identification
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G06F15/161—Computing infrastructure, e.g. computer clusters, blade chassis or hardware partitioning

Definitions

  • the present invention relates to computer network technologies, and in particular, to a service inspection method and system, and a computer storage medium.
  • a business is a service that performs a certain function. If the service is deployed on the server, the maintenance personnel are required to perform maintenance. For example, if the service is deployed on the server, the operation and maintenance personnel will deploy the monitoring program at the same time. The service will be uninstalled from a server. The operation and maintenance personnel will stop the service and stop the monitoring. Procedure, when a server is to be retired, the operation and maintenance personnel need to stop all business services and stop all monitoring procedures.
  • a service inspection method includes the following steps:
  • the changing operation is a new operation, a modification operation, or a deletion operation.
  • the method further includes the steps of:
  • the relationship between the service inspection item and the server is updated according to the traversal result.
  • the step of updating the association relationship between the service inspection item and the server according to the traversal result includes:
  • the server port is not matched with the service patrol item, or the service process is not matched with the service patrol item, the association between the server and the corresponding service patrol item is deleted.
  • the association relationship between the newly added server and the corresponding service inspection item is established.
  • the method before the step of periodically traversing the service inspection item information, the server information, and the relationship between the service inspection item and the server, the method further includes the following steps:
  • the association between the server and the corresponding service inspection item is moved to the server. Deleting the queue;
  • the association relationship between the newly added server and the corresponding service inspection item is moved into the new queue.
  • the traversal of the newly added queue increases the association between the server in the newly added queue and the service inspection item.
  • the method before the step of obtaining a change operation on the service inspection item, the method further includes the steps of:
  • the relationship between the service inspection item information, the server information, and the service inspection item and the server is stored in the service inspection database.
  • the method before the obtaining the change operation on the service inspection item, the method further includes the following steps:
  • the steps to update the results include:
  • the method further includes the steps of:
  • a business inspection system comprising:
  • An interaction module configured to acquire a change operation on a service inspection item
  • a processing module configured to acquire a service process or port bound to the service inspection item according to the change operation, and find a corresponding server according to the service process or port, and update an association relationship between the service inspection item and the server. , get the corresponding update results;
  • a publishing module for publishing the update result
  • the changing operation is a new operation, a modification operation, or a deletion operation.
  • the service inspection system further includes:
  • the scanning module is configured to periodically traverse the relationship between the service inspection item information, the server information, and the service inspection item and the server;
  • the processing module is further configured to update an association relationship between the service inspection item and the server according to the traversal result.
  • the processing module is further configured to: if the server is invalid or cannot find the server, delete the association relationship related to the server, if the server port is not matched with the port of the service inspection item or the server If the service process is not matched with the service process, the association between the server and the corresponding service inspection item is deleted, and if the server is added and the new server does not exist, the corresponding server does not exist.
  • the association relationship between the service inspection item and the corresponding service inspection item is established.
  • the service inspection system further includes:
  • the processing module is further configured to: if the server is invalid or cannot find the server, move the association relationship related to the server into the delete queue, if the port that the server port is bound to the service inspection item does not match or the service on the server If the process is not matched with the service process, the association between the server and the corresponding service inspection item is moved to the deletion queue, and if the server is added and the new server does not exist. And the associated relationship between the newly added server and the corresponding service inspection item is moved into the new queue;
  • the scanning module is further configured to traverse the deletion queue, and the processing module is further configured to delete an association relationship between the server in the deletion queue and a service inspection item;
  • the scanning module is further configured to traverse the newly added queue, and the processing module is further configured to increase an association relationship between the server and the service inspection item in the newly added queue.
  • the service inspection system further includes:
  • the service inspection database is used to store the relationship between the service inspection item information, the server information, and the service inspection item and the server.
  • the service inspection system further includes:
  • a classification module for classifying servers
  • Tag module for marking each type of server
  • the processing module is further configured to: obtain a service process or a port bound to the newly added service inspection item according to the change operation, and find a server of the corresponding class according to the service process or port, and update the service inspection item and each class. The relationship between the servers is updated accordingly.
  • the switching module is further configured to obtain a query request, and view an association relationship between the updated service inspection item and the server according to the query request.
  • One or more computer storage media containing computer executable instructions for performing a service inspection method comprising the steps of:
  • the service inspection method and system, and the computer storage medium obtain the port or service process bound to the service inspection item according to the change operation, automatically find the corresponding server according to the port or the service process, and update the service inspection item and the server. Correlation relationship, release update results, automatically update maintenance business, release operation and maintenance personnel from repetitive labor, and reduce manual investment.
  • FIG. 1 is a flow chart of a method for service inspection in an embodiment
  • FIG. 2 is a flowchart of querying a relationship between a service inspection item and a server in an embodiment
  • FIG. 3 is a schematic diagram showing the internal structure of a service inspection system in an embodiment
  • FIG. 4 is a schematic diagram showing the internal structure of a service inspection system in another embodiment
  • FIG. 5 is a schematic diagram showing the internal structure of a service inspection system in another embodiment
  • Figure 6 is a timing diagram of the operation of the business inspection system.
  • a service inspection method includes the following steps:
  • Step S110 obtaining a change operation on the service inspection item.
  • the change operation of the service inspection item is obtained on the configuration interface of the service inspection.
  • the business inspection item is the smallest business monitoring program unit, which is bound to a business process or an open port, and then is responsible for monitoring the business process or the port.
  • the change operation can be a new operation, a modification operation, or a delete operation.
  • the method before step S110, further includes the step of: storing the relationship between the service inspection item information, the server information, and the service inspection item and the server in the service inspection database.
  • the service inspection item information includes the CPU of the device (Central Processing Unit, central processing unit, hard disk, network status, monitoring service running status, etc., for example, Mysql (Associated Database Management System) connection number and other custom monitoring services.
  • the server information includes the service process information registered on the server, the port information, and the operation status of the server itself.
  • the service process information includes the name of the service process.
  • the port information includes an open port number.
  • the operation status of the server itself includes the status of running or decommissioning.
  • the relationship between the service inspection item and the server can be represented by the association between the service inspection item identifier and the server identifier.
  • the service patrol item identifier is used to distinguish the identity of the service patrol item.
  • the server ID is used to distinguish the identity of the service patrol item.
  • step S120 the service process or port bound to the service inspection item is obtained according to the change operation, and the corresponding server is found according to the service process or port, and the relationship between the service inspection item and the server is updated, and the corresponding relationship is obtained. Update the results.
  • the association relationship refers to a mapping relationship between the service inspection item and the server.
  • a server or a service process is configured on the server.
  • the service inspection item is bound to a service process or port.
  • the corresponding server can be found according to the service process or port.
  • Server uses IP (Internet Protocol, the protocol for interconnection between networks) is distinguished.
  • step S130 the update result is released.
  • Zookeeper is a distributed, open source distributed application coordination service, including a simple primitive set, is an important component of Hadoop and Hbase, mainly used to solve the consistency problem of application systems in distributed clusters. It provides data storage based on a directory node tree similar to a file system and maintains and monitors the state changes of stored data.
  • the ZooKeeper's script program contains the relationship between the service patrol item and the server. The running program searches for the corresponding server according to the server ID of the service patrol item identifier, and then publishes the service patrol item to the server.
  • the change operation is a new operation
  • first register the new service inspection item obtain the service process or port bound to the newly added service inspection item, find the corresponding server according to the service process or port, and then create a new one.
  • the relationship between the added service inspection items and the corresponding server is released, and the new service inspection items are released to the corresponding server through Zookeeper.
  • the change operation is a modification operation, that is, when the service inspection item itself is upgraded, the service process or port bound to the service inspection item is obtained, and the corresponding server is found according to the service process or port, and the upgraded service inspection item is updated.
  • the relationship between the servers is used to deploy the upgraded service inspection items to all the servers associated with them through Zookeeper, and replace the original service inspection items (that is, the monitoring program).
  • the change operation is the delete operation
  • the service inspection item is deleted, the service process or port bound to the service inspection item is obtained, and the corresponding server is found according to the service process or port, and all the servers associated with the service inspection item are selected. Perform the uninstall operation so that the service inspection item no longer works.
  • the foregoing service patrol method further includes the steps of: periodically traversing the service patrol item information, the server information, and the relationship between the two; according to the traversal result Update the relationship between the business inspection item and the server.
  • the traversal period may be set periodically according to requirements, such as traversing once a day. After traversing, you can scan the status of the server and whether the relationship between the service inspection item and the server is valid.
  • the step of updating the association relationship between the service inspection item and the server according to the traversal result includes:
  • the state of the server is maintained in the server configuration system.
  • the server is configured to be invalid in the server configuration system, all associations related to the server are deleted. If the server is not found, it means that the server (indicating that the server's IP does not exist) is retired.
  • the server configuration system records a server port and service process information
  • the service inspection item monitors the port and the service process information
  • the service inspection item is bound with a port or a service process, thereby obtaining a server and service tour.
  • the association between the check items is deleted when the server port is not matched with the port to which the service patrol is bound, or when the service process on the server does not match the service process bound to the service patrol item. The relationship between items.
  • the association relationship between the server and the corresponding service inspection item is automatically established.
  • the service patrol method further includes the steps of: setting a delete queue and adding a queue before the step of periodically traversing the service patrol item information, the server information, and the relationship between the two.
  • association relationship in (111) and (112) may be added to the deletion queue, the association relationship in (113) is added to the new queue, and then the association relationship in the deletion queue is deleted by traversing the deletion queue. By traversing the newly added queue, the associations in the newly added queue are added together.
  • the association relationship related to the server is moved into the deletion queue; if the port that the server port is bound to the service inspection item does not match or the service process and service inspection on the server are performed, If the service process is not matched, the association between the server and the corresponding service inspection item is moved to the deletion queue. If the server is added, the association between the new server and the corresponding service inspection item does not exist. Relationship, the association relationship between the newly added server and the corresponding service inspection item is moved into the new queue; then the deletion queue is traversed, and the association between the server in the deletion queue and the service inspection item is deleted. Relationship; traverse the new queue to increase the association between the server and the service inspection item in the new queue.
  • the foregoing service inspection method further includes the steps of: classifying the server and marking each type of server before the obtaining the change operation on the service inspection item. Specifically, the servers are classified according to similar properties or functions, and then the corresponding types of servers are assigned corresponding tags. Establish the association between the same type of server and service inspection items, that is, manage the servers by category.
  • Step 120 includes: obtaining a service process or port bound to the service inspection item according to the change operation, and searching for a corresponding server according to the service process or port, and updating an association relationship between the service inspection item and each type of server. , get the corresponding update results.
  • the update relationship between the server and the service inspection item is updated according to the change operation, that is, the service inspection item changes, and the relationship between the service inspection item and the mark of the type server is changed. For example, if the marking of a type of server is 01, the relationship between the marking 01 and the business inspection item is established. When the business inspection item is updated, the relationship between the marking 01 and the business inspection item is also updated.
  • the foregoing service inspection method further includes the following steps after the step of publishing the update result:
  • Step S210 obtaining a query request.
  • the relationship between the query service inspection item and the server can be obtained.
  • Step S220 View an association relationship between the updated service inspection item and the server according to the query request.
  • the relationship between the updated service inspection item and the server may be viewed from the service inspection database according to the query request.
  • the method before step S130, further includes the step of: storing the update result in the service inspection database. Stored in the business inspection database for subsequent queries.
  • the method further includes the step of: reporting the information detected by the inspection item to the visualization system and/or the early warning system.
  • a service inspection system includes an interaction module 110, a processing module 120, and a distribution module 130. among them:
  • the interaction module 110 is configured to acquire a change operation on the service inspection item. Specifically, the change operation of the service inspection item is obtained on the configuration interface of the service inspection. Among them, the business inspection item is the smallest business monitoring program unit, which is bound to a business process or an open port, and then is responsible for monitoring the service or the port.
  • the change operation can be a new operation, a modification operation, or a delete operation.
  • the interaction module 110 is located on the configuration system of the service inspection.
  • the processing module 120 is configured to obtain a service process or port bound to the service inspection item according to the change operation, and find a corresponding server according to the service process or port, and update an association relationship between the service inspection item and the server, and obtain The corresponding update results.
  • the association relationship refers to a mapping relationship between the service inspection item and the server.
  • the relationship between the service inspection item and the server can be represented by the association between the service inspection item identifier and the server identifier.
  • the service patrol item identifier is used to distinguish the identity of the service patrol item.
  • the server ID is used to distinguish the identity of the service patrol item.
  • a server or a service process is configured on the server.
  • the service inspection item is bound to a service process or port.
  • the corresponding server can be found according to the service process or port.
  • IP Internet Protocol, the protocol for interconnection between networks
  • the processing module 120 is located on the configuration system of the service inspection.
  • the publishing module 130 is configured to publish the update result.
  • the publishing module 130 is a Zookeeper publishing system.
  • Zookeeper is a distributed, open source distributed application coordination service, including a simple primitive set, is an important component of Hadoop and Hbase, mainly used to solve the consistency problem of application systems in distributed clusters. It provides data storage based on a directory node tree similar to a file system and maintains and monitors the state changes of stored data.
  • the ZooKeeper's script program contains the relationship between the service patrol item and the server. The running program searches for the corresponding server according to the server ID of the service patrol item identifier, and then publishes the service patrol item to the server.
  • the processing module 120 When the change operation is a new operation, the processing module 120 first registers the newly added service inspection item, obtains a service process or port bound to the newly added service inspection item, and finds the corresponding server according to the service process or port. Then, the relationship between the newly added service inspection item and the corresponding server is established, and the new service inspection item is released to the corresponding server through Zookeeper.
  • the processing module 120 acquires the service process or port bound to the newly added service inspection item, and finds the server of the corresponding class according to the service process or port, and updates and upgrades. After the relationship between the service inspection item and the server, the upgraded service inspection item is deployed to all the servers associated with it through Zookeeper, and the original service inspection item (ie, the monitoring program) is replaced.
  • the change operation is the delete operation
  • the service patrol item is deleted, and the processing module 120 obtains the service process or port bound to the newly added service patrol item, and finds the corresponding server according to the service process or port, and all the services are
  • the server associated with the patrol item performs an uninstall operation, so that the service patrol item no longer works.
  • the service inspection system includes an interaction module 110, a processing module 120, and a distribution module 130, and further includes a scanning module 140, a setting module 150, and a service inspection database 160. among them:
  • the scanning module 140 is configured to periodically traverse the service inspection item information, the server information, and the relationship between the two.
  • the service inspection item information includes the CPU of the device (Central) Processing Unit, central processing unit, hard disk, network status, monitoring service running status, etc., for example, Mysql (Associated Database Management System) connection number and other custom monitoring services.
  • the server information includes the service process information registered on the server, the port information, and the operation status of the server itself.
  • the service process information includes the name of the service process.
  • the port information includes an open port number.
  • the operation status of the server itself includes the status of running or decommissioning. Periodically, you can set the traversal period as needed, such as traversing once a day. After traversing, you can scan the status of the server and whether the relationship between the service inspection item and the server is valid.
  • the processing module 130 is further configured to update an association relationship between the service inspection item and the server according to the traversal result.
  • the processing module 130 is further configured to delete an association relationship related to the server if the server is invalid or the server is not found.
  • the state of the server is maintained in the server configuration system.
  • the server is configured to be invalid in the server configuration system, all associations related to the server are deleted. If the server is not found, it means that the server (indicating that the server's IP does not exist) is retired.
  • processing module 130 is further configured to: if the server port is not matched with the service patrol item, or the service process bound to the service patrol item does not match, the server and the corresponding service patrol are deleted. The relationship between the items.
  • the server configuration system records a server port and service process information
  • the service inspection item monitors the port and the service process information
  • the service inspection item is bound with a port or a service process, thereby obtaining a server and service tour.
  • the association between the check items is deleted when the server port is not matched with the port to which the service patrol is bound, or when the service process on the server does not match the service process bound to the service patrol item. The relationship between items.
  • processing module 130 is further configured to establish an association relationship between the newly added server and the corresponding service inspection item if the server is added and the association relationship between the newly added server and the corresponding service inspection item does not exist.
  • the association relationship between the server and the corresponding service inspection item is automatically established.
  • the setting module 150 is used to set a delete queue and a new queue.
  • the processing module 130 is further configured to: if the server is invalid or cannot find the server, move the association relationship related to the server into the delete queue, if the port that the server port is bound to the service inspection item does not match or the service process and service on the server The service process bound to the patrol item does not match. The association between the server and the corresponding service inspection item is moved to the deletion queue. If the server is added and the server does not have an association with the corresponding service inspection item. Relationship, the association relationship between the server and the corresponding service inspection item is moved into the new queue.
  • the scanning module 140 is further configured to traverse the deletion queue, and the processing module 130 is further configured to delete an association relationship between the server and the service inspection item in the deletion queue; the scanning module 140 is further configured to traverse the new queue, and the processing module The 130 is further configured to increase an association between the server and the service inspection item in the newly added queue.
  • the delete queue By traversing the delete queue, the associations in the delete queue are deleted together.
  • the associations in the newly added queues are increased together, which improves the operation efficiency.
  • the scanning module 140 and the setting module 150 are all disposed on the configuration system of the business inspection.
  • the service inspection database 160 is configured to store the relationship between the service inspection item information, the server information, and the service inspection item and the server before the interaction module 110 acquires the change operation of the service inspection item.
  • the processing module 130 updates the stored relationship between the service inspection item information, the server information, and the service inspection item and the server according to the change request.
  • the service inspection database 160 is further configured to store updated service inspection item information, server information, and an association relationship between the service inspection item and the server.
  • the switching module 110 is further configured to obtain a query request, and view an association relationship between the updated service inspection item and the server according to the query request. On the service inspection configuration page, you can obtain the association between the query service inspection item and the server.
  • the service inspection system includes the interaction module 110, the processing module 120, and the distribution module 130, the scan module 140 or the setup module 150 or the service inspection database 160 may be further included.
  • the service inspection system includes an interaction module 110, a processing module 120, and a distribution module 130, and further includes a classification module 170 and a marking module 180. among them:
  • Classification module 170 is used to classify servers. Classify servers by similar nature or function.
  • the tagging module 180 is used to tag each type of server. Assign the appropriate tags to the same type of server.
  • the classification module 170 and the marking module 180 are provided on the configuration system of the business inspection.
  • the processing module 130 is further configured to obtain a service process or port bound to the service inspection item according to the change operation, and find a corresponding server according to the service process or port, and update the service inspection item with each type of server. Correlation relationship, get the corresponding update results.
  • the update relationship between the server and the service inspection item is updated according to the change operation, that is, the service inspection item changes, and the relationship between the service inspection item and the mark of the type server is changed. For example, if the marking of a type of server is 01, the relationship between the marking 01 and the business inspection item is established. When the business inspection item is updated, the relationship between the marking 01 and the business inspection item is also updated.
  • the service inspection system may include an interaction module 110, a processing module 120 and a distribution module 130, a scanning module 140, a setting module 150, a service inspection database 160, a classification module 170, and a marking module 180.
  • the service inspection system After the service inspection system releases the update result, the service inspection system starts monitoring the service and reports the monitoring information to other systems, such as a visualization system or an early warning system.
  • the interaction module 110 and the processing module 120 are placed in the configuration system of the service inspection, and the interaction between the service inspection configuration system, the service inspection database, and the Zookeeper distribution system is described. As shown in Figure 6, the specific process is as follows:
  • New business inspection items including:
  • the newly created service inspection item is registered and saved in the business inspection database.
  • the service inspection database transmits the registration status to the configuration system of the business inspection.
  • the status of the registration success is returned to the configuration system of the service inspection for the user to understand.
  • the IP of the associated service inspection item to the specific server includes:
  • the server uses an IP identifier to establish an association relationship between the service inspection item and the IP of the server.
  • the release status describes the relationship between the service inspection item and the IP of the server, and the operation status of the server.
  • the service inspection item is a program for monitoring the service, which is used to monitor a certain service, that is, a task, and the ZooKeeper release system deploys the service inspection item to the associated server, that is, the task is released to a specific IP. .
  • the identifier of the feedback task is recorded in the service inspection database.
  • the service inspection configuration system periodically traverses the task status through the service inspection database.
  • the service inspection configuration system queries the service inspection database for the release status.
  • the service inspection method and system are configured to obtain the port or service process bound to the service inspection item according to the change operation, and automatically find the corresponding server according to the port or the service process, and update the relationship between the service inspection item and the server, and release the relationship. Update the results, automatically update the maintenance business, release the operation and maintenance personnel from the repetitive work, and reduce the labor input.
  • the change operation may be to add, modify, or delete the service, or the server is automatically renewed and automatically maintained; the service patrol item information, the server information, and the relationship between the two may be traversed periodically to further correct the possible existence.
  • the relationship between the service inspection item and the server is correct or missing; the association between the service inspection item and the server can be queried to facilitate the operation and maintenance personnel to understand.
  • the storage medium may be a magnetic disk, an optical disk, or a read-only storage memory (Read-Only) Memory, ROM) or Random Access Memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Mathematical Physics (AREA)
  • Software Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Debugging And Monitoring (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明涉及一种业务巡检方法和系统、计算机存储介质。该业务巡检方法包括以下步骤：获取对业务巡检项的变更操作；根据所述变更操作更新业务巡检项与服务器之间的关联关系，得到相应的更新结果；发布所述更新结果。上述业务巡检方法和系统、计算机存储介质，根据变更操作获取业务巡检项绑定的端口或业务进程，根据端口或业务进程自动查找到对应的服务器，更新业务巡检项与服务器之间的关联关系，发布更新结果，自动更新维护业务，将运维人员从重复性的劳动中释放出来，减少人工的投入。

Description

业务巡检方法和系统、计算机存储介质
本申请要求于2012年9月19日提交中国专利局、申请号为201210349218.9、发明名称为“业务巡检方法和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
【技术领域】
本发明涉及计算机网络技术，特别是涉及一种业务巡检方法和系统、计算机存储介质。
【背景技术】
随着计算机网络技术的发展，网络成为人们日常生活中不可或缺的一部分。在服务器上会提供各种各样的业务，以满足网络中不同的需求。业务是指完成某个功能的服务。业务存在服务器上需要运维人员进行维护，如业务部署到服务器上，运维人员会同时部署配套的监控程序，业务从某台服务器上卸载，运维人员会停止业务服务，同时停止配套的监控程序，某台服务器要退役时，运维人员需要停止所有的业务服务，同时停止所有的监控程序。
传统的业务维护主要是通过运维人员手动实现的。然而因业务与监控程序的种类繁多，每当有业务部署到服务器上，就需要人工来部署相配套的所有监控程序，重复劳动，且人工操作容易出现误操作；当业务从某台服务器上下线或服务器退役时，监控程序不能自动停止监控，需要人工干预；当监控程序自身进行升级时，需要人工替换原来版本的监控程序，此时很难获知监控程序已经部署在哪些服务器上，从而造成监控程序升级困难。
【发明内容】
基于此，有必要提供一种能自动维护业务的业务巡检方法，减少人工的投入。
一种业务巡检方法，包括以下步骤：
获取对业务巡检项的变更操作；
根据所述变更操作获取该业务巡检项绑定的业务进程或端口，根据该业务进程或端口查找到相应的服务器，更新业务巡检项与服务器之间的关联关系，得到相应的更新结果；
发布所述更新结果。
在其中一个实施例中，所述变更操作为新增操作、修改操作或删除操作。
在其中一个实施例中，在所述发布所述更新结果的步骤之后，还包括步骤：
定期遍历业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系；
根据遍历结果更新业务巡检项与服务器之间的关联关系。
在其中一个实施例中，所述根据遍历结果更新业务巡检项与服务器之间的关联关系的步骤包括：
若服务器无效或查找不到服务器，则删除与所述服务器相关的关联关系；
若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，则删除所述服务器与对应的业务巡检项之间的关联关系；
若新增服务器且不存在所述新增服务器与对应的业务巡检项的关联关系，则建立所述新增服务器与对应的业务巡检项之间的关联关系。
在其中一个实施例中，在所述定期遍历业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系的步骤之前，还包括步骤：
设置删除队列和新增队列；
若服务器无效或查找不到服务器，将与所述服务器相关的关联关系移入所述删除队列中；
若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，将所述服务器与对应的业务巡检项之间的关联关系移入所述删除队列中；
若新增服务器且不存在所述新增服务器与对应的业务巡检项的关联关系，则将所述新增服务器与对应的业务巡检项之间的关联关系移入所述新增队列中；
遍历所述删除队列，删除所述删除队列中的服务器与业务巡检项之间的关联关系；
遍历所述新增队列，增加所述新增队列中的服务器与业务巡检项之间的关联关系。
在其中一个实施例中，在所述获取对业务巡检项的变更操作的步骤之前，还包括步骤：
将业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系存入业务巡检数据库中。
在其中一个实施例中，在所述获取对业务巡检项的变更操作之前，还包括步骤：
将服务器进行分类，并标记每类服务器；
根据所述变更操作获取新增的业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应的服务器，更新所述业务巡检项与服务器之间的关联关系，得到相应的更新结果的步骤包括：
根据所述变更操作获取新增的业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应类的服务器，更新所述业务巡检项与每类服务器之间的关联关系，得到相应的更新结果。
在其中一个实施例中，在所述发布所述更新结果的步骤之后，还包括步骤：
获取查询请求；
根据所述查询请求查看所述更新后的业务巡检项与服务器之间的关联关系。
此外，还有必要提供一种能自动维护业务的业务巡检系统，减少人工的投入。
一种业务巡检系统，包括：
交互模块，用于获取对业务巡检项的变更操作；
处理模块，用于根据所述变更操作获取该业务巡检项绑定的业务进程或端口，根据该业务进程或端口查找到相应的服务器，更新所述业务巡检项与服务器之间的关联关系，得到相应的更新结果；
发布模块，用于发布所述更新结果。
在其中一个实施例中，所述变更操作为新增操作、修改操作或删除操作。
在其中一个实施例中，所述业务巡检系统还包括：
扫描模块，用于定期遍历业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系；
所述处理模块还用于根据遍历结果更新业务巡检项与服务器之间的关联关系。
在其中一个实施例中，所述处理模块还用于若服务器无效或查找不到服务器，则删除与所述服务器相关的关联关系，若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，则删除所述服务器与对应的业务巡检项之间的关联关系，以及若新增服务器且不存在所述新增服务器与对应的业务巡检项的关联关系，则建立所述新增服务器与对应的业务巡检项之间的关联关系。
在其中一个实施例中，所述业务巡检系统还包括：
设置模块，用于设置删除队列和新增队列；
所述处理模块还用于若服务器无效或查找不到服务器，将与所述服务器相关的关联关系移入所述删除队列中，若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，将所述服务器与对应的业务巡检项之间的关联关系移入所述删除队列中，以及若新增服务器且不存在所述新增服务器与对应的业务巡检项的关联关系，则将所述新增服务器与对应的业务巡检项之间的关联关系移入所述新增队列中；
所述扫描模块还用于遍历所述删除队列，所述处理模块还用于删除所述删除队列中的服务器与业务巡检项之间的关联关系；
所述扫描模块还用于遍历所述新增队列，所述处理模块还用于增加所述新增队列中的服务器与业务巡检项之间的关联关系。
在其中一个实施例中，所述业务巡检系统还包括：
业务巡检数据库，用于存储业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系。
在其中一个实施例中，所述业务巡检系统还包括：
分类模块，用于将服务器进行分类；
标记模块，用于标记每类服务器；
所述处理模块还用于根据所述变更操作获取新增的业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应类的服务器，更新所述业务巡检项与每类服务器之间的关联关系，得到相应的更新结果。
在其中一个实施例中，所述交换模块还用于获取查询请求，以及根据所述查询请求查看所述更新后的业务巡检项与服务器之间的关联关系。
此外，还有必要提供一种计算机存储介质。
一个或多个包含计算机可执行指令的计算机存储介质，所述计算机可执行指令用于执行一种业务巡检方法，所述方法包括以下步骤：
获取对业务巡检项的变更操作；
根据所述变更操作获取该业务巡检项绑定的业务进程或端口，根据该业务进程或端口查找到相应的服务器，更新业务巡检项与服务器之间的关联关系，得到相应的更新结果；
发布所述更新结果。
上述业务巡检方法和系统、计算机存储介质，根据变更操作获取业务巡检项绑定的端口或业务进程，根据端口或业务进程自动查找到对应的服务器，更新业务巡检项与服务器之间的关联关系，发布更新结果，自动更新维护业务，将运维人员从重复性的劳动中释放出来，减少人工的投入。
【附图说明】
图1为一个实施例中业务巡检方法的流程图；
图2为一个实施例中查询业务巡检项与服务器关联关系的流程图；
图3为一个实施例中业务巡检系统的内部结构示意图；
图4为另一个实施例中业务巡检系统的内部结构示意图；
图5为另一个实施例中业务巡检系统的内部结构示意图；
图6为业务巡检系统的工作时序图。
【具体实施方式】
下面结合具体的实施例及附图对业务巡检方法和系统的技术方案进行详细的描述，以使其更加清楚。
如图1所示，在一个实施例中，一种业务巡检方法，包括以下步骤：
步骤S110，获取对业务巡检项的变更操作。
具体的，在业务巡检的配置界面获取对业务巡检项的变更操作。其中，业务巡检项是最小的业务监控程序单元，它会绑定一个业务进程或者一个开放的端口，然后负责监控该业务进程或该端口。变更操作可为新增操作、修改操作或删除操作。
在一个实施例中，在步骤S110之前，还包括步骤：将业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系存入业务巡检数据库中。
具体的，业务巡检项信息包括设备的CPU（Central Processing Unit，中央处理器）、硬盘、网络状况、监控服务的运行状态等，例如，Mysql（关联数据库管理系统）的连接数等自定义的监控服务。服务器信息包括服务器上注册的业务进程信息、端口信息以及服务器本身的运营状态，业务进程信息包括业务进程名称，端口信息包括开放的端口号，服务器本身的运营状态包括运行中或已经退役等状态。业务巡检项与服务器之间的关联关系可通过业务巡检项标识与服务器标识进行关联体现。业务巡检项标识用于区分业务巡检项的身份唯一，服务器标识用于区分业务巡检项的身份唯一。
步骤S120，根据该变更操作获取该业务巡检项绑定的业务进程或端口，根据该业务进程或端口查找到相应的服务器，更新该业务巡检项与服务器之间的关联关系，得到相应的更新结果。
具体的，关联关系是指业务巡检项与服务器之间的映射关系。服务器上设有端口或业务进程，业务巡检项绑定了某业务进程或端口，根据该业务进程或端口可查找到对应的服务器。服务器采用IP（Internet Protocol，网络之间互连的协议）进行区分。
步骤S130，发布该更新结果。
具体的，可通过Zookeeper发布该更新结果到相应的服务器。其中，Zookeeper是一个分布式的、开放源代码的分布式应用程序协调服务，包含一个简单的原语集，是Hadoop和Hbase的重要组件，主要用来解决分布式集群中应用系统的一致性问题，它能提供基于类似于文件系统的目录节点树方式的数据存储，并能维护和监控存储的数据的状态变化。Zookeeper的脚本程序中包含业务巡检项与服务器之间的关联关系，通过运行脚本程序根据业务巡检项标识对应的服务器标识查找到相应的服务器，然后将业务巡检项发布到该服务器上。
当变更操作为新增操作时，首先注册该新增的业务巡检项，获取新增的业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应的服务器，然后建立新增的业务巡检项与相应的服务器之间的关联关系，再通过Zookeeper发布将新增的业务巡检项到相应的服务器。
当变更操作为修改操作，即当业务巡检项自身升级时，获取业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应的服务器，更新升级后的业务巡检项与服务器之间的关联关系，在通过Zookeeper把升级后的业务巡检项部署到与之关联的所有的服务器上，替换掉原来的业务巡检项（即监控程序）。
当变更操作为删除操作时，即删除业务巡检项，获取业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应的服务器，将所有与该业务巡检项关联的服务器执行卸载操作，使得该业务巡检项不再工作。
在一个实施例中，上述业务巡检方法，在所述发布所述更新结果的步骤之后，还包括步骤：定期遍历业务巡检项信息、服务器信息及两者之间的关联关系；根据遍历结果更新业务巡检项与服务器之间的关联关系。
具体的，定期可根据需要设定遍历的期限，如一天遍历一次等。遍历后，可扫描到服务器的状态以及业务巡检项与服务器之间的关联关系是否有效等。
在一个实施例中，该根据遍历结果更新业务巡检项与服务器之间的关联关系的步骤包括：
（111）若服务器无效或查找不到服务器，则删除与所述服务器相关的关联关系。
具体的，服务器的状态是在服务器配置系统中进行维护的，当服务器配置系统中将服务器配置为无效，则与该服务器相关的关联关系全部删除。若查找不到服务器是指该服务器（表示该服务器的IP不存在）退役。
（112）若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，则删除该服务器与对应的业务巡检项之间的关联关系。
具体的，在服务器配置系统中记录有某个服务器端口与业务进程信息，业务巡检项监控该端口与业务进程信息，因业务巡检项绑定有端口或业务进程，进而得到服务器与业务巡检项之间的关联关系，当服务器端口与业务巡检项绑定的端口之间不匹配时或服务器上业务进程与业务巡检项绑定的业务进程不匹配时，删除服务器与业务巡检项之间的关联关系。
（113）若新增服务器且不存在新增服务器与对应的业务巡检项的关联关系，则建立所述新增服务器与对应的业务巡检项之间的关联关系。
具体的，扫描中获取到新增了服务器，且没有扫描到新增的服务器与对应的业务巡检项的关联关系，则需自动建立服务器与对应的业务巡检项之间的关联关系。
在一个实施例中，上述业务巡检方法，在该定期遍历业务巡检项信息、服务器信息及两者之间的关联关系的步骤之前，还包括步骤：设置删除队列和新增队列。
进一步的，可将（111）和（112）中的关联关系加入删除队列中，将（113）中的关联关系加入新增队列中，然后通过遍历删除队列，将删除队列中的关联关系一起删除，通过遍历新增队列，将新增队列中的关联关系一起增加。
具体的，若服务器无效或查找不到服务器，将与该服务器相关的关联关系移入所述删除队列中；若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，将该服务器与对应的业务巡检项之间的关联关系移入所述删除队列中；若新增服务器且不存在新增服务器与对应的业务巡检项的关联关系，则将该新增服务器与对应的业务巡检项之间的关联关系移入所述新增队列中；然后遍历该删除队列，删除该删除队列中的服务器与业务巡检项之间的关联关系；遍历该新增队列，增加该新增队列中的服务器与业务巡检项之间的关联关系。
在一个实施例中，上述业务巡检方法，在该获取对业务巡检项的变更操作之前，还包括步骤：将服务器进行分类，并标记每类服务器。具体的，对服务器按照相似的性质或功能进行分类，然后对同一类服务器分配相应的标记。建立同一类服务器与业务巡检项之间的关联关系，即对服务器按分类进行管理。
步骤120包括：根据该变更操作获取该业务巡检项绑定的业务进程或端口，根据该业务进程或端口查找到相应的服务器，更新所述业务巡检项与每类服务器之间的关联关系，得到相应的更新结果。
具体的，根据变更操作更新的是一类服务器与业务巡检项之间的关联关系，即业务巡检项发生变化，该业务巡检项与一类服务器的标记之间的关联关系发生变化。例如一类服务器的标记为01，则标记01与业务巡检项之间建立关联关系，当业务巡检项更新时，标记01与业务巡检项之间的关联关系也更新。
在一个实施例中，如图2所示，上述业务巡检方法，在所述发布该更新结果的步骤之后，还包括步骤：
步骤S210，获取查询请求。
具体的，在业务巡检的配置界面可获取查询业务巡检项与服务器之间的关联关系。
步骤S220，根据该查询请求查看所述更新后的业务巡检项与服务器之间的关联关系。
具体的，根据查询请求可从业务巡检数据库中查看更新后的业务巡检项与服务器之间的关联关系。
进一步的，在一个实施例中，在步骤S130之前，还包括步骤：将更新结果存储在业务巡检数据库中。存储于业务巡检数据库中，以便后续查询。
进一步的，在一个实施例中，在步骤S130之后，还包括步骤：将巡检项检测的信息上报到可视化系统和/或预警系统。
如图3所示，在一个实施例中，一种业务巡检系统，包括交互模块110、处理模块120和发布模块130。其中：
交互模块110用于获取对业务巡检项的变更操作。具体的，在业务巡检的配置界面获取对业务巡检项的变更操作。其中，业务巡检项是最小的业务监控程序单元，它会绑定一个业务进程或者一个开放的端口，然后负责监控该业务进行或该端口。变更操作可为新增操作、修改操作或删除操作。本实施例中，交互模块110位于业务巡检的配置系统上。
处理模块120用于根据该变更操作获取该业务巡检项绑定的业务进程或端口，根据该业务进程或端口查找到相应的服务器，更新该业务巡检项与服务器之间的关联关系，得到相应的更新结果。具体的，关联关系是指业务巡检项与服务器之间的映射关系。业务巡检项与服务器之间的关联关系可通过业务巡检项标识与服务器标识进行关联体现。业务巡检项标识用于区分业务巡检项的身份唯一，服务器标识用于区分业务巡检项的身份唯一。服务器上设有端口或业务进程，业务巡检项绑定了某业务进程或端口，根据该业务进程或端口可查找到对应的服务器。
服务器采用IP（Internet Protocol，网络之间互连的协议）进行区分。本实施例中，处理模块120位于业务巡检的配置系统上。
发布模块130用于发布该更新结果。
具体的，可通过Zookeeper发布系统发布该更新结果。本实施例中，发布模块130为Zookeeper发布系统。其中，Zookeeper是一个分布式的、开放源代码的分布式应用程序协调服务，包含一个简单的原语集，是Hadoop和Hbase的重要组件，主要用来解决分布式集群中应用系统的一致性问题，它能提供基于类似于文件系统的目录节点树方式的数据存储，并能维护和监控存储的数据的状态变化。Zookeeper的脚本程序中包含业务巡检项与服务器之间的关联关系，通过运行脚本程序根据业务巡检项标识对应的服务器标识查找到相应的服务器，然后将业务巡检项发布到该服务器上。
当变更操作为新增操作时，处理模块120首先注册该新增的业务巡检项，获取新增的业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应的服务器，然后建立新增的业务巡检项与相应的服务器之间的关联关系，再通过Zookeeper发布将新增的业务巡检项到相应的服务器。
当变更操作为修改操作，即当业务巡检项自身升级时，处理模块120获取新增的业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应类的服务器，更新升级后的业务巡检项与服务器之间的关联关系，在通过Zookeeper把升级后的业务巡检项部署到与之关联的所有的服务器上，替换掉原来的业务巡检项（即监控程序）。
当变更操作为删除操作时，即删除业务巡检项，处理模块120获取新增的业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应的服务器，将所有与该业务巡检项关联的服务器执行卸载操作，使得该业务巡检项不再工作。
如图4所示，在一个实施例中，上述业务巡检系统，包括交互模块110、处理模块120和发布模块130，还包括扫描模块140、设置模块150、业务巡检数据库160。其中：
扫描模块140用于定期遍历业务巡检项信息、服务器信息及两者之间的关联关系。具体的，业务巡检项信息包括设备的CPU（Central Processing Unit，中央处理器）、硬盘、网络状况、监控服务的运行状态等，例如，Mysql（关联数据库管理系统）的连接数等自定义的监控服务。服务器信息包括服务器上注册的业务进程信息、端口信息以及服务器本身的运营状态，业务进程信息包括业务进程名称，端口信息包括开放的端口号，服务器本身的运营状态包括运行中或已经退役等状态。定期可根据需要设定遍历的期限，如一天遍历一次等。遍历后，可扫描到服务器的状态以及业务巡检项与服务器之间的关联关系是否有效等。
处理模块130还用于根据遍历结果更新业务巡检项与服务器之间的关联关系。
具体的，处理模块130还用于若服务器无效或查找不到服务器，则删除与该服务器相关的关联关系。
具体的，服务器的状态是在服务器配置系统中进行维护的，当服务器配置系统中将服务器配置为无效，则与该服务器相关的关联关系全部删除。若查找不到服务器是指该服务器（表示该服务器的IP不存在）退役。
进一步的，处理模块130还用于若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，则删除该服务器与对应的业务巡检项之间的关联关系。
具体的，在服务器配置系统中记录有某个服务器端口与业务进程信息，业务巡检项监控该端口与业务进程信息，因业务巡检项绑定有端口或业务进程，进而得到服务器与业务巡检项之间的关联关系，当服务器端口与业务巡检项绑定的端口之间不匹配时或服务器上业务进程与业务巡检项绑定的业务进程不匹配时，删除服务器与业务巡检项之间的关联关系。
进一步的，处理模块130还用于若新增服务器且不存在新增服务器与对应的业务巡检项的关联关系，则建立该新增服务器与对应的业务巡检项之间的关联关系。
具体的，扫描中获取到新增了服务器，且没有扫描到新增的服务器与对应的业务巡检项的关联关系，则需自动建立服务器与对应的业务巡检项之间的关联关系。
设置模块150用于设置删除队列和新增队列。
处理模块130还用于若服务器无效或查找不到服务器，将与该服务器相关的关联关系移入该删除队列中，若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，将该服务器与对应的业务巡检项之间的关联关系移入该删除队列中，以及若新增服务器且不存在服务器与对应的业务巡检项的关联关系，则将该服务器与对应的业务巡检项之间的关联关系移入该新增队列中。
扫描模块140还用于遍历所述删除队列，处理模块130还用于删除该删除队列中的服务器与业务巡检项之间的关联关系；扫描模块140还用于遍历该新增队列，处理模块130还用于增加该新增队列中的服务器与业务巡检项之间的关联关系。通过遍历删除队列，将删除队列中的关联关系一起删除，通过遍历新增队列，将新增队列中的关联关系一起增加，提高了操作效率。
扫描模块140、设置模块150均设在业务巡检的配置系统上。
业务巡检数据库160用于在交互模块110获取对业务巡检项的变更操作之前，存储业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系。处理模块130根据变更请求更新已存储的业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系。此外，业务巡检数据库160还用于存储更新后的业务巡检项信息、服务器信息以及业务巡检项与服务器之间的关联关系。
交换模块110还用于获取查询请求，以及根据该查询请求查看该更新后的业务巡检项与服务器之间的关联关系。在业务巡检的配置界面可获取查询业务巡检项与服务器之间的关联关系。
在其他实施例中，上述业务巡检系统包括交互模块110、处理模块120和发布模块130后，可仅还包括扫描模块140或设置模块150或业务巡检数据库160。
如图5所示，在一个实施例中，上述业务巡检系统，包括交互模块110、处理模块120和发布模块130，还包括分类模块170和标记模块180。其中：
分类模块170用于将服务器进行分类。对服务器按照相似的性质或功能进行分类。
标记模块180用于标记每类服务器。对同一类服务器分配相应的标记。
分类模块170和标记模块180设在业务巡检的配置系统上。
处理模块130还用于根据该变更操作获取该业务巡检项绑定的业务进程或端口，根据该业务进程或端口查找到相应的服务器，更新所述业务巡检项与每类服务器之间的关联关系，得到相应的更新结果。
具体的，根据变更操作更新的是一类服务器与业务巡检项之间的关联关系，即业务巡检项发生变化，该业务巡检项与一类服务器的标记之间的关联关系发生变化。例如一类服务器的标记为01，则标记01与业务巡检项之间建立关联关系，当业务巡检项更新时，标记01与业务巡检项之间的关联关系也更新。
在其他实施例中，业务巡检系统可包括交互模块110、处理模块120和发布模块130、扫描模块140、设置模块150、业务巡检数据库160、分类模块170和标记模块180。
上述业务巡检系统通过发布模块130发布更新结果后，开始监控业务，并将监控信息上报到其他系统，如可视化系统或预警系统等。
为了进一步说明上述业务巡检系统的工作过程，以交互模块110和处理模块120置于业务巡检的配置系统内，描述业务巡检的配置系统、业务巡检数据库和Zookeeper发布系统之间交互，如图6所示，具体过程如下：
新增业务巡检项，具体包括：
（201）在业务巡检的配置系统的配置界面获取新建业务巡检项。
（202）增加业务巡检项到业务巡检数据库。
（203）通过Zookeeper发布系统发布业务巡检项。
（204）返回注册状态到业务巡检数据库。
具体的，新建的业务巡检项注册并保存在业务巡检数据库中。
（205）业务巡检数据库将注册状态传递给业务巡检的配置系统。
具体的，将注册成功的状态返回给业务巡检的配置系统供用户了解。
关联业务巡检项到具体的服务器的IP，具体包括：
（206）在业务巡检的配置系统的界面关联业务巡检项到具体的服务器的IP。
具体的，服务器采用IP标识，建立业务巡检项与服务器的IP之间的关联关系。
（207）更改IP与业务巡检项的发布状态存储到业务巡检数据库。
具体的，建立了IP与业务巡检项的关联关系后，需将该关联关系存储在业务巡检数据库中。发布状态描述业务巡检项与服务器的IP之间的关联关系、服务器的运营状态等。
（208）通过Zookeeper发布系统发布任务到具体的IP。
具体的，业务巡检项是为监控业务的程序，用于监控某一业务，即为一件任务，Zookeeper发布系统将业务巡检项部署到关联的服务器上，即为发布任务到具体的IP。
（209）反馈任务ID（标识）到业务巡检数据库。
具体的，发布任务到具体的IP后，会反馈任务的标识记录在业务巡检数据库中。
（210）定期遍历任务状态。
具体的，业务巡检的配置系统通过业务巡检数据库定期遍历任务状态。
（211）业务巡检的配置系统向业务巡检数据库查询发布状态。
（212）业务巡检数据库反馈发布状态及具体的关联情况。
修改或删除业务巡检项，具体包括步骤（207）至（212）。
上述业务巡检方法和系统，根据变更操作获取业务巡检项绑定的端口或业务进程，根据端口或业务进程自动查找到对应的服务器，更新业务巡检项与服务器之间的关联关系，发布更新结果，自动更新维护业务，将运维人员从重复性的劳动中释放出来，减少人工的投入。
另外，变更操作可为新增、修改或删除业务，或服务器退役均自动更新，自动维护；通过定期遍历业务巡检项信息、服务器信息及两者之间的关联关系，可进一步修正可能存在不正确或漏掉的业务巡检项与服务器关联关系；能查询业务巡检项与服务器之间的关联关系，方便运维人员了解。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体（Read-Only Memory，ROM）或随机存储记忆体（Random Access Memory，RAM）等。
以上所述实施例仅表达了本发明的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对本发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干变形和改进，这些都属于本发明的保护范围。因此，本发明专利的保护范围应以所附权利要求为准。

Claims (17)

  1. 一种业务巡检方法，包括以下步骤：
    获取对业务巡检项的变更操作；
    根据所述变更操作获取该业务巡检项绑定的业务进程或端口，根据该业务进程或端口查找到相应的服务器，更新业务巡检项与服务器之间的关联关系，得到相应的更新结果；
    发布所述更新结果。
  2. 根据权利要求1所述的业务巡检方法，其特征在于，所述变更操作为新增操作、修改操作或删除操作。
  3. 根据权利要求1所述的业务巡检方法，其特征在于，在所述发布所述更新结果的步骤之后，还包括步骤：
    定期遍历业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系；
    根据遍历结果更新业务巡检项与服务器之间的关联关系。
  4. 根据权利要求3所述的业务巡检方法，其特征在于，所述根据遍历结果更新业务巡检项与服务器之间的关联关系的步骤包括：
    若服务器无效或查找不到服务器，则删除与所述服务器相关的关联关系；
    若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，则删除所述服务器与对应的业务巡检项之间的关联关系；
    若新增服务器且不存在所述新增服务器与对应的业务巡检项的关联关系，则建立所述新增服务器与对应的业务巡检项之间的关联关系。
  5. 根据权利要求4所述的业务巡检方法，其特征在于，在所述定期遍历业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系的步骤之前，还包括步骤：
    设置删除队列和新增队列；
    若服务器无效或查找不到服务器，将与所述服务器相关的关联关系移入所述删除队列中；
    若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，将所述服务器与对应的业务巡检项之间的关联关系移入所述删除队列中；
    若新增服务器且不存在所述新增服务器与对应的业务巡检项的关联关系，则将所述新增服务器与对应的业务巡检项之间的关联关系移入所述新增队列中；
    遍历所述删除队列，删除所述删除队列中的服务器与业务巡检项之间的关联关系；
    遍历所述新增队列，增加所述新增队列中的服务器与业务巡检项之间的关联关系。
  6. 根据权利要求1所述的业务巡检方法，其特征在于，在所述获取对业务巡检项的变更操作的步骤之前，还包括步骤：
    将业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系存入业务巡检数据库中。
  7. 根据权利要求1所述的业务巡检方法，其特征在于，在所述获取对业务巡检项的变更操作之前，还包括步骤：
    将服务器进行分类，并标记每类服务器；
    根据所述变更操作获取新增的业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应的服务器，更新所述业务巡检项与服务器之间的关联关系，得到相应的更新结果的步骤包括：
    根据所述变更操作获取新增的业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应类的服务器，更新所述业务巡检项与每类服务器之间的关联关系，得到相应的更新结果。
  8. 根据权利要求1所述的业务巡检方法，其特征在于，在所述发布所述更新结果的步骤之后，还包括步骤：
    获取查询请求；
    根据所述查询请求查看所述更新后的业务巡检项与服务器之间的关联关系。
  9. 一种业务巡检系统，其特征在于，包括：
    交互模块，用于获取对业务巡检项的变更操作；
    处理模块，用于根据所述变更操作获取该业务巡检项绑定的业务进程或端口，根据该业务进程或端口查找到相应的服务器，更新所述业务巡检项与服务器之间的关联关系，得到相应的更新结果；
    发布模块，用于发布所述更新结果。
  10. 根据权利要求9所述的业务巡检系统，其特征在于，所述变更操作为新增操作、修改操作或删除操作。
  11. 根据权利要求9所述的业务巡检系统，其特征在于，所述业务巡检系统还包括：
    扫描模块，用于定期遍历业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系；
    所述处理模块还用于根据遍历结果更新业务巡检项与服务器之间的关联关系。
  12. 根据权利要求11所述的业务巡检系统，其特征在于，所述处理模块还用于若服务器无效或查找不到服务器，则删除与所述服务器相关的关联关系，若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，则删除所述服务器与对应的业务巡检项之间的关联关系，以及若新增服务器且不存在所述新增服务器与对应的业务巡检项的关联关系，则建立所述新增服务器与对应的业务巡检项之间的关联关系。
  13. 根据权利要求12所述的业务巡检系统，其特征在于，所述业务巡检系统还包括：
    设置模块，用于设置删除队列和新增队列；
    所述处理模块还用于若服务器无效或查找不到服务器，将与所述服务器相关的关联关系移入所述删除队列中，若服务器端口与业务巡检项绑定的端口不匹配或服务器上业务进程与业务巡检项绑定的业务进程不匹配，将所述服务器与对应的业务巡检项之间的关联关系移入所述删除队列中，以及若新增服务器且不存在所述新增服务器与对应的业务巡检项的关联关系，则将所述新增服务器与对应的业务巡检项之间的关联关系移入所述新增队列中；
    所述扫描模块还用于遍历所述删除队列，所述处理模块还用于删除所述删除队列中的服务器与业务巡检项之间的关联关系；
    所述扫描模块还用于遍历所述新增队列，所述处理模块还用于增加所述新增队列中的服务器与业务巡检项之间的关联关系。
  14. 根据权利要求9所述的业务巡检系统，其特征在于，所述业务巡检系统还包括：
    业务巡检数据库，用于存储业务巡检项信息、服务器信息及业务巡检项与服务器之间的关联关系。
  15. 根据权利要求9所述的业务巡检系统，其特征在于，所述业务巡检系统还包括：
    分类模块，用于将服务器进行分类；
    标记模块，用于标记每类服务器；
    所述处理模块还用于根据所述变更操作获取新增的业务巡检项绑定的业务进程或端口，根据业务进程或端口查找到相应类的服务器，更新所述业务巡检项与每类服务器之间的关联关系，得到相应的更新结果。
  16. 根据权利要求9所述的业务巡检系统，其特征在于，所述交换模块还用于获取查询请求，以及根据所述查询请求查看所述更新后的业务巡检项与服务器之间的关联关系。
  17. 一个或多个包含计算机可执行指令的计算机存储介质，所述计算机可执行指令用于执行一种业务巡检方法，其特征在于，所述方法包括以下步骤：
    获取对业务巡检项的变更操作；
    根据所述变更操作获取该业务巡检项绑定的业务进程或端口，根据该业务进程或端口查找到相应的服务器，更新业务巡检项与服务器之间的关联关系，得到相应的更新结果；
    发布所述更新结果。
PCT/CN2013/083198 2012-09-19 2013-09-10 业务巡检方法和系统、计算机存储介质 WO2014044130A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
IN1263DEN2015 IN2015DN01263A (zh) 2012-09-19 2013-09-10
RU2014136486A RU2607991C2 (ru) 2012-09-19 2013-09-10 Способ и система технического осмотра и соответствующий им машиночитаемый носитель данных
KR1020147033870A KR101482651B1 (ko) 2012-09-19 2013-09-10 서비스 폴링 방법 및 시스템, 그리고 컴퓨터 기억 매체
CA 2866308 CA2866308A1 (en) 2012-09-19 2013-09-10 Method and system for service inspection and computer-readable storage medium thereof
US14/395,667 US20150081625A1 (en) 2012-09-19 2013-09-10 Service polling method and system, and computer storage medium
JP2015523409A JP5782585B1 (ja) 2012-09-19 2013-09-10 サービスインスペクションの方法及びシステム、及びそのコンピュータ読取可能な記憶媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210349218.9A CN103684900B (zh) 2012-09-19 2012-09-19 业务巡检方法和系统
CN201210349218.9 2012-09-19

Publications (1)

Publication Number Publication Date
WO2014044130A1 true WO2014044130A1 (zh) 2014-03-27

Family

ID=50321280

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/083198 WO2014044130A1 (zh) 2012-09-19 2013-09-10 业务巡检方法和系统、计算机存储介质

Country Status (9)

Country Link
US (1) US20150081625A1 (zh)
JP (1) JP5782585B1 (zh)
KR (1) KR101482651B1 (zh)
CN (1) CN103684900B (zh)
BR (1) BR112015003276A2 (zh)
CA (1) CA2866308A1 (zh)
IN (1) IN2015DN01263A (zh)
RU (1) RU2607991C2 (zh)
WO (1) WO2014044130A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104518903B (zh) * 2013-09-30 2019-01-08 腾讯科技（北京）有限公司 线上业务巡检方法、系统及装置
CN106911739B (zh) * 2015-12-23 2020-02-07 北京奇虎科技有限公司 一种信息分发方法及装置
CN107665119B (zh) * 2016-07-27 2020-06-26 北京金山云网络技术有限公司 一种分布式数据系统
CN106990992A (zh) * 2017-04-10 2017-07-28 深圳乐信软件技术有限公司 服务配置方法、装置、服务器及存储介质
CN109104302A (zh) * 2018-07-18 2018-12-28 杭州鑫合汇互联网金融服务有限公司 一种全链路追踪监控方法
CN109118607A (zh) * 2018-07-26 2019-01-01 郑州云海信息技术有限公司 设备巡检方法和巡检装置
CN111026702B (zh) * 2019-11-22 2023-05-16 安徽三实信息技术服务有限公司 一种windows或linux主机文件的快速巡检方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101043692A (zh) * 2007-04-30 2007-09-26 华为技术有限公司 巡检方法及巡检服务器
CN101216797A (zh) * 2008-01-11 2008-07-09 中国移动通信集团四川有限公司 大型数据中心it系统基础软硬件平台的深度巡检系统和方法
CN102521099A (zh) * 2011-11-24 2012-06-27 深圳市同洲视讯传媒有限公司 一种进程监控方法及进程监控系统
CN102591765A (zh) * 2011-12-31 2012-07-18 珠海市君天电子科技有限公司 一种进程自动管理系统

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7017162B2 (en) * 2001-07-10 2006-03-21 Microsoft Corporation Application program interface for network software platform
GB0306971D0 (en) * 2003-03-26 2003-04-30 British Telecomm Client server model
US7443867B2 (en) * 2003-08-15 2008-10-28 Nortel Networks Limited Method for performing network services
US20060271552A1 (en) * 2005-05-26 2006-11-30 Venture Capital & Consulting Group, Llc. Targeted delivery of content
CA2627073A1 (en) * 2005-10-24 2007-05-03 Accenture Global Services Gmbh Dynamic server consolidation and configuration
US7330882B2 (en) * 2005-12-28 2008-02-12 Matsushita Electric Works, Ltd. Systems and methods for discovering and interacting with services
JP4891722B2 (ja) * 2006-09-29 2012-03-07 株式会社日立製作所 検疫システムおよび検疫方法
US20080208806A1 (en) * 2007-02-28 2008-08-28 Microsoft Corporation Techniques for a web services data access layer
CN101217400B (zh) * 2007-12-29 2010-11-03 北京亿阳信通软件研究院有限公司 一种综合智能巡检方法和系统
US8775624B2 (en) * 2008-12-31 2014-07-08 Cerner Innovation, Inc. Load-balancing and technology sharing using Lempel-Ziv complexity to select optimal client-sets
CN102201934A (zh) * 2011-05-05 2011-09-28 中国联合网络通信集团有限公司 集中管理分布式自动测试巡检方法及系统
KR20130048094A (ko) * 2011-11-01 2013-05-09 한국전자통신연구원 콘텐츠 스트리밍 중계를 위한 노드 장치 및 그 방법
US9444884B2 (en) * 2011-12-31 2016-09-13 Level 3 Communications, Llc Load-aware load-balancing cluster without a central load balancer
CN102546796B (zh) * 2011-12-31 2014-08-06 重庆新媒农信科技有限公司 业务服务器数据更新处理系统及方法
US8955041B2 (en) * 2012-02-17 2015-02-10 Kabushiki Kaisha Toshiba Authentication collaboration system, ID provider device, and program

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101043692A (zh) * 2007-04-30 2007-09-26 华为技术有限公司 巡检方法及巡检服务器
CN101216797A (zh) * 2008-01-11 2008-07-09 中国移动通信集团四川有限公司 大型数据中心it系统基础软硬件平台的深度巡检系统和方法
CN102521099A (zh) * 2011-11-24 2012-06-27 深圳市同洲视讯传媒有限公司 一种进程监控方法及进程监控系统
CN102591765A (zh) * 2011-12-31 2012-07-18 珠海市君天电子科技有限公司 一种进程自动管理系统

Also Published As

Publication number Publication date
KR101482651B1 (ko) 2015-01-14
KR20140144313A (ko) 2014-12-18
CA2866308A1 (en) 2014-03-27
RU2014136486A (ru) 2016-11-10
US20150081625A1 (en) 2015-03-19
IN2015DN01263A (zh) 2015-07-03
CN103684900B (zh) 2018-03-16
CN103684900A (zh) 2014-03-26
JP5782585B1 (ja) 2015-09-24
BR112015003276A2 (pt) 2017-07-04
JP2015529893A (ja) 2015-10-08
RU2607991C2 (ru) 2017-01-11

Similar Documents

Publication Publication Date Title
WO2014044130A1 (zh) 业务巡检方法和系统、计算机存储介质
WO2018214320A1 (zh) 数据库业务逻辑监控方法、系统、及存储介质
WO2020224246A1 (zh) 基于区块链的数据管理方法、装置、设备和存储介质
WO2018103315A1 (zh) 监控数据的处理方法、装置、服务器及存储设备
WO2014044136A1 (zh) 基于分布式数据的并发处理方法、系统和计算机存储介质
WO2021012481A1 (zh) 系统性能监控方法、装置、设备及存储介质
WO2018058959A1 (zh) Sql审核方法、装置、服务器及存储设备
WO2018014580A1 (zh) 数据接口测试方法、装置、服务器和存储介质
WO2020233077A1 (zh) 系统服务的监控方法、装置、设备及存储介质
WO2020147385A1 (zh) 数据录入方法、装置、终端及计算机可读存储介质
WO2020253135A1 (zh) 自动化分析方法、用户设备、存储介质及装置
WO2020253125A1 (zh) 日志管理方法、装置、设备及存储介质
WO2018076841A1 (zh) 数据分享方法、装置、存储介质及服务器
WO2018201774A1 (zh) 数据审批方法、装置、设备和计算机可读存储介质
WO2021051492A1 (zh) 数据库服务节点切换方法、装置、设备及计算机存储介质
WO2016101441A1 (zh) 一种进行文件同步的方法及系统
WO2010123168A1 (ko) 데이터베이스 관리 방법 및 시스템
WO2010147362A2 (en) Widget activation and communication method
WO2020077832A1 (zh) 云桌面的访问方法、装置、设备及存储介质
WO2020177376A1 (zh) 数据的提取方法、装置、终端及计算机可读存储介质
WO2015144012A1 (zh) 一种软件开发事务的实现方法及电子设备
WO2009136740A2 (ko) OSGi 서비스 플랫폼에 원격으로 설치된 번들에 대한 바인딩 정보를 관리하는 방법 및 장치
WO2015024167A1 (zh) 一种处理用户报文的方法及转发面设备
WO2020220412A1 (zh) 基于零知识证明的公民隐私保护的方法、系统及存储介质
WO2020062658A1 (zh) 合同生成方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13839216

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2015523409

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2866308

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 14395667

Country of ref document: US

ENP Entry into the national phase

Ref document number: 20147033870

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2014136486

Country of ref document: RU

Kind code of ref document: A

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC OF 290715

122 Ep: pct application non-entry in european phase

Ref document number: 13839216

Country of ref document: EP

Kind code of ref document: A1

ENPC Correction to former announcement of entry into national phase, pct application did not enter into the national phase

Ref document number: 112015003276

Country of ref document: BR

Kind code of ref document: A2

Free format text: ANULADA A PUBLICACAO CODIGO 1.3 NA RPI NO 2426 DE 04/07/2017 POR TER SIDO INDEVIDA.

REG Reference to national code

Ref country code: BR

Ref legal event code: B01E

Ref document number: 112015003276

Country of ref document: BR

Kind code of ref document: A2

ENP Entry into the national phase

Ref document number: 112015003276

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20150212