Goal
| User story |
| As a Fleet user setting a report's interval, |
| I want the UI to accurately explain what the interval controls, |
| so that I understand why results take a while to show up instead of assuming Fleet is slow or broken. |
For help creating a user story, see "Writing a good user story" in the website handbook.
Discussed in #31171. Today, the Interval field's help text (in both the "Save report" and "Edit report" modals) reads:
This is how often your report collects data.
That's not accurate. As Rachael pointed out: the interval is how long each host waits, based on its own (osquery) uptime, before it sends new data to Fleet. If the interval is 1 hour, a host has to be online for 1 hour before it reports in. It's not Fleet polling on a schedule.
The "Collecting results..." empty state (shown while waiting for the first results) has the same problem — it reads "Fleet is collecting report results. Check back in about X" which implies Fleet is actively working, when it's actually waiting on host uptime.
Change
Goal
Discussed in #31171. Today, the Interval field's help text (in both the "Save report" and "Edit report" modals) reads:
That's not accurate. As Rachael pointed out: the interval is how long each host waits, based on its own (osquery) uptime, before it sends new data to Fleet. If the interval is 1 hour, a host has to be online for 1 hour before it reports in. It's not Fleet polling on a schedule.
The "Collecting results..." empty state (shown while waiting for the first results) has the same problem — it reads "Fleet is collecting report results. Check back in about X" which implies Fleet is actively working, when it's actually waiting on host uptime.
Change