Example - Aggregated session data in JSON format This is an example of a JSON file sent downstream after a flush. | Code Block |
|---|
{
"timeoutAt": "2024-10-02T14:19:48.108Z",
"createdAt": "2024-10-02T13:19:48.108Z",
"sum_fieldX": 52,
"userIdgroup_fieldsA": 105,
"month_timestamp": "2024-09"
} |
"timeoutAt": "2024-10-02T14:19:48.108Z" This indicates the exact time when the system flushed the aggregated data. The data was flushed (sent downstream or processed further) based on a timeout at this specific timestamp. "createdAt": "2024-10-02T13:19:48.108Z" This marks the start time of the aggregation session, showing when the session was created. It indicates that this session ran for exactly one hour before the timeout occurred and the data was flushed. "sum_fieldX": 52 This shows that the aggregator has summed up the value in fieldX to 52 during this session 52 fieldX during this session. This could refer to any other fields configured in the aggregated field section in the function’s configuration. in configuration. unit of data being aggregated. "userIdgroup_fieldsA": 105 This could be any field that’s been used to group the data during aggregation. It can be set by selecting fields in Group fields in the function's configuration. This is the identifier for an entity associated with this aggregation. It shows which entity’s data was aggregated in this session. "month_timestamp": "2024-09" This field represents the aggregation period. It shows that the processed data corresponds to this is based on the date/time configured in Group fields in the function’s configuration. September 2024. |