-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a list of Osquery fleet managers #7781
Conversation
Following on from a quick discussion on Slack. I've added a table to show case the available fleet managers for Osquery.
Co-authored-by: Zach Wasserman <zach@fleetdm.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little ambivalent about this. But will to go with the flow.
I think it's hard to enumerate everyone. And that makes me wonder if this is the wrong place for it.
PS: I don't have any investment here, I just approved because there wasn't anything against it and the change request was resolved. I think the TSC should decide here. |
Not against it, just offering an opinion: Kolide and Fleet are both upstream contributors that ensure osquery is well tested against those environments. From the point of view of a user, it may be useful to know this detail when choosing a fleet manager. Without this, it's not immediately clear whether we are endorsing software we tried/develop or just listing 3rd party projects we are not involved in (which may be useful to disclose) |
I added some text. How's it look to you? |
If you think it's worth mentioning that both Fleet and Kolide are active upstream contributors (contributing not just patches but also a lot of testing at each release) they could maybe be grouped in their own category. Otherwise, this looks good! |
That seemed like more effort than it's worth right now. |
Following on from a quick discussion on Slack. I've added a table to show case the available fleet managers for Osquery.