I do miss the grid view, and it doesn't appear that I can resize the columns so even on my very wide monitor, I still have to scroll

Hey Zach, thanks for the feedback. How many hosts do you normally have in your Fleet instance? cc @Noah Talerman

This is just a dev instance of fleet, so we only have about 100 instances in this case. production fleet is expected to be online sometime soon, and that'll have ~4k.

just going to pile onto this with an upvote • resizable columns • selecting & re-ordering columns • less whitespace additional feedback: • the delete & query icons are so similar, I want more contrast. • I miss the colors for online / offline, but I'll wait to see how I feel about it in a few days. MIA icon upvote And I'll end with: 🎉 overall I'm a huge fan of the updates 😄

Thanks for the suggestions and feedback! A restructuring of the Hosts page, including more control over the hosts table, is something we’re definitely looking into.

Oh and how many hosts in fleet instance? Have multiple fleet instances for different environments, but largest individual one is XX,000.

Oh and how many hosts in fleet instance?

This question stems from not fully understanding your setup for Fleet. Does the small count above your hosts table not display the correct host total?

It seems to work for me, won't claim to speak for Zach Zeid above. (separate company) -- I just figured a rough idea of host count may be useful

we're only running a few dozen in our dev instance, we expect there to be more once we deploy a production-ready environment

Got it.

ttbh, I'd love to be able to dynamically populate host details with query decorators, at the very least.

^ yes this If there were a very detailed page, I'd love to be able to see decorator values, for example, maybe displaying "additional host details" query info. Example: I'm considering getting installed packages via additional hosts queries. Then if I could display that, I could see what packages are installed on the host. Example: I might add decorators for environment, service name, etc. Being able to choose either decorators or additional host info to display would be useful. Generic: • osquery config hash • kernel version • label(s) for the host • some sort of presentation of osquery_schedule info (for denylisted queries / performance analysis?) or maybe on a separate page that could aggregate / slice & dice this data? • flags / options 🤷 • which packs / queries apply to the host • which enroll secret the host used • host uuid

Great suggestions. Thank you. Why would it be helpful to see decorator values in the UI? Same question but more specific to the example, why would you like to see what packages are installed on the host, the environment, and service name in the UI?

decorator values: I guess maybe less-specifically I would say: "user-defined query results showing in the UI". Maybe that's decorators, maybe additional hosts queries. It can be used to display extra metadata specific to our environment, for example: owner, service name, environment, etc.

That can be useful when trying to figure out “is X service / host reporting? How many of X service hosts are reporting, etc” in fleet.

Would displaying the extra metadata on a Host details page achieve these goals with something like XX,XXX hosts reporting? I’m curious if including the extra metadata on each individual Hosts detail pages alone would achieve these goals. Or if a way to search/sort hosts (by owner, service name, etc.) in the UI is also necessary.

It's mostly about correlation of data. Okay, an individual host page doesn't need to solve "how many of this host". But if I can say "oh this is a prod foo-service host", then I can go look for more of those. I definitely think there's a lot that could be done on the search front to make this better.

It’s mostly about correlation of data.

This detail is super helpful for my understanding. And thank you for the different paths explanation.

Thanks everyone. This on our list for Jan.