...
- Data that needs to be monitored will be persistent in a local database - nodes collect and monitor the target metrics.
- The schemas that are used to store the data are shared among all participating nodes.
- Each node is extended to include a rule engine that can act on data and status events.
- Using the rule engine - thresholds are monitored to trigger alerts when needed.
- Using the rule engine - old data is removed and archived to avoid storage overload.
- Each node is extended to include southbound connectors (to ingest data) and northbound connectors (to share data).
KubeArmor running on the edge node provides visibility and protection for all the processes, files, or network operations in the containers as well as those running directly on the host. See KubeArmor integration repo. In this feature, KubeArmor (when present) can transmit (define how) collected metrics to the AnyLog code running on the Node.
NS1 will provide an API endpoint and help define when how, and what information will be transmitted from the Nodes over AnyLog into NS1 for Node and network visibility and analytics.
The query and monitoring functionality
...