forked from tumi8/vermont
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement flowKey/nonFlowKey aggregation behaviour
The implementation now respects the configuration of flowKey/nonFlowKey for fields in the aggregator. Default aggregation behaviour for nonFlowKey fields, as defined in 4.3.3 RFC 6728 and 5 RFC 7012, is to take the value from first packet/sample/flow. This configuration behaviour is seen in other ipfix/netflow implementations from Cisco/Juniper/etc Fixes: tumi8#112
- Loading branch information
Showing
5 changed files
with
18 additions
and
97 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters