Please note that the following notes apply to the MySQL database version of telemetry collection.
This page does not apply to testing telemetry data collected since the end of January-2013.

This document will assume that the required prerequisite software is installed and configured correctly on the relevant computers.

Testing on a developer's workstation

Testing that a telemetry client is sending the correct telemetry in a development environment is a four step process. Since the release of telemetry may change, the placeholder [TEL_RELEASE] will be used to represent the release of telemetry being used. Please substitute the actual release for this placeholder in the process steps.

1) Install and start the local test store. The local test store is a MySQL database residing on the local host that where the collection library will store the testing telemetry samples. To install and start the local test store, enter the following command in a terminal window.

prompt> /lbt/telemetry/[TEL_RELEASE]/bin/test_store/admin_test install

2) Run a test using the telemetry client.

3) Check what is written in the local test store. Each release since r7 provides a stand-alone version of the telemetry exporter tool for exporting samples stored in a local test store. To start this tool and connect to the local test store, enter the following command in a terminal window.

prompt> /lbt/telemetry/[TEL_RELEASE]/bin/telexporter

Please read the help dialog to understand how to export the desired samples.

4) Stop and uninstall local test store. The telemetry database resides in the directory /tmp/telemetry. The contents of the /tmp directory are not guaranteed to be persist indefinitely. If the local test store is not uninstalled between tests, part or all of the database may disappear. This may result in a test failing strangely. To stop and uninstall the local test store, type the following command in a terminal window on the local host.

prompt> /lbt/telemetry/[TEL_RELEASE]/bin/test_store/admin_test uninstall

Testing on the Tucson test cluster

Testing on the Tucson test cluster is a little easier since the test cluster has its own test store. Testing is only a two step process. Again, since the release of telemetry may change, the placeholder [TEL_RELEASE] will be used to represent the release of telemetry being used. Please substitute the actual release for this placeholder in the process steps.

1) Run a test using the telemetry client.

2) Check what is written in the test cluster store. Each release since r8 provides a stand-alone version of the telemetry exporter tool for exporting samples stored in the test stores. To start this tool and connect to the test cluster store, enter the following command in a terminal window on any computer part of the lbto.arizona.edu domain.

prompt> /lbt/telemetry/[TEL_RELEASE]/bin/telexporter badwater

Please read the help dialog to understand how to export the desired samples.

-- TonyEdgin - 27 Aug 2009