RPuth
11/06/2018, 6:20 PMzwass
Martijn Bakkes
11/06/2018, 6:46 PMzwass
Martijn Bakkes
11/06/2018, 6:48 PMzwass
Martijn Bakkes
11/06/2018, 6:55 PMRPuth
11/06/2018, 6:55 PMzwass
logger_tls_period
.Martijn Bakkes
11/06/2018, 7:04 PMzwass
logger_tls_period: 1
? This is likely to unnecessarily increase the load on the Fleet server. Do you have your Fleet server horizontally scaled? What does the CPU usage look like on the Fleet server? What does the CPU usage look like on the MySQL server?RPuth
11/06/2018, 7:17 PMzwass
RPuth
11/06/2018, 7:28 PMSELECT * FROM file WHERE directory="/usr/bin/"
to return an exact count of 457 per server.
Now, running the query towards a single target returned a beautiful result of 457 within a 1 second time frame.
Although, when running against 100 hosts it returned the desired total count of 45700 but over 84 seconds (logger_tls_period was within the range of 1 -> 10 during that test)zwass
Martijn Bakkes
11/06/2018, 7:33 PMzwass
Martijn Bakkes
11/06/2018, 7:37 PMzwass
What was the interval you set on the query?
Martijn Bakkes
11/06/2018, 7:38 PMzwass
RPuth
11/06/2018, 7:42 PMzwass
RPuth
11/06/2018, 7:50 PMzwass
config_tls_refresh: 60
. This means that it may take up to 60s for a host to receive a new query you schedule.RPuth
11/06/2018, 8:10 PMzwass
logger_tls_period
in the 60s range. To simulate this on the smaller number of hosts you might try 1-5s.