Last phase of data not posted in InfluxDB

[guptapranay]

Hi Team,
I am currently working with Artillery InfluxDB and Grafana integration. And found out that, there is a mismatch in the total number of requests been displayed in Grafana & Influx against number of requests generated in artillery.

The issue here is: The Last phase of data is never pushed to influx DB. This is probably a defect. I tried to include Pause at last, but it did not work.

Could someone correct this push newer version in npm? - Look the logs below: For last 17 request, data did not pushed to InfluxDB.

1 metrics reported to InfluxDB.
Report @ 20:03:33(+0000) 2019-11-15
Elapsed time: 1 minute, 0 seconds
  Scenarios launched:  68
  Scenarios completed: 76
  Requests completed:  143
  RPS sent: 14.44
  Request latency:
    min: 10.9
    max: 168
    median: 57.5
    p95: 88.2
    p99: 134.5
  Codes:
    200: 3
    201: 67
    404: 73

1 metrics reported to InfluxDB.
143 metrics reported to InfluxDB.
Started phase 3, duration: undefineds @ 20:03:34(+0000) 2019-11-15
Report @ 20:03:36(+0000) 2019-11-15
Elapsed time: 1 minute, 3 seconds
  Scenarios launched:  4
  Scenarios completed: 12
  Requests completed:  17
  RPS sent: 4.94
  Request latency:
    min: 14.3
    max: 385.8
    median: 42
    p95: 282.9
    p99: 385.8
  Codes:
    201: 5
    404: 12

All virtual users finished
Summary report @ 20:03:36(+0000) 2019-11-15
  Scenarios launched:  482
  Scenarios completed: 482
  Requests completed:  964
  RPS sent: 15.3
  Request latency:
    min: 10.4
    max: 385.8
    median: 61.5
    p95: 94.3
    p99: 120
  Scenario counts:
    Get list of all employees and fetch employeeId for request chaining to other api: 482 (100%)
  Codes:
    200: 6
    201: 482
    404: 476

[Gregory W. Smith II]

@guptapranay

Thanks for bringing this to our attention.

Not sure what the issue is with the reporting to Influx. Maybe a bug in our implementation or some other issue.

This project only has the resources to address major issues at this time, however, we always consider the impact of all bugs.

Thanks!

[guptapranay]

Hi @gwsii ,

Thanks for replying back. If possible, it would be great to have a fix. Since there will always be a mismatch between the number of requests that happened and the actual getting recorded in influxDB. This will majorly give incorrect performance parameters in reporting.

But surly, I would wait for the updates. :)

[guptapranay]

Is there any update on this?