jimmy
05/15/2022, 7:04 PMLucas Rodriguez
05/16/2022, 2:27 PM4.14.0
(there have been several performance improvements since 3.5.1
).and when I use fleetctl the third fleet works. do you have any solution?1.
fleetctl
--> 3rd Fleet Server
2. fleetctl
--> load balancer --> 3rd Fleet Server
If you are doing (1) then I'd suggest you try with (2) to test that the request is really going through the load balancer.jimmy
05/16/2022, 6:32 PMfleetctl
--> 3rd Fleet ServerLucas Rodriguez
05/16/2022, 6:35 PMhow can i check thisSo if I understood correctly, your devices will connect to Fleet through the load balancer (via some defined URL). Have
fleetctl
use the same URL as the osquery hosts. To be sure that you are connecting to Fleet the same way as your devices.jimmy
05/16/2022, 6:41 PMLucas Rodriguez
05/16/2022, 6:49 PMfleetctl config get address
will return the URL it's using to connect to Fleet. Such URL should match the one your devices use to connect to Fleet.
E.g. in my development setup:
$ fleetctl config get address
default.address => <https://localhost:8080>
but how can i check this to be sure?A way to check this would be to run the third Fleet server in debug mode (
FLEET_LOGGING_DEBUG
var or --logging_debug
cli argument) and see if it's getting any requests (Fleet logs one line per request when --logging_debug
is set)jimmy
05/17/2022, 8:13 AMLucas Rodriguez
05/17/2022, 11:50 AMfleetctl
address with:
fleetctl config set --address https://$LOAD_BALANCER_IP:$LOAD_BALANCER_PORT
jimmy
05/17/2022, 7:24 PMLucas Rodriguez
05/17/2022, 7:26 PMi did this but sadly it still doesn't get queries from the load balancerWhat do you mean by this?
This command is only configuringfleetctl config set --address https://$LOAD_BALANCER_IP:$LOAD_BALANCER_PORT
fleetctl
to connect to Fleet via the load balancer.jimmy
05/17/2022, 8:29 PMLucas Rodriguez
05/17/2022, 9:41 PMfleetctl
via the load balancer to be able to troubleshoot.