Move Notification to Sample Conversion Into Sample Pipeline
Currently we have a group of extensions that produce samples from a collected notification in the collector service. We should push this conversion into the pipeline and instead of describing separate pipelines in pipeline.yaml, we ought to describe the meters that constitute the pipeline. This includes describing what notifications are of interest (event white-list) and what attributes from that notification are relevant for a sample, along with what transformations need to occur on the sample object created from the attribute white-list. This can be implemented by repeating the notification for each applicable meter definition.
It may even be appropriate to call this a meter pipeline going forward, since that is the function of the samples it produces (goes to a Meter collection or table).
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Thomas Maddox
- Direction:
- Needs approval
- Assignee:
- Thomas Maddox
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Thomas Maddox