Know how many hosts, and which hosts, are missing

[noahtalerman]

Problem

I'm an engineer managing thousands of hosts and I'm overwhelmed with tracking this goal:

• Know how many hosts, and which hosts, are missing.

This makes it hard to troubleshoot why a host is missing. Is the user on a longer vacation? Is the host stolen? Is the host is someone's closet? Is the host broken?

Goals

1. Know how many hosts are missing.

2. Know which hosts are missing.

Requirements

• Fleet Premium users can see how many hosts (count) have been offline for 30 days or more.
• Fleet Premium users can navigate to a list of hosts filtered by hosts that have been offline for 30 days or more. The user can navigate to this list via the Fleet UI or by pasting a URL in their browsers URL bar.
• The UI is powered by updates to the GET /host_summary API route.
• The Fleet API supports adding more intervals in the future. For example, later, we may want to add the ability to see how many hosts have been offline for 7 days or more.

Figma

https://www.figma.com/file/hdALBDsrti77QuDNSzLdkx/%F0%9F%9A%A7-Fleet-EE-(dev-ready%2C-scratchpad)?node-id=9223%3A304723

API

1. Update the GET /host_summary API route

• See Add new missing_30_days_count property to the GET /host_summary endpoint #7587

2. Add new param to GET /hosts to filter by missing hosts.

• See Add new "Missing" hosts count card to dashboard, and set status query param to missing #7589

Parent Epic

• Expansion of host vitals #397

Child issues

Backend:

• Add new missing_30_days_count property to the GET /host_summary endpoint #7587
• Add new missing value to existing status URL parameter at the GET /hosts endpoint #7588

Frontend:

• Add new "Missing" hosts count card to dashboard, and set status query param to missing #7589

[noahtalerman]

@lukeheath heads up, this issue and the related issues (found in the "Related issues" section) are a top priority after "Update query console right side panel in Fleet product". This is because they are tied to the following Q4 OKRs:

I'd like to estimate these issues during next week's estimation.

Even though these issues are currently being designed, I wanted to give you a heads up so that you have time to...

• think about who will be responsible for spec'ing these issue
• draft API wireframes. If it's helpful I'm happy to hop on a call to work on these together.

Once designed, I will move them under the "Update query console right side panel in Fleet product" issue in the designed column to indicate their priority:

[lukeheath]

@noahtalerman Sounds good and thanks for the heads up. I'll keep an eye out for these hitting the design column. Do you think that will happen by Tuesday?

[noahtalerman]

Do you think that will happen by Tuesday?

@lukeheath yes. I will @ mention you when they hit the designed column.

[noahtalerman]

@lukeheath this issue and the other issues under the "Related" section in this issue's description are in the designed column. I assigned you these issues.

When you get the chance, can you please confirm high-level requirements and create child issues as necessary? Thanks :)

I also added an agenda item to today's interface weekly call. Item is to discuss these issues. I think it's a good idea to chat about the requirements like we did during last week's estimation.

[noahtalerman]

@erikng heads up, we updated the requirements to "see how many hosts have been offline for 30 days or more" (originally 10 days or more).