From 429875d4e547618f8ac289c433c480d50dbf7add Mon Sep 17 00:00:00 2001 From: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> Date: Mon, 27 Sep 2021 20:25:23 +0900 Subject: [PATCH] Update 00-Learn-how-to-use-Fleet.md (#2217) Updated to reflect latest UI and query library content changes in Fleet 4.3.0. --- docs/01-Using-Fleet/00-Learn-how-to-use-Fleet.md | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/docs/01-Using-Fleet/00-Learn-how-to-use-Fleet.md b/docs/01-Using-Fleet/00-Learn-how-to-use-Fleet.md index aa7a894d83..c10538fcc9 100644 --- a/docs/01-Using-Fleet/00-Learn-how-to-use-Fleet.md +++ b/docs/01-Using-Fleet/00-Learn-how-to-use-Fleet.md @@ -28,19 +28,14 @@ So, let's start by asking the following questions about Fleet's 7 simulated Linu 2. Do these devices have a high severity vulnerable version of OpenSSL installed? -These questions can easily be answered, by running the following query: "Detect Linux hosts with high severity vulnerable versions of OpenSSL." +These questions can easily be answered, by running this simple query: "Get OpenSSL versions." -On the **Queries** page, enter the query name, "Detect Linux hosts with high severity vulnerable versions of OpenSSL," in the search box, select the query from the results table, and navigate to the **Edit or run query** page. +On the **Queries** page, enter the query name, "Get OpenSSL versions," in the search box, and select it to enter the **query console**. Then from the **query console**, hit "Run query", and from the "Select targets" page, select "All hosts," to run this query against all hosts enrolled in your Fleet. Then hit the "Run" button to execute the query. -Fleet query search +Fleet select targets -On the **Edit or run query** page, open the "Select targets" dropdown, and press the purple "+" icon to the right of "All hosts," to run this query against all hosts enrolled in your Fleet. Then hit the "Run" button to execute the query. - - -Fleet select targets - The query may take several seconds to complete, because Fleet has to wait for the osquery agents to respond with results. > Fleet's query response time is inherently variable because of osquery's heartbeat response time. This helps prevent performance issues on hosts. @@ -48,7 +43,7 @@ The query may take several seconds to complete, because Fleet has to wait for th When the query has finished, you should see 4 columns and several rows in the "Results" table: -Fleet query results +Fleet query results - The "hostname" column answers: which device responded for a given row of results?