-
Epic
-
Resolution: Done
-
Major
-
None
-
Deploy Vector Collector as a GA offering (Phase 2)
-
False
-
False
-
NEW
-
To Do
-
OBSDA-108 - Distribute an alternate Vector Log Collector
-
Impediment
-
VERIFIED
-
0% To Do, 0% In Progress, 100% Done
-
undefined
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, ppc4le
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
- Supports outputs: elasticsearch, kafka, loki, cloudwatch, Elasticsearch 8
- Comparable auth capabilities to fluentd for supported outputs
- Enabled all functional tests for vector
Risk and Assumptions
TODO
Documentation Considerations
- Feature gaps
- Metrics dashboard
- clones
-
LOG-1795 GA vector as the primary collector for logging (Phase 1)
- Closed
- is blocked by
-
LOG-1795 GA vector as the primary collector for logging (Phase 1)
- Closed
- is documented by
-
RHDEVDOCS-4421 Vector as the primary collector for logging
- Closed
- mentioned in
-
Page Loading...
There are no Sub-Tasks for this issue.