...

• Data that needs to be monitored will be persistent in a local database.
• The schemas that are used to store the data are shared among all participating nodes (nodes deployed by Open Horizon).
• Each node is extended to include a rule engine that can act on data and status events.
• Each node is extended to include southbound connectors (to ingest data) and northbound connectors (to share data).
• Each node can collect and monitor the target metrics.

The query and monitoring functionality

Nodes members of the network, as well as applications connected to nodes in the network are able to view all the monitored data as if it is a single and unified collection of data.

Practically, nodes view a virtual database based on the schema published on the shared metadata layer and can issue queries to the data as if the data is centralized.

In addition, a network can be configured such that nodes would push data to an aggregator node periodically, or based on events.

The query or monitoring can view an entire network as a single machine, or dynamically partition the network to satisfy the user view by criteria's determined by the users (and represented in the shared metadata policies).
For example: by locations, by type of software deployed, by owners etc.

User Experience

<Describe which user roles are related to the problem AND the solution, e.g. admin, deployer, node owner, etc. If you need to define a new role in your design, make that very clear. Remember this is about what a user is thinking when interacting with the system before and after this design change. This section is not about a UI, it's more abstract than that. This section should explain all the aspects of the proposed feature that will surface to users.>

...