Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-2608

OpenShift Debuggability MVP - OpenShift.Next

XMLWordPrintable

    • Icon: Outcome Outcome
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • None

      Outcome Overview

      Once all Features and/or Initiatives in this Outcome are complete, what tangible, incremental, and (ideally) measurable movement will be made toward the company's Strategic Goal(s)?

      This can be used as the overarching tracker for AI-Assisted debuggability within openshift for OpenShift.NEXT. Since this outcome is dependent on at least 2 teams: OpenShift Observability and OpenShift Application Platform Engineering (for must-gather work) we can use this outcome as the high level tracker, with the goal of supplying the customer with 2 key capabilities:

      1. Real-time/Self-service Debuggability of OpenShift (Observability Team)
      2. Improved Debuggability when working with Red Hat Support (OAPE)

      Delivery of these capabilities should significantly impact and reduce:

      1. MTTR - Mean Time to Recovery
      2. MTTD - Mean Time to Discovery (more for real-time/self-service debuggability)

      Tangible outputs of these high level capabilities should be linked as features to this tracker but could include:

      • MCP Servers - necessary to supply a LLM such as OLS with data needed for triage, or to inform an LLM how to construct certain manifests in order to execute specific commands for log gathering (MCP Resource vs Tool)

       

      Success Criteria

      What is the success criteria for this strategic outcome?  Avoid listing Features or Initiatives and instead describe "what must be true" for the outcome to be considered delivered.

      Success criteria should be measured based on the number of self-resolved tickets (more tickets self-resolved by customers is better) and mean time to resolution of red hat support tickets (lower MTTR is better). Finally, we can also measure the % of tickets that result in a support exception (fewer is better)

       

      Expected Results (what, how, when)

      What incremental impact do you expect to create toward the company's Strategic Goals by delivering this outcome?  (possible examples:  unblocking sales, shifts in product metrics, etc. + provide links to metrics that will be used post-completion for review & pivot decisions). {}For each expected result, list what you will measure and when you will measure it (ex. provide links to existing information or metrics that will be used post-completion for review and specify when you will review the measurement such as 60 days after the work is complete)

       

       

      Post Completion Review – Actual Results

      After completing the work (as determined by the "when" in Expected Results above), list the actual results observed / measured during Post Completion review(s).

       

              rh-ee-npng Nick Png
              rh-ee-npng Nick Png
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: