Nighthawk fortio's output is discrepant then real fortio's output #514
Description
Description
Nighthawk's fortio transform output is different than real fortio output for a few fields.
Nighthawk's Output
{
"Labels": "",
"RequestedQPS": 5,
"ActualQPS": 4.9999995930000329,
"ActualDuration": 5000000407,
"NumThreads": 100,
"DurationHistogram": {
"Count": "25",
"Data": [
{
"Start": 0.024088575,
"End": 0.024088575,
"Percent": 0,
"Count": "1"
},Fortio's Output
{
"RunType": "HTTP",
"Labels": "test",
"StartTime": "2020-09-08T16:29:19.35507+05:30",
"RequestedQPS": "100",
"RequestedDuration": "5s",
"ActualQPS": 59.9799880886016,
"ActualDuration": 5101701580,
"NumThreads": 8,
"Version": "1.6.8",
"DurationHistogram": {
"Count": 306,
"Min": 0.114543168,
"Max": 0.436206912,
"Sum": 40.422087638,
"Avg": 0.1320983256143791,
"StdDev": 0.03333137761133907,
"Data": [
{
"Start": 0.114543168,
"End": 0.2,
"Percent": 97.38562091503267,
"Count": 298
},As can be seen
- RequestedQPS is an integer but should be a string.
- Dataentry.count, Sizes.count, HeaderSizes.count is a string but should be an integer.
Expected Behaviour
Nighthawk Output should be similar to Fortio's Output.