mirror of
https://github.com/fleetdm/fleet
synced 2026-05-22 00:18:27 +00:00
Docs: Update documentation to reflect scheduled query changes. (#12884)
This commit is contained in:
parent
388d6511db
commit
ee4ce28c02
2 changed files with 30 additions and 20 deletions
|
|
@ -22,7 +22,7 @@ How to create a query:
|
|||
|
||||
3. In the **Query** field, enter your query. Remember, you can find common queries in [Fleet's library](https://fleetdm.com/queries).
|
||||
|
||||
4. Select **Save**, enter a name and description for your query, and select **Save query**.
|
||||
4. Select **Save**, enter a name and description for your query, select the frequency that the query should run at, and select **Save query**.
|
||||
|
||||
## Run a query
|
||||
|
||||
|
|
@ -44,33 +44,43 @@ The query may take several seconds to complete because Fleet has to wait for the
|
|||
|
||||
## Schedule a query
|
||||
|
||||
Fleet allows you to schedule queries. Scheduled queries will send data to your log destination automatically.
|
||||
*In Fleet 4.35.0, the "Schedule" page was removed, and query automations are now configured on the "Queries" page. Instructions for scheduling queries in earlier versions of Fleet can be found [here](https://github.com/fleetdm/fleet/blob/ac797c8f81ede770853c25fd04102da9f5e109bf/docs/Using-Fleet/Fleet-UI.md#schedule-a-query).*
|
||||
|
||||
>Only users with the [admin role](https://fleetdm.com/docs/using-fleet/manage-access#admin) can manage query automations.
|
||||
|
||||
Fleet allows you to schedule queries to run at a set frequency. Scheduled queries will send data to your log destination automatically.
|
||||
|
||||
The default log destination, **filesystem**, is good to start. With this set, data is sent to the `/var/log/osquery/osqueryd.snapshots.log` file on each host’s filesystem. To see which log destinations are available in Fleet, head to the [log destinations page](https://fleetdm.com/docs/using-fleet/log-destinations).
|
||||
|
||||
How to schedule a query:
|
||||
By default, queries that run on a schedule will only target platforms compatible with that query. This behavior can be overridden by setting the platforms in the "advanced options" when saving a query.
|
||||
|
||||
1. In the top navigation, select **Schedule**.
|
||||
**How to schedule queries:**
|
||||
|
||||
2. Select **Schedule a query**.
|
||||
1. In the top navigation, select **Queries**.
|
||||
|
||||
3. Select the **Select query** dropdown and choose the query that you'd like to run on a schedule.
|
||||
2. Select **Manage automations**.
|
||||
|
||||
4. Select the **Frequency** dropdown and choose how often you'd like the query to run and send results to your log destination. **Every hour** is a good frequency to start. You can change this later.
|
||||
3. Check the box next to the queries you want to automate, and select **Save**.
|
||||
|
||||
5. Select **Schedule**.
|
||||
> The frequency that queries run at is set when a query is created.
|
||||
|
||||
With Fleet Premium, you can schedule queries for groups of hosts using [the teams feature](https://fleetdm.com/docs/using-fleet/teams). This allows you to collect different data for each group.
|
||||
With Fleet Premium, you can schedule queries for groups of hosts using [the teams feature](https://fleetdm.com/docs/using-fleet/segment-hosts). This allows you to collect different data for each group.
|
||||
|
||||
> In Fleet Premium, groups of hosts are called "teams."
|
||||
|
||||
How to use teams to schedule queries for a group of hosts:
|
||||
**How to use teams to schedule queries for a group of hosts:**
|
||||
|
||||
1. If you haven't already, first [create a team](https://fleetdm.com/docs/using-fleet/teams#create-a-team) and [transfer hosts](https://fleetdm.com/docs/using-fleet/teams#transfer-hosts-to-a-team) to the team.
|
||||
1. If you haven't already, first [create a team](https://fleetdm.com/docs/using-fleet/segment-hosts#create-a-team) and [transfer hosts](https://fleetdm.com/docs/using-fleet/segment-hosts#transfer-hosts-to-a-team) to the team.
|
||||
|
||||
2. In the **Teams** dropdown below the top navigation, select the team.
|
||||
2. In the top navigation, select **Queries**.
|
||||
|
||||
3. Follow the "How to schedule a query" instructions above.
|
||||
3. In the **Teams** dropdown below the top navigation, select the team you want to manage automation for.
|
||||
|
||||
4. Select **Manage automations**
|
||||
|
||||
5. Select the queries you want to run on a schedule for this team, and select **Save**.
|
||||
|
||||
> Note: Only queries that belong to the selected team will be listed. When configuring query automations for all hosts, only global queries will be listed.
|
||||
|
||||
## Update agent options
|
||||
|
||||
|
|
|
|||
|
|
@ -10,19 +10,19 @@ Users with the admin role receive all permissions.
|
|||
|
||||
### Maintainer
|
||||
|
||||
Maintainers can manage most entities in Fleet, like queries, policies, labels and schedules.
|
||||
Maintainers can manage most entities in Fleet, like queries, policies, and labels.
|
||||
Unlike admins, maintainers cannot edit higher level settings like application configuration, teams or users.
|
||||
|
||||
### Observer
|
||||
|
||||
The Observer role is a read-only role. It can access most entities in Fleet, like queries, policies, labels, schedules, application configuration, teams, etc.
|
||||
The observer role is a read-only role. It can access most entities in Fleet, like queries, policies, labels, application configuration, teams, etc.
|
||||
They can also run queries configured with the `observer_can_run` flag set to `true`.
|
||||
|
||||
### Observer+
|
||||
|
||||
`Applies only to Fleet Premium`
|
||||
|
||||
Observer+ is an Observer with the added ability to run *any* query.
|
||||
Observer+ is an observer with the added ability to run *any* query.
|
||||
|
||||
### GitOps
|
||||
|
||||
|
|
@ -51,7 +51,7 @@ GitOps is an API-only and write-only role that can be used on CI/CD pipelines.
|
|||
| Run any query as [live query](https://fleetdm.com/docs/using-fleet/fleet-ui#run-a-query) against all hosts | | ✅ | ✅ | ✅ | |
|
||||
| Create, edit, and delete queries | | | ✅ | ✅ | ✅ |
|
||||
| View all queries\** | ✅ | ✅ | ✅ | ✅ | |
|
||||
| Add, edit, and remove queries from all schedules | | | ✅ | ✅ | ✅ |
|
||||
| Manage [query automations](https://fleetdm.com/docs/using-fleet/fleet-ui#schedule-a-query) | | | ✅ | ✅ | ✅ |
|
||||
| Create, edit, view, and delete packs | | | ✅ | ✅ | ✅ |
|
||||
| View all policies | ✅ | ✅ | ✅ | ✅ | |
|
||||
| Filter hosts using policies | ✅ | ✅ | ✅ | ✅ | |
|
||||
|
|
@ -100,11 +100,11 @@ GitOps is an API-only and write-only role that can be used on CI/CD pipelines.
|
|||
|
||||
Users in Fleet either have team access or global access.
|
||||
|
||||
Users with team access only have access to the [hosts](https://fleetdm.com/docs/using-fleet/rest-api#hosts), [software](https://fleetdm.com/docs/using-fleet/rest-api#software), [schedules](https://fleetdm.com/docs/using-fleet/fleet-ui#schedule-a-query) , and [policies](https://fleetdm.com/docs/using-fleet/rest-api#policies) assigned to
|
||||
Users with team access only have access to the [hosts](https://fleetdm.com/docs/using-fleet/rest-api#hosts), [software](https://fleetdm.com/docs/using-fleet/rest-api#software), and [policies](https://fleetdm.com/docs/using-fleet/rest-api#policies) assigned to
|
||||
their team.
|
||||
|
||||
Users with global access have access to all
|
||||
[hosts](https://fleetdm.com/docs/using-fleet/rest-api#hosts), [software](https://fleetdm.com/docs/using-fleet/rest-api#software), [queries](https://fleetdm.com/docs/using-fleet/rest-api#queries), [schedules](https://fleetdm.com/docs/using-fleet/fleet-ui#schedule-a-query) , and [policies](https://fleetdm.com/docs/using-fleet/rest-api#policies). Check out [the user permissions
|
||||
[hosts](https://fleetdm.com/docs/using-fleet/rest-api#hosts), [software](https://fleetdm.com/docs/using-fleet/rest-api#software), [queries](https://fleetdm.com/docs/using-fleet/rest-api#queries), and [policies](https://fleetdm.com/docs/using-fleet/rest-api#policies). Check out [the user permissions
|
||||
table](#user-permissions) above for global user permissions.
|
||||
|
||||
Users can be a member of multiple teams in Fleet.
|
||||
|
|
@ -124,7 +124,7 @@ Users that are members of multiple teams can be assigned different roles for eac
|
|||
| Run any query as [live query](https://fleetdm.com/docs/using-fleet/fleet-ui#run-a-query) | | ✅ | ✅ | ✅ | |
|
||||
| Create, edit, and delete only **self authored** queries | | | ✅ | ✅ | ✅ |
|
||||
| View all queries\** | ✅ | ✅ | ✅ | ✅ | |
|
||||
| Add, edit, and remove queries from the schedule | | | ✅ | ✅ | ✅ |
|
||||
| Manage [query automations](https://fleetdm.com/docs/using-fleet/fleet-ui#schedule-a-query) | | | ✅ | ✅ | ✅ |
|
||||
| View policies | ✅ | ✅ | ✅ | ✅ | |
|
||||
| View global (inherited) policies | ✅ | ✅ | ✅ | ✅ | |
|
||||
| Run global (inherited) policies as a live policy | | | ✅ | ✅ | |
|
||||
|
|
|
|||
Loading…
Reference in a new issue