This is a script that will allow you to monitor all of the currently available stats from the WMI Query Daemon that installs with Traverse. You can write the data to a logfile, use the script to feed data to Traverse with the EDF API, or you can choose to do both.

The script is also a workable example of how to both create tests using the BVE API, as well as pushing a data set to Traverse using the EDF API within Perl.

The script is designed to run from the TRAVERSE_HOME/plugin/monitors directory, but can also be run from other locations on a Linux/Unix installation.

It has full command line help, but I will also provide some basic instructions for provisioning tests, and creating the cron job that will run the data feed.

Assumptions :
BVE and EDF API are running on 10.0.0.1, with the default ports.
WMIQD is running on 10.0.0.2, with the default port.

First, you will need to create a device in Traverse. For this example, we will assume it has been named 'Traverse WMIQD' and has the IP address of 10.0.0.2.

You will need to create the tests for this device next - the script will do this for you, with the proper command line options.

Code:

wmiqd-stats.pl --createtests --edfserver=10.0.0.1 --devicename "Traverse WMIQD" --deviceaddress "10.0.0.2"

Note : For test creation only, the edf<n> command line options are using for connecting to the BVE API to provision the tests.

Once this is complete, you will need to populate the tests with data. On a linux host, you can run this script every 5 minutes (the default) by using a cron entry similar to this (either as root via crontab -e, or in /etc/crontab).

Code:
*/5 * * * * root /usr/local/traverse/plugin/monitors/wmiqd-stats.pl --wmiserver 10.0.0.2 --devicename "Traverse WMIQD" --deviceaddress "10.0.0.2" --edfserver "10.0.0.1" --edf --log /usr/local/traverse/log/wmi-getstats.log

Note the use of --edf and --log. This will log the same data capture through EDF, and place it in the wmi-getstats.log file in your TRAVERSE_HOME/logs/ directory.

After two full polling cycles, all of your tests should have collected data. Be aware that the defaults set with the test creation may or may not be appropriate for your environment, and will likely need to be adjusted.