Goals

• As an OCP user, I want Logging to manage the collection of events through the Logging Operator so that I don't have to maintain two completely separate components.
• As an OCP user, I want to forward events to another, external third party solution via the log forwarding API.

Non-Goals

Motivation

Currently, we ship a component called "eventrouter" as a separate deployment that scrapes events and logs them via STDOUT so that is gets pushed into the OpenShift Logging pipeline. Unfortunately, due to it being separate from Logging – it creates additional maintenance baggage for administrators since updates and everything else just gets more difficult.

Alternatives

Acceptance Criteria

Risk and Assumptions

Documentation Considerations

Open Questions

Additional Notes