Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3493

Red Hat Logging for Observability

XMLWordPrintable

    • Logging Next
    • 100
    • False
    • None
    • False
    • Yellow
    • NEW
    • Administer, API, Deploy
    • To Do
    • OBSDA-550 - Updated APIs for Logging 6.0
    • OBSDA-550Updated APIs for Logging 6.0
    • NEW
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      This feature introduces a new architecture for Red Hat OpenShift Logging by deferring or moving component responsibilities to their respective operators (e.g. storage, visualization, collection). It introduces the ClusterLogForwarder.observability.openshift.io API for log collection and forwarding. Lastly, it removes support for the ClusterLogging.logging.openshift.io, ClusterLogForwarder.logging.openshift.io APIs, and the Red Hat Managed Elastic stack consisting of Elasticsearch and Kibana. User's are encouraged to migrate to the Red Hat LokiStack for their log storage needs and can continue to use existing, managed Elasticsearch deployments for a limited time. This feature does not provide an automated migration for log collection and requires administrators to create a new ClusterLogForwarder.observability.openshift.io spec to replace their previous custom resources. See the official product documentation for additional details.
      Show
      This feature introduces a new architecture for Red Hat OpenShift Logging by deferring or moving component responsibilities to their respective operators (e.g. storage, visualization, collection). It introduces the ClusterLogForwarder.observability.openshift.io API for log collection and forwarding. Lastly, it removes support for the ClusterLogging.logging.openshift.io, ClusterLogForwarder.logging.openshift.io APIs, and the Red Hat Managed Elastic stack consisting of Elasticsearch and Kibana. User's are encouraged to migrate to the Red Hat LokiStack for their log storage needs and can continue to use existing, managed Elasticsearch deployments for a limited time. This feature does not provide an automated migration for log collection and requires administrators to create a new ClusterLogForwarder.observability.openshift.io spec to replace their previous custom resources. See the official product documentation for additional details.
    • Feature
    • L

      Goals

      The goals of this epic are to:

      • Drop all dependencies upon out dated technologies (e.g. fluentd, Elastic stack)
      • Drop the ClusterLogging.logging.openshift.io API
      • Introduce the ClusterLogForwarder.observability.openshift.io API to replace ClusterLogForwarder.logging.openshift.io
      • Produce an alternate workflow for deploying a full logging stack

      Non-Goals

      Motivation

      • The primary motivation is drop technologies we no longer will offer
         

        Alternatives

      • Alternative is to continue updating the 1.0 apis

      Acceptance Criteria

      • Verify administrators can deploy a logging stack that includes vector forwarding, loki logstorage, console visualization
      • Verify forwarding and collection can be deployed using the new CLF.observability API
      • Verify existing forwarding and collection are migrated to the new CLF.opservability API

      Risk and Assumptions

      Documentation Considerations

      Open Questions

      Additional Notes

      Specific Items to review before release:

      • template of parameters
      • Viaq specific changes in outputs (e.g. flat labels). Drop? Figure out how to swap from viaq v1 and v2
      • token auth in elasticsearch
      • Document migration of default es should provide index that matches alias
      • Document migrations for enabling container structured logs
      • Viaq v2 remove "file" field
      • Add validation for http auth for token or username/password only
      • Ensure outputs modify "timestamp" key to viaq V2
      • migrate syslog "field references" to use vector like templating
      • Document removal of non-RFC fields which varies from v1: remove_tag_prefix , tag_key , use_record, payload_key
      • Document all labels passed to ES with underscore... instead of allow list

          There are no Sub-Tasks for this issue.

              jcantril@redhat.com Jeffrey Cantrill
              jcantril@redhat.com Jeffrey Cantrill
              Qiaoling Tang Qiaoling Tang
              Libby Anderson Libby Anderson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: