Feature Overview 

Implement a set of predefined dashboards for network observability as defined in the requirements document.

Goals

• Provide mechanisms for the customer / user to consume infrastruture telemetry data to realize improved network observability
• Reduce the RCA significantly and reduce the number of support tickets or Red Hat engineering time for RCA and support by making the customer self-reliant

Requirements 

Implement the pre-defined dashboards for network observability . This set of dashboards may be updated. The pre-defined dashboards are there to supplement the generic observability dashboards and not replace the generic observability capabilities

Detailed Requirements Document

Done - Acceptance Criteria 

1. Implement the predefined dashboards
2. Ensure that the predefined dashboards address the top use cases defined in the requirements document
3. QE testing for workflow and quality
4. Documentation for navigation worklow and how to use the 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

• …