Service limits and usage measurement

Stream Pipelines usage is measured by the number of events that the pipeline processes each day. An event is a record variation, which is a single change to a record that is published to Data Fabric.

A table row count does not represent the number of events. Each record change generates a new variation. Each variation that a pipeline processes counts as one event. For service limits and entitlements that are associated with the ION-S-DFP SKU, see the Infor OS Service Limits documentation.

All data that Stream Pipelines process counts toward the daily event volume, regardless of the data source. Included data sources are real-time events from Streaming Ingestion, data from Data Lake that the Initial Load capability processes, and data that batch ingestion methods ingest, such as the Batch Ingestion API and ION.

Service limits are licensing and entitlement limits that support usage measurement and capacity planning. Service limits are not technical limits that restrict Stream Pipelines processing. Stream Pipelines continue to process data when processed event volume exceeds the licensed event volume. You must ensure that usage remains within the licensed entitlement.

When estimating usage for licensing and capacity planning, base your estimates on peak daily event volumes, not averages. A single high-activity day can exceed the licensed limit even when the overall daily average appears low.