Epic Goal

Why is this important?

It is too difficult to diagnose customer issues with the current oadp-must-gather tooling 

Scenarios

• support calls with customers
• CI
• debug and test

Dependencies (internal and external)

User Story:
Foundation for product enhancement.

As an engineer 
I want to have access to the relevant OADP debug information in an easy to read format where I'm more likely to diagnose errors quickly.
so that we no longer have to dig through irrelevant files and directories to find what we're looking for. 

Acceptance Criteria: (Definition of Done)
Defines the scope, what to satisfy before the story is proclaimed as completed. Defines pass/fail criteria.

Verify that

• engineering finds the new oadp-must-gather helpful
• support team find the new oadp-must-gather helpful
• testing indicates we are finding issues more easily.

Functional Acceptance Criteria

Non - Functional Acceptance Criteria