The new service release comes with improvements for managing your connection, and various minor bug fixes.
Additionally to the Metrics view, we have now introduced a Log entries view.
This view will help you as a developer to search for specific log entries, and thus, to hunt for bugs and messages, which failed to reach their destination.
How it works
At the Metrics tab you can decide which log entry you need to trace.
The Log entries view allows you to get more insights in your connections.
Start by enabling the logging for one hour. The service will automatically renew the expiration date each time you have a look at the logs.
This view does not only contain a list of the latest log entries for the connection, but also allows a full-text search on all log entries, and to add filters for different fields of the log messages.
If you need more details about a specific log entry, simply click on it.
You can reset the values captured so far, to more easily track a specific type of event, telemetry data, message, or response. Also, in case a real device is configured to use the connection, check the box Refresh automatically.
Please note, that we will only maintain a restricted number of log entries. Thus, older entries will be replaced by newer entries. Therefore, this list of logs might be incomplete.
If you are interested in one particular message, you should block all other messages, to make sure, that your desired message shows up in the list.
Currently, it is not possible to change the duration for which logging will be enabled.
Logging will not cause any costs itself. Note however, that all requests and all responses (e.g. retrieving the log entries) used in the UI are counted as transactions, and are reported for billing purposes.