• Icon: Epic Epic
    • Resolution: Obsolete
    • Icon: Critical Critical
    • None
    • None
    • Installer Core
    • Installer Telemetry
    • 5
    • installer
    • Done
    • OCPSTRAT-97 - Installer Telemetry Collection
    • OCPSTRAT-97Installer Telemetry Collection
    • 23% To Do, 0% In Progress, 77% Done

      Goal:

      As a product owner for the installer, I want insight into how users run the installer and their rate of success.

      Problem:

      Clusters don’t provide any telemetry until they are fully installed. If a user encounters an error during this process, we won’t know about it unless they notify us. This makes it very difficult to understand the global success rate for installation.

      This is specifically not about the resultant cluster and therefore none of these metrics should be tied to a cluster-id, instead we'll have to create an identifier that tracks a specific installation workflow.

      Why is this important:

      In order to improve the product and improve the rate of success, we need to be able to measure that rate of success and understand what errors are encountered.

      Dependencies (internal and external):

      • Service Delivery needs to create and run the telemetry-gathering service

      Previous Work:

      • Telemeter

      Customers:

      Specifics unknown

       

      Open Questions

      • Compile Examples of data we'd like to send back
      • Confirm whether Telemetry can receive reports or only time series data

              Unassigned Unassigned
              rhn-coreos-acrawfor Alex Crawford (Inactive)
              Jianli Wei Jianli Wei
              Votes:
              1 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: