-
Notifications
You must be signed in to change notification settings - Fork 360
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
Unclear how often policy pass/fail counts update #19083
Comments
@lukeheath by design the cron job that updates the total number runs every 1H. If still required, we can make it a story. In such case we'll need product to describe how to solve it. (e.g. UI will count current failing hosts, or more frequent cron jobs etc) |
@lukeheath here's the issue where we made this change: #13574 I think 1 hr is for customers with a large number of policies and hosts. We could crank it down in dogfood. But, I don't think this job's frequency is configurable. @mostlikelee please correct me if I'm wrong. Maybe that's the feature request: making this job configurable. |
That's correct. We could also consider defaulting smaller environments to calculate counts on demand. The original issue is that the request/page load would take a very long time with large amounts of hosts and policies. |
Thanks Tim! Moving this one to feature fest. |
@lukeheath we added this tooltip a few months ago, does this solve it or do you think that info needs to be more prominent? |
Removing from feature fest for now. @lukeheath please feel free to bring it back. |
@rachaelshaw Thanks, I think the tooltip addresses this issue. Closing. |
Policy counts in sync, |
Fleet version: 4.49.3
Web browser and operating system: Chrome
💥 Actual behavior
A policy count shows 2 failing hosts ("macOS - Check if latest version"), but when I click the link, I see 25 hosts that are listed as showing. If we know the 25 failing hosts, we should update the policy count. It did eventually update.
🧑💻 Steps to reproduce
🕯️ More info (optional)
N/A
The text was updated successfully, but these errors were encountered: