Documentation: Add warning about lack of centralized logging (#21865)

Following team feedback from PR #20723.

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

Feedback Row 7: Added warning about lack of centralized logging.

Co-authored-by: Joey Salazar <jgsal@yahoo.com>

articles/fleetctl.md

@@ -32,6 +32,8 @@ npm install -g fleetctl@latest
 
 Much of the functionality available in the Fleet UI is also available in `fleetctl`. You can run queries, add and remove users, generate Fleet's agent (fleetd) to add new hosts, get information about existing hosts, and more!
 
+> Note: Unless a logging infrastructure is configured on your Fleet server, osquery-related logs will be stored locally on each device. Read more [here](https://fleetdm.com/guides/log-destinations)
+
 To see the available commands you can run:
 
 ```sh

articles/queries.md

@@ -2,6 +2,8 @@
 
 Queries in Fleet allow you to ask questions to help you manage, monitor, and identify threats on your devices. This guide will walk you through how to create, schedule, and run a query.
 
+> Note: Unless a logging infrastructure is configured on your Fleet server, osquery-related logs will be stored locally on each device. Read more [here](https://fleetdm.com/guides/log-destinations)
+
 > New users may find it helpful to start with Fleet's policies. You can find policies and queries from the community in Fleet's [query library](https://fleetdm.com/queries). To learn more about policies, see [What are Fleet policies?](https://fleetdm.com/securing/what-are-fleet-policies) and [Understanding the intricacies of Fleet policies](https://fleetdm.com/guides/understanding-the-intricacies-of-fleet-policies).
 
 ### In this guide: