-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add configuration option to customize query report cap #19600
Comments
@rachaelshaw It seems we had the 1000 hardcoded on the UI too.
fleet/frontend/pages/queries/details/QueryDetailsPage/QueryDetailsPage.tsx Lines 202 to 203 in 30e4b25
So I added a Let me know if this makes sense. |
@lucasmrod sounds good! Updated the API changes in the description |
#19600 - [X] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://fleetdm.com/docs/contributing/committing-changes#changes-files) for more information. - [X] Added/updated tests - [X] Manual QA for all new/changed functionality
Hey @rachaelshaw, tracking the TODO from our discussion during product design review in this issue so we see it during confirm and celebrate: TODO Rachael: Update GitOps reference docs to call out that you should enable reports for one query at time and monitor your infrastructure UPDATE: Add PR for API changes. |
Hey @zayhanlon & @Patagonia121 this story has shipped but before we notify customers we want to make sure docs PR is merged. See the comment above for TODO docs. |
Docs PR here: #20414 |
- Add documentation for the `query_report_cap` config option. For #19600
Hey @zayhanlon and @Patagonia121, the API reference docs are shipped! Customers can now increase the max number of query report results (per query) Fleet stores. From the From the GitOps reference: |
Customize cap high, |
Goal
Currently, for queries that run on >1000 hosts, query reports in the Fleet UI serve as previews of the data returned, rather than true reports of the latest results. (Those users need to send data to a log destination in order to build a complete up-to-date report, since reports in Fleet are clipped at 1,000.)
Context
Changes
Product
server_settings.query_report_cap
to Fleet configuration APIreport_clipped
toGET /api/latest/fleet/queries/:query_id/report
responseEngineering
QA
Risk assessment
Manual testing steps
Testing notes
Confirmation
The text was updated successfully, but these errors were encountered: