Monitor tool
A monitor tool allows you to check and analyze attributes and tracker parameters in the flow. Using it, you can choose only the necessary trackers and parameters you want to see, check the last received known values (without null values), and any last values (including null). You can check how data is enriched and recalculated, and what you can get on out. Furthermore, you can check TCP dumps and node logs. It's like you have an X-ray, but you can choose what exactly you want to see and even compare data from sources between each other.
Let's dive deeper into all the possibilities and functions you can find here.
Main parameters
In the top menu, there are two main controls for the monitor tool.
Select 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.
How about to take a closer look at each mode and the information available in them?
Table view
Top menu
The top menu contains the main controls for the table view.
Depth: This control is responsible for the depth of history data, i.e., 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 4, 3, 2, 1, and 0 for all chosen parameters in monitor.
Play: This button allows you to start getting updates of values into the table. So you will see how values are changing and updating in real-time.
Pause: This button allows you to pause getting updates of values to take a break and analyze the already received information.
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.
Close: This button closes the monitor and opens IoT Logic main window again.
Left part
The left part 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.
Additionally, you can choose several trackers and attributes to be shown in the table using checkboxes.
The checked trackers and attributes lists will filter each other. For example, if you choose some trackers first, you will get a list of attributes available for all these trackers at once. And vice versa, if you choose some attributes first, the list of trackers will show only devices that support such attributes according to their protocol and are integrated on the platform.
Table view monitor
The information about received values per chosen devices and attributes will be displayed in the "last attribute values" table.
The first thing the monitor will ask you is what to show in the table.
All values: This option will show values based on all received packets from a device. If there were no values from the chosen parameter in the packet, it will be null. This option will show you the depth of all received packets from trackers.
Valid only: This option will show only valid, non-null values. This option will show information only for packets where values were received from trackers.
The table provides information in the following way:
The first 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.
Let's read the example from the screenshot above:
The last latitude from device 17357839171225 was -76.97410, from device 860962852931682 was 44.04177, and from device 863932291743680 was -35.92661. Devices 452672481451077 and 304144310199137 didn't provide any valid latitude in their last packets.
The previous can_raw12 from device 17357839171225 was 6d ef de. Device 304144310199137 didn't provide any information.
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.
Flow view
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.