Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-3187

[DOC] Pull in Kiali FAQ content: Distributed Tracing

    XMLWordPrintable

Details

    Description

      Add relevant content from the upstream Kiali FAQs to OSSM downstream docs

      1. Identify user story
      2. Identify where content should live in SM docs
      3. Format as a customer task 

       

      https://kiali.io/docs/faq/distributed-tracing/ 

       

      Per Jay's suggestion in comments: https://kiali.io/docs/faq/distributed-tracing/#why-do-i-see-missing-root-span-for-the-root-span-of-some-span-details-on-traces-tab 

      Attachments

        Issue Links

          clones

          Task - Represents a small unit of work that is not end-user facing. OSSM-2908 Pull in Kiali FAQ content: Authentication

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Task - Represents a small unit of work that is not end-user facing. OSSM-3144 [DOC] Pull in Kiali FAQ content: General

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              gmonahan Gwynne Monahan
              cbremble@redhat.com Claire Bremble
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: