CN107528751B - A kind of system and its management method of dynamic distribution Zabbix monitoring data - Google Patents

A kind of system and its management method of dynamic distribution Zabbix monitoring data Download PDF

Info

Publication number
CN107528751B
CN107528751B CN201710920092.9A CN201710920092A CN107528751B CN 107528751 B CN107528751 B CN 107528751B CN 201710920092 A CN201710920092 A CN 201710920092A CN 107528751 B CN107528751 B CN 107528751B
Authority
CN
China
Prior art keywords
zabbix
server
host
agent
node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201710920092.9A
Other languages
Chinese (zh)
Other versions
CN107528751A (en
Inventor
金友兵
段秀勇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nanjing thahai Mdt InfoTech Ltd
Nanjing Zhuo Shengyun Mdt InfoTech Ltd
Original Assignee
Nanjing Thahai Mdt Infotech Ltd
Nanjing Zhuo Shengyun Mdt Infotech Ltd
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 Nanjing Thahai Mdt Infotech Ltd, Nanjing Zhuo Shengyun Mdt Infotech Ltd filed Critical Nanjing Thahai Mdt Infotech Ltd
Priority to CN201710920092.9A priority Critical patent/CN107528751B/en
Publication of CN107528751A publication Critical patent/CN107528751A/en
Application granted granted Critical
Publication of CN107528751B publication Critical patent/CN107528751B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/12Network monitoring probes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04Network management architectures or arrangements
    • H04L41/046Network management architectures or arrangements comprising network management agents or mobile agents therefor
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention discloses a kind of systems of dynamic distribution Zabbix monitoring data, including management node and service node, each node is connect by cable with interchanger, and Zabbix Server information database service module and workflow management module are provided in the management node.The step of management method of monitoring data system as above are as follows: (1) management node and all service nodes first passes through cable and connect with interchanger;(2) Zabbix Server information database service module and workflow management module are disposed in management node, and monitoring data distribution is dynamically controlled by workflow management module;(3) Zabbix Server container mirror image, Zabbix Server deployment module are disposed on the Server node in service node;(4) Zabbix Agent container mirror image, Zabbix Agent deployment module are all disposed on the Server node and Agent node in service node.The place that the present invention can need to send to all Zabbix Agent container dynamic adjustment monitoring datas, has reached the quick collection and management of cluster monitoring data.

Description

A kind of system and its management method of dynamic distribution Zabbix monitoring data
Technical field
The invention belongs to computer application field, in particular to the system of a kind of dynamic distribution Zabbix monitoring data and its Management method.
Background technique
Monitoring is an important aspect in current computer systems.With the increase of calculation scale, cluster application service It quicklys increase, the state for how monitoring some node in cluster becomes extremely important.Zabbix is mentioning based on WEB interface For distributed system monitoring and the enterprise level solution of network monitoring function.
Zabbix is generally made of 2 parts, Zabbix Server and Zabbix Agent.Zabbix Agent needs to pacify On monitored target machine, it is mainly completed to hardware information or memory related with operating system, the information such as CPU It collects.Zabbix Server obtains monitoring data from Zabbix Agent, and saves these data, is then opened up by Web The operation such as show, alarm and analyze.In view of the high availability of monitoring system and the flexibility of system scale, a Zabbix Agent can be sent in monitoring data to multiple Zabbix Server servers, as long as Zabbix Agent can pass through network Zabbix Server is accessed.Method is the IP address column that Server is specified in the configuration file of Zabbix Agent Table or host list of file names determine that Agent is sent to monitoring data on those Zabbix Server servers.Such as In Linux server, in configuration file/etc/zabbix/zabbix_agentd.conf of Zabbix Agent, there is a line Server=host1, host2, host3 record.The record indicates the Server node that needs are sent, host1, host2, Host3 is the IP address or host name of Server node.
Currently as the containerization technique that Docker is representative is fast-developing, Zabbix system is disposed based on container technique And operation, it can obviously simplify the deployment of Zabbix system and use difficulty.It, can be with especially after Zabbix Server containerization Fast implement the deployment of multiple Zabbix Server, it might even be possible to according to the scale of cluster server and loading condition automatically and It is dynamic to increase Zabbix Server number.But when Zabbix Server variation, how Zabbix Agent knows The situation of change of road Zabbix Server, appropriate is sent to monitoring data on different Zabbix Server, this becomes One important technical problem.The IP of node (being host here) where Zabbix Server container especially after containerization The IP address of address and container itself is not identical.When Zabbix Agent container with Zabbix Server container not same On a host node, the address that Server is recorded in configuration file, with needing the host IP using Zabbix Server Location is just known in this way and monitoring data is sent on that host;But work as Zabbix Agent container and Zabbix Server container is on the same host node, and at this moment if using host address, the judgement of Docker network is the machine number According to will not be forwarded in the container of Zabbix Server, cause the machine Zabbix Server container that can not obtain the machine in this way The data that Zabbix Agent container is sent.So Zabbix Agent container and Zabbix Server container are in the same place On host node, the address that Server is recorded in configuration file needs the container IP address using Zabbix Server.
In view of the above problems as can be seen that after containerization Zabbix monitoring system, Zabbix Agent configuration complexities increase Add, the variation dynamic according to Zabbix Server, which distributes Zabbix monitoring data, becomes relatively difficult.
Summary of the invention
Goal of the invention: aiming at the problems existing in the prior art, the present invention provides a kind of Zabbix Agent foundation The situation of change of Zabbix Server dynamically associates Zabbix Server service, and can judge automatically is using Zabbix The practical host IP address of Server or the IP address of container itself realize a kind of dynamic distribution Zabbix monitoring number According to system and its management method.
Technical solution: in order to solve the above technical problems, a kind of dynamic distribution Zabbix monitoring data provided by the invention System, including management node and service node, each node are connect with interchanger by cable, are provided in the management node Zabbix Server information database service module and workflow management module.
Further, the service node includes Server node and Agent node again, is arranged on the Server node There are Zabbix Server container, Zabbix Server deployment module, Zabbix Agent container and Zabbix Agent deployment Module is provided with Zabbix Agent container and Zabbix Agent deployment module on the Agent node.
A kind of management method of dynamic distribution Zabbix monitoring data system as described above,
(1) management node and all service nodes first passes through cable and connect with interchanger;
(2) Zabbix Server information database service module and workflow management module are disposed in management node, are passed through Workflow management module dynamically controls monitoring data distribution;
(3) Zabbix Server container mirror image, Zabbix Server are disposed on the Server node in service node Deployment module;
(4) all disposed on the Server node and Agent node in service node Zabbix Agent container mirror image, Zabbix Agent deployment module.
Further, steps are as follows for the specific management method of the workflow management module in the step (2):
(2.1) Zabbix Server and Zabbix Agent host list conduct are specified by user or upper layer application The input of workflow management module, this list can dynamic changes at any time;
(2.2) according to above-mentioned (2.1) list traversal Zabbix Server host;
(2.3) Zabbix Server host is logged in respectively;
(2.4) Zabbix Server deployment module is called on each Zabbix Server host;
(2.5) according to above-mentioned (2.1) list traversal Zabbix Agent host;
(2.6) Zabbix Agent host is logged in respectively;
(2.7) Zabbix Agent deployment module is called on each Zabbix Agent host;
(2.8) realize that monitoring data is correctly sent to all Zabbix Server and serviced by Zabbix Agent container In, user can access the http service that Zabbix Server is provided by browser and be monitored management to group system.
Further, the calling Zabbix Server deployment module operating procedure in the step (2.4) is as follows:
(2.4.1) enters Zabbix Server deployment module;
(2.4.2) if Zabbix Server container has existed, disposing process terminates;
(2.4.3) is based on Zabbix Server mirror image and creates container;
(2.4.4) obtains the IP address of this host and the implicit IP address of Zabbix Server container;
(2.4.5) sends two IP address and is saved into Zabbix Server information database service.
Further, the calling Zabbix Agent deployment module operating procedure in the step (2.7) is as follows:
(2.7.1) enters Zabbix Agent deployment module, accesses Zabbix Server information database service, then Enter step (2.7.2);
(2.7.2) obtains the IP address list of all Zabbix Server containers and the IP of Zabbix Server host Address list, subsequently into step (2.7.3);
(2.7.3) obtains the IP address of this host, subsequently into step (2.7.4);
(2.7.4) judge this host IP address whether in Zabbix Server host IP address list, if (2.7.5) is entered step, if not entering step (2.7.6);
(2.7.5) in Zabbix Server host IP address list, the data for replacing this host IP address are pair The data of the machine Zabbix Server container IP address are answered, and enter step (2.7.7);
(2.7.6) directlys adopt former Zabbix Server host IP address list, and enters step (2.7.7);
(2.7.7) forms final Zabbix Server Host List, is ServerList;
(2.7.8) judges that Zabbix Agent container whether there is, if there is (2.7.9) is entered step, if do not deposited Entering step (2.7.12);
(2.7.9) obtains the Host List saved last time from container, is OldServerList;
(2.7.10) if this Host List ServerList is identical as last time Host List OldServerList, This process terminates, and (2.7.11) is entered step if not identical
(2.7.11) deletes original Zabbix Agent container
(2.7.12) is based on Zabbix Agent mirror image and creates container, the Zabbix obtained in step (2.7.7) Server Host List ServerList is transmitted in container in a manner of environmental variance,
(2.7.13) is recorded in the value of Host List environmental variance replacement Zabbix Agent configuration file in a reservoir Zabbix Server Host List content
(2.7.14) starts Zabbix Agent process service in container, starts collection and delivery monitoring data.
Compared with the prior art, the advantages of the present invention are as follows:
Main advantages of the present invention are to work as Zabbix after containerization Zabbix Server and Zabbix Agent When Server container deployment scenario changes, all Zabbix Agent container dynamic adjustment monitoring datas can be needed to send out The place sent has reached the quick collection and management of cluster monitoring data.
Detailed description of the invention
Fig. 1 is the structural diagram of the present invention;
Fig. 2 is the flow chart of workflow management module in management node in the present invention;
Fig. 3 is the flow chart of Zabbix Server deployment module on service node in the present invention;
Fig. 4 is the flow chart of Zabbix Agent deployment module on service node in the present invention.
Specific embodiment
With reference to the accompanying drawings and detailed description, the present invention is furture elucidated:
Need to monitor those hosts 1. first planning, to dispose Zabbix Agent service on it;Secondly it plans Good Zabbix Server is deployed on those hosts, so as to preservation and management monitoring data;Management node has finally been specified to use In whole workflow management, structure as shown in Fig. 1 is ultimately formed.
2. providing the service of Zabbix Server information database and workflow management module in specified management node. Zabbix Server information database service saves the IP address of each Zabbix Server container and the IP of place host Address.Workflow management module realizes the dynamic distribution control of entire Zabbix system.
3. needing to place Zabbix Server deployment module and relevant appearance for the Server node of service node Device mirror image can create Zabbix Server container in this way.
4. for the Agent node of service node, this be monitoring system state in need host node, need to put Zabbix Agent deployment module and relevant container mirror image are set, Zabbix Agent container can be created in this way.If clothes The Server node of business node itself also needs to monitor, then be also required to place Zabbix Agent deployment module in the node, And relevant container mirror image.
5. workflow management module is shown in attached drawing 2 for Zabbix Server operating process, are as follows:
A) specify Zabbix Server and Zabbix Agent host list as process by user or upper layer application Dynamic change can occur at any time for management module input, this list.
B) the Zabbix Server list in traversal input.
C) for host name each in list, log on to the Zabbix Server host, execute Zabbix Server Deployment module.Zabbix Server deployment module itself process is seen below.
D) the Zabbix Agent list in traversal input.
E) for host name each in list, log on to the Zabbix Agent host, execute the portion Zabbix Agent Affix one's name to module.Zabbix Agent deployment module itself process is seen below.
F) after the completion of all traversals, system can correctly obtain monitoring data, and itself be mentioned by Zabbix Server The http of confession is serviced, inquiry, management and the analysis being monitored.
6. attached drawing 3 is shown in the operating process of Zabbix Server deployment module on service node, are as follows:
If a) Zabbix Server container exists, deployment module terminates
B) Zabbix Server container is created using bridge network mode.
C) IP address of this host and container is obtained.As under linux, host IP address can be used " hostname-i " is obtained.Container IP address can be obtained using docker inspect Container Name.
D) two IP address are sent in Zabbix Server information database service module, by Zabbix Server Information database service module saves.Preserving type can be saved using common database, or even use text file Format is ok.
7. attached drawing 4 is shown in the operating process of Zabbix Agent deployment module on service node, are as follows:
A) Zabbix Server information database service is accessed, the host node IP address of Zabbix Server is obtained List and container IP address list.Such as hostiplist=host1_ip, host2_ip, host3_ip etc., Containeriplist=container1_ip, container2_ip, container3_ip etc..
B) IP address of this host, for example selfip are obtained.
If c) IP address of this host node is not in Zabbix Server host IP address list, i.e., Selfip is not in hostiplist, then the server-side list that Zabbix Agent needs to send monitoring data is ServerList=hostiplist.
If d) IP address of this host node is in Zabbix Server host IP address list, i.e. selfip In hostiplist, then the IP address of the host is the IP address of corresponding container in replacement list, service is then generated Hold list ServerList.Such as assume selfip=host2_ip, then final ServerList=host1_ip, container2_ip,host3_ip。
If e) having existed Zabbix Agent container, from container the list of reading service end.This list is to save In the environmental variance or configuration file of container, last time server-side list OldServerList is formed.If there is no Zabbix Agent container, then on leap in below step g.
If f) the server-side list OldServerList of last registration is identical as current ServerList, illustrate Zabbix Agent container is normal and does not change, and deployment module terminates.Hold if it is not the same, deleting original Zabbix Agent Device.
ServerList value is transmitted when g) creating new Zabbix Agent container, but creating into the environmental variance of container, For example ZBX_SERVER_HOST environmental variance.
H) Zabbix Agent configuration file, generally/etc/zabbix/zabbix_ are updated in a reservoir Agentd.conf file.The record of Server=xxx in this document, the value of environmental variance, i.e. Server=ZBX_ are replaced with The value of SERVER_HOST.
I) start Zabbix Agent process service in a reservoir, form the correct distribution of monitoring data.

Claims (2)

1. a kind of management method of dynamic distribution Zabbix monitoring data, it is characterised in that:
(1) management node and all service nodes first passes through cable and connect with interchanger;
(2) Zabbix Server information database service module and workflow management module are disposed in management node, pass through process Management module dynamically controls monitoring data distribution;
(3) Zabbix Server container mirror image, Zabbix Server deployment are disposed on the Server node in service node Module;
(4) Zabbix Agent container mirror image, Zabbix are all disposed on the Server node and Agent node in service node Agent deployment module;
Steps are as follows for the specific management method of workflow management module in the step (2):
(2.1) specify Zabbix Server and Zabbix Agent host list as process by user or upper layer application Management module input, this list dynamic change at any time;
(2.2) according to above-mentioned (2.1) list traversal Zabbix Server host;
(2.3) Zabbix Server host is logged in respectively;
(2.4) Zabbix Server deployment module is called on each Zabbix Server host;
(2.5) according to above-mentioned (2.1) list traversal Zabbix Agent host;
(2.6) Zabbix Agent host is logged in respectively;
(2.7) Zabbix Agent deployment module is called on each Zabbix Agent host;
(2.8) it realizes that Zabbix Agent container is correctly sent to monitoring data in all Zabbix Server services, uses Family can access the http service that Zabbix Server is provided by browser and be monitored management to group system;
Calling Zabbix Agent deployment module operating procedure in the step (2.7) is as follows:
(2.7.1) enters Zabbix Agent deployment module, accesses Zabbix Server information database service, subsequently into Step (2.7.2);
(2.7.2) obtains the IP address list of all Zabbix Server containers and the IP address of Zabbix Server host List, subsequently into step (2.7.3);
(2.7.3) obtains the IP address of this host, subsequently into step (2.7.4);
(2.7.4) judges this host IP address whether in Zabbix Server host IP address list, if entering Step (2.7.5), if not entering step (2.7.6);
(2.7.5) replaces the data of this host IP address in Zabbix Server host IP address list to correspond to this The data of machine Zabbix Server container IP address, and enter step (2.7.7);
(2.7.6) directlys adopt former Zabbix Server host IP address list, and enters step (2.7.7);
(2.7.7) forms final Zabbix Server Host List, is ServerList;
(2.7.8) judges that Zabbix Agent container whether there is, if there is entering step (2.7.9), if there is no into Enter step (2.7.12);
(2.7.9) obtains the Host List saved last time from container, is OldServerList;
(2.7.10) if this Host List ServerList is identical as last time Host List OldServerList, this stream Journey terminates, and (2.7.11) is entered step if not identical;
(2.7.11) deletes original Zabbix Agent container;
(2.7.12) is based on Zabbix Agent mirror image and creates container, the Zabbix Server master obtained in step (2.7.7) Machine list ServerList is transmitted in container in a manner of environmental variance;
(2.7.13) is in a reservoir with recording in the value of Host List environmental variance replacement Zabbix Agent configuration file Zabbix Server Host List content;
(2.7.14) starts Zabbix Agent process service in container, starts collection and delivery monitoring data.
2. a kind of management method of dynamic distribution Zabbix monitoring data according to claim 1, it is characterised in that: described Calling Zabbix Server deployment module operating procedure in step (2.4) is as follows:
(2.4.1) enters Zabbix Server deployment module;
(2.4.2) if Zabbix Server container has existed, disposing process terminates;
(2.4.3) is based on Zabbix Server mirror image and creates container;
(2.4.4) obtains the IP address of this host and the implicit IP address of Zabbix Server container;
(2.4.5) sends two IP address and is saved into Zabbix Server information database service.
CN201710920092.9A 2017-09-30 2017-09-30 A kind of system and its management method of dynamic distribution Zabbix monitoring data Active CN107528751B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710920092.9A CN107528751B (en) 2017-09-30 2017-09-30 A kind of system and its management method of dynamic distribution Zabbix monitoring data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710920092.9A CN107528751B (en) 2017-09-30 2017-09-30 A kind of system and its management method of dynamic distribution Zabbix monitoring data

Publications (2)

Publication Number Publication Date
CN107528751A CN107528751A (en) 2017-12-29
CN107528751B true CN107528751B (en) 2019-10-29

Family

ID=60684358

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710920092.9A Active CN107528751B (en) 2017-09-30 2017-09-30 A kind of system and its management method of dynamic distribution Zabbix monitoring data

Country Status (1)

Country Link
CN (1) CN107528751B (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108363653B (en) * 2018-02-07 2020-08-07 平安科技(深圳)有限公司 Deployment method and device of monitoring system, computer equipment and storage medium
CN110380879A (en) * 2018-04-12 2019-10-25 上海宝信软件股份有限公司 Track traffic synthetic monitoring dispositions method and system based on docker
CN110048888A (en) * 2019-04-16 2019-07-23 深圳市致宸信息科技有限公司 A kind of method based on zabbix monitoring alarm, server, equipment and storage medium
CN111641521B (en) * 2020-05-11 2023-05-09 紫光云技术有限公司 Method for deploying big data clusters on cloud based on Ambari
CN111625418A (en) * 2020-05-12 2020-09-04 深圳前海微众银行股份有限公司 Process monitoring method and device
CN112804291B (en) * 2020-12-21 2022-07-12 武汉虹旭信息技术有限责任公司 Remote equipment auditing method, device and system

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105357296A (en) * 2015-10-30 2016-02-24 河海大学 Elastic caching system based on Docker cloud platform
CN105530145A (en) * 2015-12-23 2016-04-27 中国电子科技集团公司第三十研究所 Agentless equipment monitoring network based on ZABBIX framework, networking method and monitoring method
CN106789284A (en) * 2016-12-28 2017-05-31 郑州云海信息技术有限公司 A kind of monitoring system and method based on Zabbix and Docker
CN106776212A (en) * 2016-12-09 2017-05-31 中电科华云信息技术有限公司 The supervisory systems and method of container clustered deploy(ment) multi-process application
CN107124297A (en) * 2017-03-31 2017-09-01 广州九乐维信息科技有限公司 SNMP method for discovering network topology and device based on zabbix
CN107179977A (en) * 2017-05-10 2017-09-19 杭州铭师堂教育科技发展有限公司 Database Full-automatic monitoring system based on mpm models

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105357296A (en) * 2015-10-30 2016-02-24 河海大学 Elastic caching system based on Docker cloud platform
CN105530145A (en) * 2015-12-23 2016-04-27 中国电子科技集团公司第三十研究所 Agentless equipment monitoring network based on ZABBIX framework, networking method and monitoring method
CN106776212A (en) * 2016-12-09 2017-05-31 中电科华云信息技术有限公司 The supervisory systems and method of container clustered deploy(ment) multi-process application
CN106789284A (en) * 2016-12-28 2017-05-31 郑州云海信息技术有限公司 A kind of monitoring system and method based on Zabbix and Docker
CN107124297A (en) * 2017-03-31 2017-09-01 广州九乐维信息科技有限公司 SNMP method for discovering network topology and device based on zabbix
CN107179977A (en) * 2017-05-10 2017-09-19 杭州铭师堂教育科技发展有限公司 Database Full-automatic monitoring system based on mpm models

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Data Protection for Cross-Border Live Migration in Multi-cloud Environment.;Yuichi Hashi et al.;《2016 Fourth International Symposium on Computing and Networking (CANDAR)》;20161125;第1-5页 *
IT Infrastructure-Monitoring Tools.;Josune Hernantes et al.;《IEEE Software 》;20150831;第32卷(第4期);第1-6页 *
用 Zabbix 和 Docker 搭建监控平台.;字节流的博客;《https://blog.smoker.cc/docker/zabbix-in-docker.html》;20160122;第1-8页 *

Also Published As

Publication number Publication date
CN107528751A (en) 2017-12-29

Similar Documents

Publication Publication Date Title
CN107528751B (en) A kind of system and its management method of dynamic distribution Zabbix monitoring data
US10868861B2 (en) Techniques for network replication
CN103475682B (en) File transfer method and file transfer equipment
CN102298365B (en) Method for automatically identifying and managing spaceflight measurement and control earth station device change
US20140143602A1 (en) Techniques for evaluating and managing cloud networks
US9697066B2 (en) Method for processing data quality exceptions in a data processing system
CN110427299A (en) Log processing method, relevant device and the system of micro services system application
CN103631699A (en) Log management system and method for log monitoring, acquiring and querying
CN106933548B (en) Global information obtaining, processing and updating method, device and system
US20130198333A1 (en) Method and device for recording and reproducing web operation
CN107786551B (en) Method for accessing intranet server and device for controlling access to intranet server
CN104901845B (en) Domain name WHOIS automatizations of service test system and method
CN110113188A (en) Across subdomain communication O&M method, total O&M server and medium
CN113835836B (en) System, method, computer device and medium for dynamic publishing container service
JPWO2006117832A1 (en) In-service system check processing apparatus, method and program thereof
CN107704369A (en) A kind of recording method of Operation Log, electronic equipment, storage medium, system
CN109474698A (en) Access request labeling method, device, equipment and storage medium
CN111538754A (en) Data collection management system, method, device, equipment and storage medium
CN113438126B (en) Distributed online test system applied to block chain domain name system
CN101364224A (en) Information management system and method
JP2004038232A (en) Information management device, information processor and method for controlling them, information management system and program
CN115474234B (en) 5G core network element log collection method, computer equipment and storage medium
KR20180104919A (en) Apparatus for supporting automatic interworking between smart factory devices and method for the same
CN108055329A (en) Content distribution method, content distribution system and storage medium
JP4672055B2 (en) Information processing apparatus, information processing method, and computer program

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20190826

Address after: 211103 A510, 33 Donglu Road, Dongshan Street, Jiangning District, Nanjing City, Jiangsu Province

Applicant after: Nanjing Zhuo Shengyun Mdt InfoTech Ltd

Applicant after: Nanjing thahai Mdt InfoTech Ltd

Address before: 211103 A510, 33 Donglu Road, Dongshan Street, Jiangning District, Nanjing City, Jiangsu Province

Applicant before: Nanjing Zhuo Shengyun Mdt InfoTech Ltd

GR01 Patent grant
GR01 Patent grant