fleet
fleet copied to clipboard
fleetdm
Make Schedule + Teams the best practice for targeting groups of computers
Goals
Improve the experience of targeting computers for all users by making "Schedule" the best practice for getting fast and accurate data for all your computers.
Add more value to Fleet Premium by making "Teams" the best practice for targeting groups of computers in Fleet.
Sub issues
Interface
- #6716
- #5725
- #6024
Guides
- #7175
- #6217
Customer 1: Hosts are tagged and we instruct Osquery to read these tags to create labels such as hosts in certain datacenters, hosts part of certain services, cloud, on-prem, osquery verison
Customer 1: I would love to see the feature in which a label is automatically created as the result of query. Example query:
SELECT service FROM machine_attributes
| service |
| --------------- |
| storage |
| --------------- |
Problem 1: It takes too much work to only run certain queries on hosts based on the host's attributes. For each new service, I have to create a label and wait for hosts to respond before I run the query.
Hypothesis 1: Have 1 query that automatically creates teams for any new service and assigns hosts. This might make Teams more powerful than the top level label.
Customer 2: Teams is falling short because there’s 1 group of people at my org that manages Windows Desktop, Windows Servers, and Windows Laptops. Because there’s 1 group of people, all these Windows machines live under 1 team in Fleet.
Problem 2: On this Windows team, I want to have a policy that only targets Windows Laptops.
Hypothesis: 2: I want the ability to target a subset of my team's hosts based on some attribute.
UPDATE: https://github.com/fleetdm/fleet/issues/7765 replaces https://github.com/fleetdm/fleet/issues/6716 (now deprioritized) in the definition of done (sub issues).
@mikermcneil heads up, I updated the definition of done for this OKR.
Please let me know if you have any questions/concerns.
Teams unite, divide Computers under control Fleet flows like the breeze.
