From 6c487ddd16e3fde1f7e3219a7e5cacd361f57d97 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=90=B4=E6=99=9F=20Wu=20Sheng?= Date: Wed, 5 Aug 2020 20:34:15 +0800 Subject: [PATCH] Remove unnecessary document. (#5240) --- docs/en/guides/README.md | 2 -- docs/en/guides/inventory-extension.md | 31 --------------------------- 2 files changed, 33 deletions(-) delete mode 100644 docs/en/guides/inventory-extension.md diff --git a/docs/en/guides/README.md b/docs/en/guides/README.md index dbe428bec9..38003452c0 100755 --- a/docs/en/guides/README.md +++ b/docs/en/guides/README.md @@ -114,8 +114,6 @@ haven't provide. You need to add a new receiver rather than choosing [existed receiver](../setup/backend/backend-receivers.md). At that moment, you most likely need to add a new source and scope. This document will teach you how to do. -- [Backend Inventory entity extension](inventory-extension.md). If you want to extend SkyWalking inventory entities, and -want to push upstream back to our Apache OSS repo, please read these principles. ### UI developer Our UI is constituted by static pages and web container. diff --git a/docs/en/guides/inventory-extension.md b/docs/en/guides/inventory-extension.md deleted file mode 100644 index 3a78bba362..0000000000 --- a/docs/en/guides/inventory-extension.md +++ /dev/null @@ -1,31 +0,0 @@ -# Backend Inventory Entity Extension -SkyWalking includes four inventory entities. -- Service Inventory -- Service Instance Inventory -- Endpoint Inventory -- Network Address Inventory - -All metrics, topology, trace and alarm are related to these entity IDs. - -For understanding the **Service**, **Service Instance** and **Endpoint** concepts, -please read [Project Overview](../concepts-and-designs/overview.md#why-use-skywalking). - -For **Network Address Inventory**, it represents all network address, in IP:port, hostname, domain name -formats, which are detected by language agents or other probes. - -## Extension -Right now, only **Service Inventory** extension is already supported in backend core. -Service provides field `properties` in Json format, which is usually used for specific service -rather than normal business services, such as Database, Cache, MQ, etc. - -For keeping code consistent and friendly in query and visualization, the Json properties -need to follow the rules. - -### Database -1. NodeType == **Database(1)** -1. Json properties include following keys. - - `database`. Database name, such as MySQL, PostgreSQL - - `db.type`. Database type, such as sql db, redis db. - - `db.instance`. Database instance name. - -