Hi,
For a variety of reasons, it's a good thing to document the schema that
the code uses. So, I wrote a program which deduces the schema from the
created database ;-) - which also lets me verify whether the program is
behaving the way I want it to. Below is the output from this schema
documentation program when run against a database I created from two
machines at my house. There may be some types of relationships which
are not visible in my home configuration. The program can only note
relationship types that it observes in the database.
I believe that this information will prove especially interesting to Tom
Flaherty and Kenny Bastani and possibly Pamela Howell. It also supports
a blog post I am writing.
In the node section, the indented names are attributes found in those
types of nodes followed by how many instances of that attribute that
were seen.
I haven't looked at the output in detail, but it looks basically
reasonable. The Drone class is a subclass of the SystemNode class.
The JSON_ attributes are all the result of discovery actions. The
discovery results all produce JSON, and each type of discovery adds its
own new attribute.
There are 8 types of nodes
NODE CMAclass: (8)
domain (8)
name (8)
NODE Drone: (2)
JSON_OS (2)
JSON___LinkDiscovery (1)
JSON_arpcache (2)
JSON_cpu (2)
JSON_netconfig (2)
JSON_tcpclients (2)
JSON_tcplisteners (1)
designation (2)
domain (2)
iso8601 (2)
port (2)
primary_ip_addr (2)
reason (2)
roles (2)
startaddr (2)
status (2)
statustime (2)
time_create_iso8601 (2)
time_create_ms (2)
time_status_iso8601 (2)
time_status_ms (2)
NODE HbRing: (1)
domain (1)
name (1)
ournexttype (1)
ourreltype (1)
ringtype (1)
time_create_iso8601 (1)
time_create_ms (1)
NODE IPaddrNode: (12)
cidrmask (12)
domain (12)
ipaddr (12)
time_create_iso8601 (12)
time_create_ms (12)
NODE IPtcpportNode: (28)
domain (28)
ipaddr (28)
ipport (28)
port (28)
protocol (28)
time_create_iso8601 (28)
time_create_ms (28)
NODE NICNode: (8)
ConnectsToHost (1)
ConnectsToInterface (1)
PORTNUM (1)
PortDescription (1)
domain (8)
ifname (8)
macaddr (8)
sourceMAC (1)
time_create_iso8601 (8)
time_create_ms (8)
NODE ProcessNode: (16)
JSON_procinfo (16)
argv (16)
cwd (16)
domain (16)
gid (16)
host (16)
pathname (16)
processname (16)
roles (16)
time_create_iso8601 (16)
time_create_ms (16)
uid (16)
NODE SystemNode: (1)
ChassisId (1)
ManagementAddress (1)
SystemDescription (1)
SystemName (1)
designation (1)
domain (1)
roles (1)
time_create_iso8601 (1)
time_create_ms (1)
Relationships:
IS_A: CMAclass->CMAclass
IS_A: Drone->CMAclass
IS_A: HbRing->CMAclass
IS_A: IPaddrNode->CMAclass
IS_A: IPtcpportNode->CMAclass
IS_A: NICNode->CMAclass
IS_A: ProcessNode->CMAclass
IS_A: SystemNode->CMAclass
RingMember_The_One_Ring: HbRing->Drone
RingNext_The_One_Ring: Drone->Drone
baseip: IPtcpportNode->IPaddrNode
hosting: Drone->ProcessNode
ipowner: NICNode->IPaddrNode
nicowner: Drone->NICNode
nicowner: SystemNode->NICNode
tcpclient: ProcessNode->IPtcpportNode
tcpservice: ProcessNode->IPtcpportNode
wiredto: NICNode->NICNode
76 nodes, 175 relationships
--
Alan Robertson <[email protected]> - @OSSAlanR
"Openness is the foundation and preservative of friendship... Let me claim
from you at all times your undisguised opinions." - William Wilberforce
_______________________________________________
Assimilation mailing list - Discovery-Driven Monitoring
[email protected]
http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation
http://assimmon.org/
