Sierra Wireless - AirVantage

Top AVEP features in Oct'13 release: 4. System troubleshooting


Troubleshooting a problem We all know too well how annoying it can be to have an embedded M2M application that seems to be working OK, but for which you cannot manage to retrieve the actual data that it supposed to be sending.

There are several reasons why you may have such a problem and usually what you are interested in is knowing whether the data has actually reached AirVantage M2M Cloud or has been stuck before due to a bug in your embedded application, a problem with the network, …

This is why we have worked on making it much easier to display detailed system information right from the Monitor activity.

New Timeline View

Timeline View

When you are browsing the details of a system in the Monitor activity, you have access to a new Timeline View that displays, in a very visual way, all the history of all the exchanges between your embedded system and the server.

It is now very easy to see if a communication actually happened when it should have, and to see all its details (data that has been sent, with which protocol, etc.) by just clicking on the corresponding entry in the list of events.

New Data History View

Data History View

You are probably aware of the aggregated data API that allows you to retrieve consolidated data history for a specific system when you want, for example, the average temperature of your refrigerator, on an hourly basis, for the last 30 days. This API is pretty simple to use, but sometimes what you want is just very quickly troubleshoot a system on the field, and it’d be convenient to be able to display historical data right from the AirVantage Enterprise Platform. Well, guess what? We’ve added just that!

You can now access a Data History View from a system’s details. This view allows you to create your own charts, for the data you’re interested in (applicative data, or device-related data such as RSSI, bandwidth consumption, …), with the aggregation function(s) of your choice (average, minimum, maximum, etc.).

Photo Credit: jurvetson via Compfight cc

comments powered by Disqus