Feature Overview 

Predefined dashboards may not address specific customer needs for network observability. The customer/user must be able to replicate predefined dashboards, modify the replicated ones to customize the dashboards, or be able to create entirely new dashboards.  User must be able to create or modify existing dashboards (except the pre-defined ones) from the UI or via scripts / json (if json definition is the one used for creating the dashboards)

Goals

• Provide flexibility to create custom visualization for network observability

Requirements 

Detailed Requirements Document

Done - Acceptance Criteria 

1. Implement and test custom dashboard definitions
2. QE testing for workflow and quality
3. Documentation for how to create new custom dashboards or customize the visualization for existing ones
4. Documentation for metrics categories and widgets available to create custom dashboards
5. Release notes

Use Cases 

Refer to the requirements document for detailed use case information

Out of Scope 

• Generic observability dashboards or capabilities
• Custom dashboards (requirements defined a separate Jira feature)

Documentation Considerations 

• Release Notes

• Documentation for navigation workflows and use case descriptions 

Background and Strategic Fit 

Must have for reducing RCA, reducing customer OPEX for maintaining the RHOSO deployments, improving ability to scale to support a larger number of customers, and making customers self-reliant for an increased number of support needs. This capability will act as a key differentiator and help with gaining market share from the competition. It will also obviate the need to rely on 3rd-party network monitoring solutions and integrating those solutions with OpenStack.

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

• …