Story (Required)

As a support engineer trying to diagnose a field issue I want to be able request the customer to retrieve assets enable debugging the problem by simple clicking on buttons or running a script.

The goal of this story to define assets need to troubleshoot a problem. Some simple steps for customer to follow to retrieve everything support engineers need to diagnose the problem.

Background (Required)

Currently, we have to instruct customer/field engineer to gather diagnosis information. It is often too late to capture the critical information needed. Some simple steps or scripts will reduce the time to successfully gather the assets and eliminate human errors and delays.

Out of scope

<Defines what is not included in this story>

Approach (Required)

identify and document the assets needed.

Dependencies

None

Acceptance Criteria (Mandatory)

• Define the information we need for properly troubleshooting a case (e.g. what logs are required, what other assets such as the Operand, config maps, custom resources, etc are required)

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met