empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 08:55:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Document how performance indicator text is determined (#16553)

Browse Source 
Proposing this as a potential resolution for
https://github.com/fleetdm/fleet/issues/16123.
 
The only place we talk about performance impact in the docs is
[here](https://fleetdm.com/docs/get-started/faq#will-fleet-slow-down-my-servers-what-about-my-employee-laptops),
and it feels too high-level to include these details.

Since that FAQ section links to this article for more information about
performance impact, this seems like the most appropriate place to
document that info without adding surface area to the conceptual docs.

Code for displaying performance impact:
7da9019f4d/frontend/utilities/helpers.tsx (L691-L706)
This commit is contained in:
Rachael Shaw 2024-02-02 13:03:43 -06:00 committed by GitHub
parent af354863d6
commit 669f796d3a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
articles/fleet-4.5.0.md
View File

@ -55,6 +55,12 @@ When creating or editing a query in Fleet (either a live query, schedule, or pol
This new feature allows users to see an indication of the performance impact of scheduled queries across all devices. This is useful for mitigating the potential risk of disruption to end-users when running queries.
The level of performance impact is derived from [a query's `stats` object](https://fleetdm.com/docs/rest-api/rest-api#get-query), by totaling up milliseconds `stats.system_time_p50` and `stats.user_time_p50`:
+ **Minimal:** less than 2000
+ **Considerable:** 2000-3999
+ **Excessive:** 4000+
## First steps towards aggregated device data on the Fleet UI dashboard
**Available in Fleet Free & Fleet Premium**