zeek/scripts/policy/frameworks/cluster/controller
Christian Kreibich 7db8634c8b Add ClusterController::API::get_nodes_request/response event pair
This allows querying the status of Zeek nodes currently running in a cluster.
The controller relays the request to all instances and accumulates their
responses.

The response back to the client contains one Result record per instance
response, each of which carrying a ClusterController::Types::NodeState vector in
its $data member to convey the state of each node at that instance.

The NodeState record tracks the name of the node, its role in the controller (if
any), its role in the data cluster (if any), as well as PID and listening port,
if any.
2022-02-02 22:59:22 -08:00
..
__load__.zeek Docs/comment pass over the cluster controller framework 2022-01-03 00:31:03 -08:00
api.zeek Add ClusterController::API::get_nodes_request/response event pair 2022-02-02 22:59:22 -08:00
boot.zeek Docs/comment pass over the cluster controller framework 2022-01-03 00:31:03 -08:00
config.zeek Docs/comment pass over the cluster controller framework 2022-01-03 00:31:03 -08:00
log.zeek Docs/comment pass over the cluster controller framework 2022-01-03 00:31:03 -08:00
main.zeek Add ClusterController::API::get_nodes_request/response event pair 2022-02-02 22:59:22 -08:00
request.zeek Be more conservative with triggering request timeout events 2022-01-31 18:38:40 -08:00
types.zeek Add ClusterController::API::get_nodes_request/response event pair 2022-02-02 22:59:22 -08:00
util.zeek Docs/comment pass over the cluster controller framework 2022-01-03 00:31:03 -08:00