Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Cloud_Edition_button.webp

This page provides examples of what your input and output data might look like in your stream’s Data aggregator after your stream has been run at least once. These views will help you with troubleshooting and validating the data transformation process within the Data aggregator.

Here are some example streams that use the Data aggregator function. These are pre-configured streams that can be found and run executed from the Usage Engine platform for training learning purposes. See https://infozone.atlassian.net/wiki/x/rMB3 for more details.

Input data

The input data window shows the raw data received by the Data aggregator from the previous functions in the stream. This view can help you to verify the incoming data that will be used for aggregation. There are two tab views, Table and Tree.

Data_aggregator_input_table.png

Data_aggregator_input_tree.png

Output data

The Output data shows a subset of the aggregated data. It will show the data grouped and summarized based on the criteria set in the aggregator's configuration, for example, total consumption, number of occurrences, or maximum values for each group. It will allow you to inspect the final aggregated data and verify that the function has correctly applied the aggregation rules based on the configuration. There are three tab views, Table, Tree and Log.

Data_aggregator_output_table.png

Data_aggregator_output_tree.png

Metadata

You can view and access the following metadata properties of aggregated sessions by using the Script function. Use the meta-variable as mentioned in https://infozone.atlassian.net/wiki/x/SI94There may be instances where you want to apply certain rules to aggregated data, such as applying a discount or adjusting values based on specific business rules. You can achieve this by using the Script function. If you need to reference metadata from aggregated sessions, such as the number of records or timestamps, you can access it using the meta-variable as described in Supported Variables/APIs.

Info

Example- metadata for an aggregated session

Code Block
{"origin":"Data_Aggregator","count":7,"flushType":"TIMEOUT","firstEvent":"2022-04-08T17:35:53.239Z","lastEvent":"2022-04-08T17:38:17.315Z","lastCall":false}

Property name 

Description

count

Number of aggregated records

flushType

The reason for the session being flushed out. Shows any of the values: ALL_FILES, EACH_FILE, TIMEOUT, and CONDITION. During preview, the value will be empty.

firstEvent

Date and time of the first aggregated record in the session

lastEvent

Date and time of the last aggregated record in the session