I've put up a work in progress architecture document with a breakdown of PeerTab node components and functions that elaborates on this diagram.
But here is the high level overview of a minimal (edge) PeerTab node:
- Various event sources (which could be local or remote, for example the node could be a syslog-ng server receiving a variety of syslog-style events or a netflow collector using flow-tools) are saved locally on the filesystem so that
- Based on filtering criteria a subset of this information is added as events in a local database on the node which can be
- Searched locally via the cli or remotely via the JXTA network via other nodes that are part of the same network