-
Notifications
You must be signed in to change notification settings - Fork 321
AggregateLast
AggregateLast — Click element; lets through last packet per aggregate annotation
AggregateLast([KEYWORDS])
Ports: 1 input, 1-2 outputs
Processing: push
Drivers: userlevel
AggregateLast forwards only the final packet with a given aggregate annotation value. All previous packets with that aggregate annotation are emitted on the second output, if it exists, or dropped if it does not.
The output packet will have EXTRA_PACKETS_ANNO, EXTRA_LENGTH_ANNO, and FIRST_TIMESTAMP_ANNO set to the values reflecting the total volume of the aggregate.
Keyword arguments are:
- NOTIFIER — The name of an AggregateNotifier element, like AggregateIPFlows. If given, then AggregateLast will output a packet when the AggregateNotifier informs it that the packet's aggregate is complete. This can save significant memory on long traces.
- STOP_AFTER_CLEAR — Boolean. If true, then stop the router after the 'clear' handler is called and completes. Default is false.
- clear (write-only) — When written, AggregateLast will output every packet it has stored and clear its tables. This is the only time AggregateLast will emit packets if NOTIFIER was not set.
AggregateFirst forwards the the first packet with a given aggregate annotation value, rather than the last packet. It has significantly smaller memory requirements than AggregateLast.
Only available in user-level processes.
AggregateFirst, AggregateIP, AggregateIPFlows, AggregateCounter, AggregateFilter
Generated by click-elem2man from ../elements/analysis/aggregatelast.hh:8 on 2017/10/17.