Data Stream Analyzer

This monitoring tool allows you to analyze tracker parameters and their attributes as a flow. Using it, you can focus on the necessary devices and data of your interest:

• Select only the trackers and parameters you want to focus on.

• Access the latest known values (excluding nulls) or all recent values (including nulls).

• Track how data is enriched, recalculated, and what outputs are generated.

• Review TCP dumps and node logs for in-depth troubleshooting.

• Compare data across different sources for deeper insights.

It’s like having an X-ray for your data, tailored to show exactly what you need!

To access the Data Stream Analyzer tool, select IoT Logic from the platform menu and click .

Let's dive deeper into all the possibilities and functions you can find here.

Main parameters

In the top menu, are gathered the main controls for the monitor tool.

Data flow: This control allows you to choose from a dropdown list of flows created in your user account. This is the main grouping parameter, so you'll be able to search for devices and attributes that belong to the chosen flow only.

Mode: There are two modes for the monitor tool, and the view of the tool depends on the chosen mode.

• Table view: This mode shows decoded data from trackers in a tabular format.

• Flow logs: This mode shows overall logs, TCP dumps, and node logs in the chosen flow. It will be added in the next iterations.

The options above are unactive at the moment and contain the default selections. They will become available with further enhancements of IoT Logic functionality. Stay tuned!

Clicking the Close button will return you to the main IoT Logic screen.

Now let’s take a closer look at the interface sections and the information available within them.

Table view

Top menu bar

The top menu contains the main controls for the table view.

Exclude null toggle: This setting allows you to switch between two data display modes:

• Off — Displays all values based on packets received from the device, including those where the selected parameter has null (missing) values. This mode provides a complete view of all packet data.

• On — Displays only the packets where information was actually received from trackers for the selected parameter, with valid, non-null values. In other words, it filters out incomplete data.

Depth: This control is responsible for the depth of history data and defines the range of recent data to display. For example, how many steps into the past we need to go through to show attribute and parameter values. The maximum is 12 steps into the past. You can choose how many steps you want to see and check how values change. For example, if you set depth=4, you will see values for three steps from the past [3], [2], [1] and the last received values [0].

Play/Pause: This button allows you to start getting updates of values into the table in real-time, or pause the updates.

Search value: This field is used to find a specific value from all parameters in the table. The maximum is 100 symbols to search. For example, if you're checking the work of events and looking for a specific one from a device which should be triggered, the searched value will be highlighted.

Export: You can export all logs using the export button to share information with other specialists. The information will be in JSON format to make it easier to read.

Devices and Attributes block

The left menu block contains a list of trackers and attributes belonging to the chosen flow. To switch between lists, use the Devices and Attribute buttons on the top of the list. You may search devices by ID and attributes by their names.

You can select up to 10 trackers. Once selected, all attributes supported by these devices will be displayed, allowing you to choose any number to show in the table. Only attributes relevant to the selected trackers will be available.

Last attribute values table

The information about received values per chosen devices and attributes will be displayed in this table.

The table provides information in the following way:

• The table header row is a list of devices chosen for monitoring. These devices will become columns that show values from every device.

• Rows with attribute names will group data from the chosen attribute. The information collected in the chosen depth from this attribute per every tracker will be displayed below.
  The first column in rows under the attribute name with numbers is responsible for the depth of values. Where 0 is the current one, 1 is the previous one, and so on.

When you hover the mouse over any value, you will see additional data about when this parameter was generated by a tracker and when it was received by the platform:

Once new values are received from any tracker, they will be highlighted green for about 2 seconds. This way, you will see which parameter on which tracker was updated. Clicking on a device row will expand it, showing historical values limited by the set Depth.

Reading the table

Let’s interpret the table values using the case example shown on the screenshot above and see what insights we can get:

• Device #1Teltonika FMB001 is not returning any values. This may mean that the device cannot provide this particular kind of data. Check if there are any other attributes with values for this device, if no, make sure that the device is properly connected.

• Devices #2Teltonika FMB001 - #5Teltonika FMB001 are returning values consistently, indicating they are connected correctly. Their location can be determined using latitude and longitude attributes. Since their coordinates remain unchanged across several recent Depth levels, the devices are stationary. This is further confirmed by the moving attribute, which has a value of 0. Based on these observations, the data appears to be accurate and updated in real time.

• Device STARLINK provided values for only one Depth level, suggesting it was connected recently. The absence of values for the moving attribute likely indicates that this device likely does not have the relevant sensor.

Flow view - Coming soon!

The flow view does not have any specific controls, so we will explain the different components of this view.

• Node: This is a sequence map of nodes in the flow, where you can select a specific node for analysis.

• Node Logs: Once you select a node, its logs will appear under the node window.

• TCP Dump: In this section, you will find logs of the TCP server for trackers that belong to the chosen flow. You will see a dump of all trackers of the flow at once.t once.

You can export node logs and TCP dump using separate buttons in the appropriate sections so you can share information with other specialists for further investigation, troubleshooting and diagnosing not only trackers but the entire work process.