Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-5637 In-Cluster end-to-end support for OTLP-ingestion and OTEL Semantic Conventions
  3. LOG-6255

QE - Design validation scenarios with LokiStack providing a native OTLP ingestion point

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • False
    • None
    • False
    • NEW
    • OBSDA-849 - Enable Full In-Cluster OpenTelemetry Support In OpenShift Logging
    • NEW

      Design QE cases to cover below User stories:

      • As an administrator, I want to deploy an in-cluster logging solution that makes use of the OpenTelementry Observability framework so I can make correlations with other observability signals (i.e. metrics, tracing) in an industry, standardized way
      • As a developer, I want users to be able to query log records using OTEL or ViaQ attributes: log type, namespace, pod name, container name to facilitate LokiStack's transition from using ViaQ to OTEL
      • As a developer, I want Red Hat LokiStack to provide a native OTLP ingestion point so that other Red Hat products can forward observability signals using OTEL and rely upon OpenShift Logging tenancy and RBAC integration

       

      Polaroin Test Run: https://polarion.engineering.redhat.com/polarion/#/project/OSE/testrun?id=20241103-2058

       

       

              rhn-support-kbharti Kabir Bharti
              rhn-support-kbharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: