Original description from OSP-19942

OpenStack has the ability to collect logs via rsyslog and has the ability to transport that data via omelasticsearch plugin for storage. In the future an interface to writing logs into a central logging store is desired by customers in order to avoid segmentation of data. This goes against our unified observability vision.

The target data store is most like Loki, possibly via Vector into OpenShift Logging. Exposure of these logging bits for alerting and visibility is desired.

On the OpenStack side we need to determine how to collect data, which data to collect, resolution of the data, and how we'll transport the data securely to a central data store, and ultimately make the data visible.

TODO: identify data collection model, data transport, and data storage domain. Identify work task required. Target for OCP 4.14 in order to start allowing testing and support for RHOSP 18.0. Identify any items required for podified control plane interfaces as well as director-based solutions.

Updated description:

<TODO>

Feature Overview

< High-Level description of the feature ie: Executive Summary >

< Is Feature Back-portable? >

Goals

< Who benefits from this feature, and how? What is the difference between today’s current state and a world with this feature? >

Requirements

A list of specific needs or objectives that a Feature must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts.  If a non MVP requirement slips, it does not shift the feature.

(Optional) Use Cases

< How will the user interact with this feature? >

< Which users will use this and when will they use it? >

< Is this feature used as part of current user interface? >

Out of Scope

Background, and strategic fit

< What does the person writing code, testing, documenting need to know? >

Assumptions

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Customer Considerations

< Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

< Are there upgrade considerations that customers need to account for or that the feature should address on behalf of the customer?>

Documentation Considerations

< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >

< What does success look like?>

< Does this feature have doc impact?  Possible values are: New Content, Updates to existing content,  Release Note, or No Doc Impact>

< If unsure and no Technical Writer is available, please contact Content Strategy. If yes, complete the following.>

• <What concepts do customers need to understand to be successful in [action]?>

• <How do we expect customers will use the feature? For what purpose(s)?>

• <What reference material might a customer want/need to complete [action]?>

• <Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available. >

• <What is the doc impact (New Content, Updates to existing content, or Release Note)?>

Interoperability Considerations

< Which other products and versions in our portfolio does this feature impact?>

< What interoperability test scenarios should be factored by the layered product(s)?>