Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The lower level AnyLog functionality is enabled by a CLI, this can extend the hzn CLI.
AnyLog CLI includes dynamic help with links to help pages on GitHub - all of that can be available as an extension of the hzn CLI.

Additional information:

  • Nodes in the AnyLog network are configured such that commands and queries can be provided using REST. Therefore it is simple to integrate to existing and new applications without dependencies on existing infrastructure or setups.
  • Because of the decentralization nature of the AnyLog Network - any node or application can act as a point of access to the entire data set and the monitored status of all the member nodes.
  • AnyLog provides a web GUI that is optimized to the AnyLog API calls and data queries. It only requires a browser, can be installed on any node and can serve as a monitoring tool for network managers and as a training tool for administrators and developers showing how to interact with nodes in the network.

External Components

<Describe any new or changed interactions with components that are not the agent or the management hub.>

...

Ideally, the Anylog component should not need root-level access.    – That is correct. 

The Anylog component maintains its own P2P network. That is correct.

An AnyLog node can be deployed with and without security layers. If enabled - the AnyLog protocol is using keys and the blockchain to authenticate users and their permissions. The network can issue certificates to 3rd parties applications that authenticate the apps and users and determine their permissions.

APIs

<Describe and new/changed/deprecated APIs, including before and after snippets for clarity. Include which components or users will use the APIs.>

...

  • Each AnyLog instance includes a CLI option.
  • Data monitored can be generated by AnyLog existing functionalities. For example, disk space, memory usage, networking status, cpu state, processes running etc. are build-in functionalities that can be leverage on each node. Additional details are in the Monitor Nodes document.
  • Southbound Connectors are detailed in the Adding Data document (including services to present a node as a broker for pub-sub of a data,  to subscribe to a third party broker, to receive data via REST).
  • Northbound connectors are based on SQL and AnyLog CLI commands that are transferred to the network using REST. 

...