Christian Kreibich 83c60fd8ac Management framework: tune request timeout granularity and interval ... When the controller relays requests to agents, we want agents to time out more quickly than the corresponding controller requests. This allows agents to respond with more meaningful errors, while the controller's timeout acts mostly as a last resort to ensure a response to the client actually happens. This dials down the table_expire_interval to 2 seconds in both agent and controller, for more predictable timeout behavior. It also dials the agent-side request expiration interval down to 5 seconds, compared to the agent's 10 seconds. We may have to revisit this to allow custom expiration intervals per request/response message type.		2022-05-31 12:55:21 -07:00
..
agent	Management framework: tune request timeout granularity and interval	2022-05-31 12:55:21 -07:00
controller	Management framework: tune request timeout granularity and interval	2022-05-31 12:55:21 -07:00
node	Management framework: set defaults for log rotation and persistent state	2022-05-26 12:55:10 -07:00
__load__.zeek	Management framework: set defaults for log rotation and persistent state	2022-05-26 12:55:10 -07:00
config.zeek	Management framework: add spool and state directory config settings	2022-05-25 13:56:23 -07:00
log.zeek	Management framework: move role variable from logging into framework-wide config	2022-05-25 13:56:23 -07:00
persistence.zeek	Management framework: set defaults for log rotation and persistent state	2022-05-26 12:55:10 -07:00
request.zeek	Management framework: tune request timeout granularity and interval	2022-05-31 12:55:21 -07:00
types.zeek	Management framework: comment and layouting tweaks, no functional change	2022-05-25 13:56:23 -07:00
util.zeek	Reorg of the cluster controller to new "Management framework" layout	2022-02-09 18:09:42 -08:00