网络依赖图

ACME 的网络依赖图

数据库设置

以下是用于在 Neo4j 中创建 ACME 网络依赖图的完整 Cypher 脚本。这个简单的脚本是我们将稍后进行分析的数据集的完整设置。

// Create CRM
CREATE (crm1:Application {
			ip:'10.10.32.1',
			host:'CRM-APPLICATION',
			type: 'APPLICATION',
			system: 'CRM'
		})

// Create ERP
CREATE (erp1:Application {
			ip:'10.10.33.1',
			host:'ERP-APPLICATION',
			type: 'APPLICATION',
			system: 'ERP'
		})

// Create Data Warehouse
CREATE (datawarehouse1:Application {
			ip:'10.10.34.1',
			host:'DATA-WAREHOUSE',
			type: 'DATABASE',
			system: 'DW'
		})

// Create Public Website 1
CREATE (Internet1:Internet {
			ip:'10.10.35.1',
			host:'global.acme.com',
			type: "APPLICATION",
			system: "INTERNET"
		})

// Create Public Website 2
CREATE (Internet2:Internet {
			ip:'10.10.35.2',
			host:'support.acme.com',
			type: "APPLICATION",
			system: "INTERNET"
		})

// Create Public Website 3
CREATE (Internet3:Internet {
			ip:'10.10.35.3',
			host:'shop.acme.com',
			type: "APPLICATION",
			system: "INTERNET"
		})

// Create Public Website 4
CREATE (Internet4:Internet {
			ip:'10.10.35.4',
			host:'training.acme.com',
			type: "APPLICATION",
			system: "INTERNET"
		})

// Create Public Website 5
CREATE (Internet5:Internet {
			ip:'10.10.35.1',
			host:'partners.acme.com',
			type: "APPLICATION",
			system: "INTERNET"
		})

// Create Internal Website 1
CREATE (Intranet1:Intranet {
			ip:'10.10.35.2',
			host:'events.acme.net',
			type: "APPLICATION",
			system: "INTRANET"
		})

// Create Internal Website 2
CREATE (Intranet2:Intranet {
			ip:'10.10.35.3',
			host:'intranet.acme.net',
			type: "APPLICATION",
			system: "INTRANET"
		})

// Create Internal Website 3
CREATE (Intranet3:Intranet {
			ip:'10.10.35.4',
			host:'humanresources.acme.net',
			type: "APPLICATION",
			system: "INTRANET"
		})

// Create Webserver VM 1
CREATE (webservervm1:VirtualMachine {
			ip:'10.10.35.5',
			host:'WEBSERVER-1',
			type: "WEB SERVER",
			system: "VIRTUAL MACHINE"
		})

// Create Webserver VM 2
CREATE (webservervm2:VirtualMachine {
			ip:'10.10.35.6',
			host:'WEBSERVER-2',
			type: "WEB SERVER",
			system: "VIRTUAL MACHINE"
		})

// Create Database VM 1
CREATE (customerdatabase1:VirtualMachine {
			ip:'10.10.35.7',
			host:'CUSTOMER-DB-1',
			type: "DATABASE SERVER",
			system: "VIRTUAL MACHINE"
		})

// Create Database VM 2
CREATE (customerdatabase2:VirtualMachine {
			ip:'10.10.35.8',
			host:'CUSTOMER-DB-2',
			type: "DATABASE SERVER",
			system: "VIRTUAL MACHINE"
		})

// Create Database VM 3
CREATE (databasevm3:VirtualMachine {
			ip:'10.10.35.9',
			host:'ERP-DB',
			type: "DATABASE SERVER",
			system: "VIRTUAL MACHINE"
		})

// Create Database VM 4
CREATE (dwdatabase:VirtualMachine {
			ip:'10.10.35.10',
			host:'DW-DATABASE',
			type: "DATABASE SERVER",
			system: "VIRTUAL MACHINE"
		})

// Create Hardware 1
CREATE (hardware1:Hardware {
			ip:'10.10.35.11',
			host:'HARDWARE-SERVER-1',
			type: "HARDWARE SERVER",
			system: "PHYSICAL INFRASTRUCTURE"
		})

// Create Hardware 2
CREATE (hardware2:Hardware {
			ip:'10.10.35.12',
			host:'HARDWARE-SERVER-2',
			type: "HARDWARE SERVER",
			system: "PHYSICAL INFRASTRUCTURE"
		})

// Create Hardware 3
CREATE (hardware3:Hardware {
			ip:'10.10.35.13',
			host:'HARDWARE-SERVER-3',
			type: "HARDWARE SERVER",
			system: "PHYSICAL INFRASTRUCTURE"
		})

// Create SAN 1
CREATE (san1:Hardware {
			ip:'10.10.35.14',
			host:'SAN',
			type: "STORAGE AREA NETWORK",
			system: "PHYSICAL INFRASTRUCTURE"
		})

// Connect CRM to Database VM 1
CREATE (crm1)-[:DEPENDS_ON]->(customerdatabase1)

// Connect Public Websites 1-3 to Database VM 1
CREATE 	(Internet1)-[:DEPENDS_ON]->(customerdatabase1),
	   	(Internet2)-[:DEPENDS_ON]->(customerdatabase1),
	   	(Internet3)-[:DEPENDS_ON]->(customerdatabase1)

// Connect Database VM 1 to Hardware 1
CREATE 	(customerdatabase1)-[:DEPENDS_ON]->(hardware1)

// Connect Hardware 1 to SAN 1
CREATE 	(hardware1)-[:DEPENDS_ON]->(san1)

// Connect Public Websites 1-3 to Webserver VM 1
CREATE 	(webservervm1)<-[:DEPENDS_ON]-(Internet1),
		(webservervm1)<-[:DEPENDS_ON]-(Internet2),
		(webservervm1)<-[:DEPENDS_ON]-(Internet3)

// Connect Internal Websites 1-3 to Webserver VM 1
CREATE 	(webservervm1)<-[:DEPENDS_ON]-(Intranet1),
		(webservervm1)<-[:DEPENDS_ON]-(Intranet2),
		(webservervm1)<-[:DEPENDS_ON]-(Intranet3)

// Connect Webserver VM 1 to Hardware 2
CREATE 	(webservervm1)-[:DEPENDS_ON]->(hardware2)

// Connect Hardware 2 to SAN 1
CREATE 	(hardware2)-[:DEPENDS_ON]->(san1)

// Connect Webserver VM 2 to Hardware 2
CREATE 	(webservervm2)-[:DEPENDS_ON]->(hardware2)

// Connect Public Websites 4-6 to Webserver VM 2
CREATE 	(webservervm2)<-[:DEPENDS_ON]-(Internet4),
		(webservervm2)<-[:DEPENDS_ON]-(Internet5)

// Connect Database VM 2 to Hardware 2
CREATE 	(hardware2)<-[:DEPENDS_ON]-(customerdatabase2)

// Connect Public Websites 4-5 to Database VM 2
CREATE 	(Internet4)-[:DEPENDS_ON]->(customerdatabase2),
	   	(Internet5)-[:DEPENDS_ON]->(customerdatabase2)

// Connect Hardware 3 to SAN 1
CREATE 	(hardware3)-[:DEPENDS_ON]->(san1)

// Connect Database VM 3 to Hardware 3
CREATE 	(hardware3)<-[:DEPENDS_ON]-(databasevm3)

// Connect ERP 1 to Database VM 3
CREATE 	(erp1)-[:DEPENDS_ON]->(databasevm3)

// Connect Database VM 4 to Hardware 3
CREATE 	(hardware3)<-[:DEPENDS_ON]-(dwdatabase)

// Connect Data Warehouse 1 to Database VM 4
CREATE 	(datawarehouse1)-[:DEPENDS_ON]->(dwdatabase)

RETURN *

ACME 的网络资产清单

以下查询生成一个数据表，快速概述 ACME 的网络基础设施。

MATCH 	(n)
RETURN 	labels(n)[0] as type,
		count(*) as count,
		collect(n.host) as names

查找所有公共网站的直接依赖项

以下查询通过数据模型查找 ACME 所有面向公共互联网的业务Web应用程序。

MATCH 		(website)-[:DEPENDS_ON]->(downstream)
WHERE		website.system = "INTERNET"
RETURN 		website.host as Host,
			collect(downstream.host) as Dependencies
ORDER BY 	Host

查找所有内部网站的直接依赖项

以下查询通过数据模型查找 ACME 所有内部网络的业务网站。

MATCH 		(website)-[:DEPENDS_ON]->(downstream)
WHERE		website.system = "INTRANET"
RETURN 		website.host as Host,
			collect(downstream.host) as Dependencies
ORDER BY 	Host

查找最受依赖的组件

以下查询查找 ACME 网络基础设施中依赖程度最高的组件。不出所料，最受依赖的组件是 SAN（存储区域网络）。

MATCH 		(n)<-[:DEPENDS_ON*]-(dependent)
RETURN 		n.host as Host,
			count(DISTINCT dependent) AS Dependents
ORDER BY 	Dependents DESC
LIMIT 		1

查找业务关键组件的依赖链：CRM

以下查询查找 ACME 的 CRM 应用程序的依赖组件路径（从左到右）。如果 ACME 的 CRM（客户关系管理）应用程序出现故障，将对其业务造成重大影响。如果 CRM 主机名右侧的任何组件发生故障，CRM 应用程序将无法运行。

MATCH 		(dependency)<-[:DEPENDS_ON*]-(dependent)
WITH 		dependency, count(DISTINCT dependent) AS Dependents
ORDER BY 	Dependents DESC
LIMIT		1
WITH		dependency
MATCH 		p=(resource)-[:DEPENDS_ON*]->(dependency)
WHERE		resource.system = "CRM"
RETURN		"[" + head(nodes(p)).host + "]" +
			reduce(s = "", n in tail(nodes(p)) | s + " -> " + "[" + n.host + "]") as Chain

查找业务关键组件的依赖链：ERP

以下查询查找 ACME 的 ERP（企业资源规划）应用程序的依赖组件路径（从左到右）。ERP 应用程序代表了一系列业务资源，专门用于支持 ACME 正在进行的业务活动，包括财务和供应链管理。如果 ACME 的 ERP 应用程序出现故障，将对其业务造成重大影响。如果 ERP 主机名右侧的任何组件发生故障，ERP 应用程序将无法运行。此故障将导致收入受损，因为 ACME 的业务依赖于此系统来开展业务。

MATCH 		(dependency)<-[:DEPENDS_ON*]-(dependent)
WITH 		dependency, count(DISTINCT dependent) AS Dependents
ORDER BY 	Dependents DESC
LIMIT		1
WITH		dependency
MATCH 		p=(resource)-[:DEPENDS_ON*]->(dependency)
WHERE		resource.system = "ERP"
RETURN		"[" + head(nodes(p)).host + "]" +
			reduce(s = "", n in tail(nodes(p)) | s + " -> " + "[" + n.host + "]") as Chain

查找业务关键组件的依赖链：数据仓库

以下查询查找 ACME 的 DW（数据仓库）应用程序的依赖组件路径（从左到右）。DW 应用程序代表了一系列业务智能资源，专门用于支持 ACME 的时间敏感型分析流程。如果 ACME 的 DW 应用程序出现故障，将从技术方面对 ACME 的业务运营造成重大影响。如果 DW 主机名右侧的任何组件发生故障，DW 应用程序将无法运行。此故障将导致面向公众的网站（如电子商务应用程序）无法反映 ACME 的 ERP 应用程序的最新可用数据。

MATCH 		(dependency)<-[:DEPENDS_ON*]-(dependent)
WITH 		dependency, count(DISTINCT dependent) AS Dependents
ORDER BY 	Dependents DESC
LIMIT		1
WITH		dependency
MATCH 		p=(resource)-[:DEPENDS_ON*]->(dependency)
WHERE		resource.system = "DW"
RETURN		"[" + head(nodes(p)).host + "]" +
			reduce(s = "", n in tail(nodes(p)) | s + " -> " + "[" + n.host + "]") as Chain

查找移除网络组件（硬件服务器）的影响

以下查询查找依赖于 ACME 的 HARDWARE-SERVER-3 的应用程序。如果网络管理员计划对服务器进行干预，他必须知道哪些应用程序会受到影响。这样他就可以提前通知应用程序用户。

MATCH (application:Application)-[:DEPENDS_ON*]->(server)
WHERE       server.host = "HARDWARE-SERVER-3"
RETURN  application.type as Type,
        application.host as Host

此页面有帮助吗？

GraphGists