Questions:
What is the mechanism and commands within bro for scheduling the periodic transfer of conn.logs, protocol logs and notice.logs from each of a number of remotely distributed bro deployments to a central postgresql application running in a cloud service like AWS using a outbound port 443 connection?
Can the scheduling of the bro log files be based on time and/or a specific log volume threshold being reached?