Feature Overview

When creating a custom dashboard it should only be enabled and shown in the UI if there are actual values in it. Further it should be easily enabled/disabled and shown/hidden in the ui

Goals

• let's assume you want to monitor Virtual-Machines, the dashboard would not look nice if you don't have any in the fleet defined.
• the solution must work also with other dashboards especially Gitops-Operator

Requirements

We need to discuss the best way in some architectural forum

(Optional) Use Cases

This Section:

• Main success scenarios - high-level user stories
• Alternate flow/scenarios - high-level user stories
• ...

Questions to answer

• how can this be achieved?
  Is it a UI feature?
  Can it be achieved using Policies?

Out of Scope

• …

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?