Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-4165

Tempo integration with COO

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Minor Minor
    • COO-1.3.0
    • None
    • None
    • Tempo integration with COO
    • Product / Portfolio Work
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • In Progress
    • OBSDA-793 - Tempo integration with COO
    • OBSDA-793Tempo integration with COO
    • 0% To Do, 0% In Progress, 100% Done

      The objective of this epic is to provide integration with the cluster observability operator (COO). 

       

      The users should be able to provision entire tracing observability stack with a single CR. The stack should include an OpenTelemetry collector, Tempo as storage for trace data and tracing UI plugin for the OpenShift console.

       

      The provisioned OTEL collector should be able to receive metrics and logs and configure export to UWM/lokistack.

       

      The OTEL collector should be considered a standalone component that could be used without tracing.

              ploffay@redhat.com Pavol Loffay
              ploffay@redhat.com Pavol Loffay
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: