What s the update strategy for endpoint packages I occasiona

Question

What s the update strategy for endpoint packages I occasionally see Orbit releases in GitHub how do we make sure our endpoints have the latest version Do they self update Does `fleetctl` pull the latest version when building installers so we have to re build In the web portal I only see the osquery version not the Orbit version so it s always felt opaque to me

Kathy Satterlee · Answer

Hi Orbit keeps itself up to date based on a configurable <https fleetdm com docs using fleet orbit update channels|update channel>

Kathy Satterlee · Answer

You can check the Orbit version on your hosts with the <https fleetdm com tables orbit info|orbit info> table

Shawn Maddock · Answer

Is Fleetd the old name for Orbit

Shawn Maddock · Answer

Because that `orbit info` table is not available in my instance

Shawn Maddock · Answer

Apologies if I m missing some basic concepts here

Kathy Satterlee · Answer

Is it not queryable or not showing up in the schema

Shawn Maddock · Answer

When I try to create a new query through the web UI it s not in the list of tables

Kathy Satterlee · Answer

Try querying it anyway

Kathy Satterlee · Answer

SELECT FROM orbit info

Shawn Maddock · Answer

That worked

Kathy Satterlee · Answer

I ll look in to why it s not showing as a table

Shawn Maddock · Answer

Stable channels for all three components most on 1 6 0 a couple laggards on 1 5 0 +1

Shawn Maddock · Answer

Thanks for explaining

Kathy Satterlee · Answer

Any time