summaryrefslogtreecommitdiffstats
path: root/dashboard/Prox_BM_BNG-QoS-4Port-1507804267386.json
diff options
context:
space:
mode:
authorPatrice Buriez <patrice.buriez@intel.com>2018-10-01 13:36:33 +0200
committerEmma Foley <emma.l.foley@intel.com>2018-10-03 10:37:43 +0000
commit7d5f15e9c93c12912cc9aa92279926a77d25ead7 (patch)
tree0a420ec8e0940c3d6f04dee8a723dc3a98df2fbf /dashboard/Prox_BM_BNG-QoS-4Port-1507804267386.json
parentf5ce0ae5452d65f4b8a56c6076ec83880d6d10a1 (diff)
Fix influxdb "field type conflict" error
JIRA: YARDSTICK-1457 Field types must be consistent across points in a measurement, otherwise influxdb rejects newer points with "field type conflict" error. This error was faced when "theor_max_throughput" field, meant to be assigned as a float from "TxThroughput" sample, was instead assigned as an int from initial value of theor_max_thruput variable. This especially occured for subsequent packet sizes, when theor_max_thruput variable was reset to its default int value. This fix changes the default value of theor_max_thruput variable to 0.0, and also makes sure that the default value for "Actual_throughput" field is consistently a float. Change-Id: If8d4f1297094709fe9657ab3e2b8adaad09815b2 Signed-off-by: Patrice Buriez <patrice.buriez@intel.com> (cherry picked from commit 2f4418798a3cf245f863a617410403f226062ac8)
Diffstat (limited to 'dashboard/Prox_BM_BNG-QoS-4Port-1507804267386.json')
0 files changed, 0 insertions, 0 deletions