Functions
To create streams, you can drag and drop the functions from the list on the left side into the canvas. As you can see in Usage Engine, these functions, which are available from the library, are categorized into Collectors, Processors, and Forwarders.
Collectors gather data from external systems or devices, except the https://infozone.atlassian.net/wiki/spaces/DAZ/pages/7857105 function.
Processors receive data from collectors or other processors and deliver data to forwarders or other processors for further handling.
Forwarders distribute data from the stream to external systems or devices, except the https://infozone.atlassian.net/wiki/spaces/DAZ/pages/7799309 function.
Note!
ZIP version
All collectors and forwarders support ZIP files up to version 4.5 (which includes Zip64 support for archives with 4GB+ files). There is no support for encrypted (password-protected) zips or symlinks.
The function icons include small arrows that indicate the direction of data flow and identify the function type. Collectors have an arrow on the right edge, pointing outwards. Processors have arrows on both edges indicating an incoming and outgoing flow. Forwarders have an arrow on the left edge, pointing inwards.
Note!
Beta status
Functions that are labeled as Beta can be used as well, but their user interface and functionality may change over time. Data loss or improper handling of data may also happen. Use them with caution.
Note!
Deprecated status
During the development of Usage Engine, functions are sometimes replaced by more flexible and extended versions. As the development teams strive to make transitions between versions as seamless as possible, the common approach is to migrate any existing configurations without the need of manual intervention. We use the term deprecate to indicate that the new version of a function most likely will not be completely backward compatible with the previous function.
The process of deprecation flows as follows:
A new version of a function is developed and ready for launch.
The old version is flagged with the word "Deprecated".
During a transition period, both versions co-exist, which allows sufficient time for migration.
The old version is removed from Usage Engine.
Configuration and preview
When you double-click a function, you open the window where you configure the function and preview data that is being collected, processed, or forwarded by the function.
All entries are autosaved. To check that your configuration is valid, click Preview to generate a preview.
Note!
Even if you do not click Preview before you exit a configuration, your entries are saved. If you want to clear all of the entries that you have added to a configuration, you need to delete the function and drag the relevant function to the canvas again to reconfigure.
After configuring any function in Usage Engine, clicking Preview enables you to view input and output preview data for that function. Across all functions in Usage Engine, the input and output preview data displayed depend on the function type. Refer to the table below for more information:
Function type | Preview data displayed |
|---|---|
Collector | Output |
Processor | Input and Output |
Forwarder | Input |
Preview data is displayed in three different views:
Table Displays data in a tabular format. Data is flattened or denormalized if needed so that even deeply nested JSON data can be viewed in the column/row structure.
Tree: Displays data in the JSON format.
Log: Displays data regarding info, warning, and error messages. The Log view is only available for output preview data and not for input preview data.
Note!
When the preview data is generated, a maximum of 10 records are displayed.
When you hover the cursor over the function icon upon opening the configuration, you can view the tooltip with a brief description of the function. Clicking the See documentation button directs you to the relevant documentation for the function.
Function descriptions
Take a look at the relevant section to find out more about each of these functions.