The new event client features will be folded into the existing EventLogging extension in phases. Hopefully this will streamline code review and make it easier for us to manage the work. Each phase has its own task, since each phase will be its own patch. Things may change. For now, here is an outline of the phases:
- Phase 1 (Submit)
- Events are sent using HTTP POST to an EventGate instance
- Stream configuration data is loaded by the extension and used to format events
- Phase 2 (Sampling)
- Per-stream uniform sampling rate can be set by a stream configuration field.
NOTE: Non-essential patch phases (phase 3: stream CC-ing, phase 4: association controller) have been moved off the critical path and will be tracked as part of T259704: BUOD-KR1-Q2: Upgrade MEP clients to full release status.