Follow

Missing Metric Data From Online Meter

NOTE On October 11, 2016, BMC released Meter Version 4.4.1 which changed the name of the meter from boundary-meter to truesight-meter. This article reflects the change. If you are using a meter version prior to 4.4.1, then you will need to reference boundary-meter instead of truesight-meter in the operations discussed in this article.

Run the following command from the command-line or shell prompt...

On Linux : truesight-meter -d2

On Windows (from the TrueSight directory, normally in Program Files) : truesight_meter.exe -d2 

This will generate an http_log.txt file (in the TrueSight Pulse meter home directory) capturing the API calls being made to TrueSight Pulse by the meter including the measurements (metric data points) being posted to the API. 

The sample below captures a measurement that was posted, the timestamp for when it posted, whether it was successful (Http Code) and the actual data.

Timestamp : Wed May 13 20:17:48 2015Http Code : 200
URL : https://api.truesight.bmc.com/v1/measurements
Body : [["WIN-MHQJQKG22HM","MEMU",0.460917,1431548266],["WIN-MHQJQKG22HM","REQ_COUNT_SUMMARY",0,1431548268],["WIN-MHQJQKG22HM","REQ_RESP_TIME_SUMMARY",0,1431548268]]

This can be very useful in determining whether there is a blocking issue (Http failures) with the Meter posting data to TrueSight Pulse.

Have more questions? Submit a request