Configuration
Last updated
Last updated
This section explains each of the properties in the configuration blade.
Collection
This associates the Agent to a specific Collection (default to that of the current Data Stream).
Refer to Collections and Stream Hosts to understand more about Collections.
Type
The buffer size can be defined by:
Time - a unit of time, i.e. unit x size
Count - a number of events, i.e. size
Count with Delay - number of events PLUS a delay, i.e. size plus (unit x delay size)
Unit
The units of time options to define the buffer size are Days, Hours, Minutes, Seconds, Milliseconds, Microseconds, or Nanoseconds (applies to Time and Count with Delay types only).
Delay Size
The size of the delay (applies to Count with Delay type only).
Size
The size of the buffer.
This feature subdivides the buffer based on an asset identifier. The behavior depends on the window type:
Time: at the end of the specified time window, events are pushed in a buffer per identifier (in the order in which the identifier was first received during the period)
Count / Count with Delay: buffer x events per identifier, where x is the window size
Enable
Tick to create individual buffers, using the specified attribute as an identifier.
Partition By
The identifier attribute from the input payload by which the buffer should be partitioned.
This feature behaves differently depending on the window type:
Time: ignore duplicated events within the specified time window
Count / Count with Delay: wait for x unique events, where x is the window size, ignoring duplicated events
Enable
Tick to ignore duplicated records within a buffer, based on the specified attribute.
Distinct Attribute
Events with this attribute duplicated will be ignored until the next batch is begun.
If using either the Count or Count with Delay type and the possible values for the distinct attribute are less than the window size, the buffer will wait indefinitely.
Before configuring the Transformation, please ensure that its input endpoint is connected to a parent Agent which will be sending data to it.
Input
This endpoint is used to receive data from the parent Agent.
Output
Events received from the parent Agent are buffered and then made available to this endpoint.
