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

GA vector as the primary collector for logging (Phase 1)

    XMLWordPrintable

Details

    • Deploy Vector Collector as a GA offering (Phase 1)
    • 26
    • False
    • False
    • Yellow
    • NEW
    • In Progress
    • OBSDA-108 - Distribute an alternate Vector Log Collector
    • VERIFIED
    • 100
    • 100% 100%
    • undefined

    Description

      Goals

      This will be the initial GA release of an alternate collector to fluentd. The first phase will provide a supported
      alternative for some of the features that are available to customers using fluentd. We do not expect to have full
      feature parity with the this release:

      • Logging with a GA Release of Vector as an optional alternate collector
      • Smooth upgradable path from fluentd-based logging to Vector
      • Clear documentation for migrating from existing fluentd-specific API features.
      • Compatible API extended to handle the vector collector
      • Support arch: x86, arm, s390x, ppc64le

      Non-Goals

      • Swapping out fluentd for vector on upgrade; this is an opt-in choice due to feature differences

      TODO

      Motivation

      TODO

      Alternatives

      TODO

      Acceptance Criteria

      • Complies with viaq data model (vector vs. fluentd)
      • Supports outputs: elasticsearch, kafka, loki, cloudwatch
      • Comparable auth capabilities to fluentd for supported outputs
      • Verify switching between collector types without regression (except known or intended differences)
      • Verify compatible with a FIPS enabled cluster
      • Verify compatible with global proxy enabled cluster

      Risk and Assumptions

      TODO

      Documentation Considerations

      • Feature gaps
      • missing syslog support
      • missing fluentforward support
      • Metrics dashboard

      Attachments

        Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-2222 GA vector as the primary collector for logging (Phase 2)

          • 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

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-102 Provide GA Support for Vector with Elasticsearch for OpenShift

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • In Progress

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-111 Provide GA Support for Vector Collector with OpenShift Logging

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-114 Provide GA Support for Vector with Kafka for OpenShift

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          clones

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-1715 Preview replacing fluentd with vector as the primary collector for logging

          • 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 blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-1715 Preview replacing fluentd with vector as the primary collector for logging

          • 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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-2222 GA vector as the primary collector for logging (Phase 2)

          • 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 documented by

          Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-4067 GA vector as the primary collector for logging (Phase 1)

          • 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

          Activity

            People

              vimalkum@redhat.com Vimal Kumar
              jcantril@redhat.com Jeffrey Cantrill
              Ishwar Kanse Ishwar Kanse
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: