About the Favorites Tab

Use the Favorites tab in the Test Session window to add, view and customize reports tab and test measurements while the test is running. A second set of Favorite measurements can be added on the “Favorites 2” tab. Favorite 2 measurement feature allows users to do generically like Favorite measurements, it will be up to the user to select which measurements go onto the Favorites 2 tab.

NOTEs: The Favorites tab is persistent (present even when the test is not running), blank until you add the required test measurements, which are saved.

HTTP POST of Favorite Measurements:

Favorites tab components:

Add (+) / Delete (-)

Click Add (+) to select a measurement to add to the Favorites list.

NOTE: From the Reports tab, you can Right-Click a measurement to Add to Favorites.

The Elapsed Time and Test Iteration (if applicable) measurements are automatically displayed/included in Favorites list. You cannot add or delete them.
Measurements available for selection in the Measurement Criterion editor are not guaranteed to be reported in the running tests. These editor lists include all the reported measurements, with some additional measurements that may not be reported in some configurations. They do not cover Sub-total measurements (Per-session/Per-DMF/Per-Bearer) that are created dynamically when the tests tun.
From APIs you are able to add measurements that may not exist, as we only validate the syntax of the name, tab, subtotal, etc. However, we will provide an indication if the measurement is "Not found in test" or "Not reported yet" or has values.
A measurement that was added via the GUI can exist in a Favorite configuration even after it has been removed from a Report measurement tab. However, we will provide an indication if the measurement is "Not found in test" or "Not reported yet" or has values.

Click Delete (-) to remove a measurement from the favorite list. The Delete button becomes available when you select a measurement row.

You may add a specific measurement definition from the Select Measurement to add window: to the Favorites tab just once for each specific instance, where each instance is uniquely identified by the View (Summary vs Test Case), Tab (test case dependent), mode (Cumulative vs Per-Interval), and/or subtotal tab.

For example, your Favorites list may include all of the following:

Summary::L3 Client::Total Packets Sent
Summary::L3 Client::Total Packets Sent (P-I)
Summary::L3 Client::Total Packets Sent::DMF_0
Summary::L3 Client::Total Packets Sent::DMF_1
ts0::tc1::L3 Client::Total Packets Sent::DMF_0

NOTE: You are not allowed to add a measurement instance already added.

See also Adding Favorites on the Cross-Reference tab.

Up/Down Arrow

Select one or more measurement rows and click Up/Down arrow to order the measurements as required.

Add to QuickList

Click to add the selected item to the QuickList.

Display QuickList

Click to display the Favorites Measurement QuickList window populated with items you added.

Interval Navigation Buttons

Use the interval navigation buttons to quickly shift the displayed intervals to a different stage of the test.

HTTP Post

This feature allows for live reporting of the configured Favorite Measurements to an external server via HTTP POST in JSON format. An “HTTP POST…” button and the tooltip provides a sample view of the JSON that would be sent:

All of the fields prefixed and suffixed with _ are fixed, (in bold in the example below) and based on the configuration or TAS calculated items. They are header attributes and they should always be reported. The remaining fields are the list of Favorite Measurements and their values. When enabled the TAS will HTTP POST a message every interval with the current values for the measurements.

Example :

{
"_target_": "target from configuration","
"_test_": "name of the test session","
"_run_": "2020/11/04 16:14:44__RID-1","
"_interval_": 44,"
"_elapsedTime_": 220,"
"_actualTime_": 1604528391188,"
"_iteration_": 1,"
"L5-7 Client|Advanced::Sess_0::Command Transaction Count": "164","
"L5-7 Client|Advanced::Command Transaction Count": "490","
"L3 Client::Total Bytes Sent": "1301470","
"L3 Server::Total Bytes Received": "1301470","
"L3 Server::Total Bytes Sent": "16968214","
"L3 Client::Total Bytes Received": "16968214""
}

First you must enable the feature by at least setting a URL and a target string:

The URL must be http or https, however https will only work if the server has an officially signed-by-public-CA certificate.

We expect that this feature will be used inside a small network sandbox, lab or corporate network, and only require insecure HTTP. When using HTTPS, we currently do not provide any way to install certificates. To use HTTPS, you will have to use a SSL Certificate signed by one of the main/default CA providers that comes with standard Java8 Java.

The Target is required and expected to be used to uniquely identify the bucket/table/location to send the JSON to on the URL. The Username and Password fields are provided in case Authentication is required and it will be via HTTP Basic Auth.

The other built-in JSON fields reported:
_test_ is the test session name
_run_ is the test run’s unique identification, same that can filter on results website, made up of <START_TIME>__RUN-<RID>
_interval_ is the current interval number
_elapsedTime_ is the elapsed time of the test at the interval
_actualTime_ is the actual time in MS since EPOC.
_iteration_ is the test session current iteration, only matters for multi-iteration tests.

If the TAS has any issues sending the HTTP POST, it will log warnings to the Run Log and RT Logs. If the HTTP POST fails more than 2 times it will stop sending the POST. A successful HTTP POST is when the TAS receives a 2XX response. Any other response is considered a failure.

If you have configured the HTTP POST URL/Target and you did not receive any warnings , that means the TAS did send it. You can confirm this (and the contents) with Wireshark.

Run log messages :

Run Log Warnings (Failed login situation):
11/18 11:44:10.395:TAS: HTTP POST Response: 401:Unauthorized
11/18 11:44:14.125:TS(Coast-11.84[0]): P[0]: CPUs nominal 3-interval-avg%=72
11/18 11:44:15.413:TAS: HTTP POST Response: 401:Unauthorized
11/18 11:44:20.200:TAS: HTTP POST Disabled due to too many errors

RT Log Warnings (overall bad response from server situation):
sms 2020-11-18 12:02:02 Warning Operations Run Id(1): HTTP POST failed: java.net.SocketException: Unexpected end of file from server
sms 2020-11-18 12:02:07 Warning Operations Run Id(1): HTTP POST failed: java.net.SocketException: Unexpected end of file from server
sms 2020-11-18 12:02:11 Warning Operations Run Id(1): HTTP POST Disabled due to too many errors.

Read the KPI Pipeline to Telegraf to learn how to send measurements to a Grafana Dashboard via Telegraf.

Hide Zero's

Along with the second Favorites we have added the ability to only show the measurements that have reported a non-zero value at least once. This is done using a check box “Hide Zero’s”:

By default, the “Favorites 2” tab will enable Hide Zeros. By default, the “Favorites” tab will disable Hide Zeros.

This option is not persistent, if you change it in the GUI, it will not be saved with the test session. Also the end of test reports will not Hide Zeros, they will show all measurements.

When editing the contents of the Favorites tabs, you may want to make sure you uncheck the option. And in some cases you will be forced to uncheck it. Moving and Removing Favorites while Hide Zeros is enabled, will not be supported.

Until you start the test for the first time, this option will have no affect. Once you start the test, all measurements will disappear until they report at least one non-zero value.

Current Limitations :
#1 Hide Zeros is not available in Tex
#2 Hide Zeros is not applied in end of test results.
#3 Subtotal measurements will be shown/hidden based on the parent Measurement, if the Parent (Total) measurement reports non-zero, all subtotals for same parameter measurement will show up. If you just put 1 subtotal in the favorites and HIDE Zeros, it can show up with 0's because the parent measurement reported a non 0 value. (i.e. if just one subtotal reports non-zero the parent by logic will report non-zero)

Saving the Favorites List

In Test Session

The Favorites tab items are associated with the test Session and are automatically saved when you save the Test Session.

The Favorites tab items set when a Test Session has already started are saved in the running Test Session. If you close the Test Session window and then reconnect to the test, the favorites list will revert to the list that was in effect when the test was started.

NOTES:

If you modify the Favorites tab items while a test is running and disconnect from the test, the Favorites tab items are lost.
If you modify the Favorites tab items while a test is running, and save the Test Session, the Favorites tab items are saved to the Test Session in the library, but are not saved to the running instance of the test session on the TAS. Hence, if you disconnect the Test Session and then reconnect, the Favorites tab items are not available.

In XLS/CSV

The items in the Favorites tab are also saved to XLS and CSV reports (see example), and is the first tab/section of the report. The new “Favorites 2” tab will be reported in the end of test .xls and .csv formatted reports:

Favorites 2 table will not be shown in TeX.

See Report Formats

NOTE: Only the Favorites tab items that are already present when you click RUN button are saved to end of Test Results. Any changes made while the test is running are temporary in the GUI (which may be saved to the Test session for next run).

Learn more about:

Learn how to: