Hi Team When I am trying to change Osquery option like distr

Question

Hi Team When I am trying to change Osquery option like distributed interval from Fleet GUI I was expecting the new config will be read by the osquery endpoints whenever those reach out to fleet But I am observing all the Osquery endpoints re enrolling making the fleet go down few times before everything settles down Is this the expected behaviour is there a way I could avoid the re enroll and downtime

Kathy Satterlee · Answer

Hi < Anoop K V> What version of Fleet are you running Can you share a little of what s going on in the logs when Fleet is going down

Anoop K V · Answer

Hi < Kathy Satterlee> We are running Fleet 3 11 on AWS Attached is the snapshot of CPU and Memory during the change and logs seen during the time

Lucas Rodriguez · Answer

Hi < Anoop K V> We strongly encourage to upgrade to latest version of Fleet Fleet 3 X is not supported anymore

Anoop K V · Answer

< Lucas Rodriguez> Thanks Has there been any feature fixes came in the latest version that would help us here So that I could push for an upgrade as the setup is in production

Lucas Rodriguez · Answer

Hi < Anoop K V> Since 3 11 a whole lot of new features additions and performance improvements 3 11 0 is more than one and a half years old We strongly recommend to upgrade to latest +1

Lucas Rodriguez · Answer

Forgot to mention some features apart from bug fixes and performance improvements to name a few 1 Policy queries and automation to notify endpoints or create tickets when there s a policy failure 2 Software inventory and vulnerability processing also with automation to notify admins of vulnerabilities in their devices 3 4 New Role based access control RBAC and Teams premium features You can take a look at release notes for all versions in

Lucas Rodriguez · Answer

< Anoop K V> point up 2

Anoop K V · Answer

Thanks < Lucas Rodriguez>