Where to write the IPFIX data.
The session to use.
Add all records from a MesageReader to this ExportStream
Adds record to the output stream.
Adds record to the output stream. Prior to adding record,
adds any Templates used by record that have not
been seen before.
If record appears to contain either information element
meta-data or template meta-data, then the record is ignored if
the Export Stream is exporting that meta-data itself (see the
describeElements and describeTemplates variables).
Adds template to the output stream unless the template has
already been seen by this stream.
Adds template to the output stream unless the template has
already been seen by this stream.
If template appears to be a template for describing either
information element meta-data or template meta-data, then the
template is ignored if the Export Stream is exporting that
meta-data itself (see the describeElements and describeTemplates
variables).
Flushes and closes the output stream.
Gets the current callback invoked when bytes are written to the outputStream as an Option.
Gets the current callback invoked when bytes are written to the outputStream as an Option.
1.3.1
Sets a callback to be invoked when bytes are written to the outputStream.
Sets a callback to be invoked when bytes are written to the outputStream.
1.3.1
Whether to export option records that describe private enterprise information elements.
Whether to export option records that describe private enterprise information elements.
If this is true, ExportStream generates these records itself and any
such records given to the add method are ignored. The records are
generated as-needed and may appear anywhere in the output.
If this is false, input records that describe private enterprise
elements are written to the output without ExportStream examining their
content. This may result in duplicate descriptions in the output.
In either case, ExportStream attempts to use the same template ID for the element metadata template as seen in the incoming data.
Whether to export option records that include the name and description of each template.
Whether to export option records that include the name and description of each template.
If this is true, ExportStream generates these records itself and any
such records given to the add method are ignored. The records are
generated as-needed and may appear anywhere in the output.
If this is false, input records that describe templates are written to
the output without ExportStream examining their content. This may
result in duplicate descriptions in the output.
In either case, ExportStream attempts to use the same template ID for the template metadata template as seen in the incoming data.
Returns the template ID for the options template used by records that describe private enterprise information elements.
Returns the template ID for the options template used by records that describe private enterprise information elements. Returns scala.None if no ID has been assigned.
Sets the template ID for the options template used by records that describe private enterprise information elements and exports the template to ensure the template ID is reserved.
Sets the template ID for the options template used by records that describe private enterprise information elements and exports the template to ensure the template ID is reserved.
IllegalTemplateRecordException when tid is illegal or
is already in use by the session
RuntimeException when tid cannot be used for the
template because the template already exists
Flushes any data currently sitting in memory.
The set of templates that have been exported
Callback to generate a timestamp
Returns the file channel to which the data is being written
Returns the number of data records added to the stream.
The session to use.
Returns the number of templates added to the stream.
Returns the template ID for the options template used by records that describe templates.
Returns the template ID for the options template used by records that describe templates. Returns scala.None if no ID has been assigned.
Sets the template ID for the options template used by records that describe templates and exports the template to ensure the template ID is reserved.
Sets the template ID for the options template used by records that describe templates and exports the template to ensure the template ID is reserved.
IllegalTemplateRecordException when tid is illegal or
is already in use by the session
RuntimeException when tid cannot be used for the
template because the template already exists
ExportStream supports writing IPFIX templates and records to a file.
The caller creates an ExportStream instance with an output channel and an associated Session. The caller may then add Templates or Records to the ExportStream, and the ExportStream writes the IPFIX data to the output file.
Since the Session is part of the ExportStream's constructor, all IPFIX Messages in the stream use the same observation domain.
By default, each exported IPFIX Message uses the current time as its timestamp. Set the
makeTimestampvariable to change this behavior.By default, an ExportStream adds an options record to describe each Information Element that is not part of the standard information model, and ExportStream ignores any such options records in the input stream. Set the
describeElementsvariable tofalseto change this behavor, and useelementDescriptionTIDto view or set the template ID used by these records.By default, an ExportStream adds an options record to describe each Template it exports, and ExportStream ignores any such options records in the input stream. Set the
describeTemplatesvariable tofalseto change this behavor, and usetemplateDescriptionTIDto view or set the template ID used by these records.NOTE: When copying data from an IPFIX input stream, ExportStream may change the order in which templates and records appear---specifically, templates that appear after a record in the input may be written before that record. ExportStream is aware of the Meta-Data Options templates and records that describe Information Elements and Templates, and, when ExportStream is not creating and exporting those items itself, those templates and records are copied from the input and written to the output in the required order. The user may call flush() to ensure some items appear in the output before others. The authors of this package may need to consider providing some way for the users to know when to call flush(), such as adding a callback methods to be invoked when a new IpfixSet is read.