fortio v0.6.2

Changes since v0.6.1: #82 to fix #75

• Support for exact number of calls

If you set RunnerOptions.Exactly to any number, that exact number of calls will be made, and without additional warmup - it will still try to reach the target QPS but if the service is slower it will take the time it will take

On the command line this mode is selected using -n num (this replaces/extends the former grpc ping count flag)

• Adding the exact # option to the UI as well

Set the requested duration string to be the expected number of calls in that case

fortio v0.6.1

Mostly bug fix/tweak from v0.6.0:

#80 and #81:

Fixed the fortio/data/index.tsv so it works with google cloud storage transfer
https://cloud.google.com/storage/transfer/create-url-list
(you can backup all the results to google cloud storage)

Added a fortio redirect listening on port 8081 by default (changeable using -redirect-port) which will redirect to the https version of the incoming URL (meant to be used through an ingress, otherwise you will create a loop/error)

fortio v0.6.0

Pretty big changes in the stats/histogram in this release! (#77)

• Adding an extra <=0 bucket and changing bucket interval definition

• Fixed the cumulative percentile graph to be flat between gap and draw until the end of the interval and not the mid point

• Add support for RecordN to record N instance of same data point

• Delay can now also be a list of probabilities

eg
delay="10ms:20,20ms:10,1s:0.5" for 20% 10ms, 10% 20ms, 0.5% 1s and
69.5% 0 delay

• Allow optional % at the end of the percentage probability (it helps self documenting the feature)

• Split export and calc percentile(s)

calculate the percentiles after export (scaled data, calculated
cumulative percentage etc…)

Also in this release

• #71 Increased coverage from 66% to 82% with many core files as near to 100% as possible: found and fixed a synchronization/abort bug as a positive side effect.

• We are now mentioned in

• #62 Fixes to fortio report mode to only serve .json and returns 404s. TSV index/export. Only expose .json files, create our own index for directory. Added CORS header so json data can be downloaded anywhere.

• #65 Configurable timeouts and histogram at different offset/resolution merging support.

fortio v0.5.2

Happy New Year 2018 🎉

Changes since 0.5.1:

#64 (fix for #63)

• Fortio now compiles and runs on Windows (go get'able)

• Now uses separate channel to interrupt runs

• Now can interrupt specific/correct run for each window/UI

• Allow save+json to both work together

• Changed the signal handling to be fully correct

• ^C interrupts all outstanding runs (while the UI can interrupt 1 (from each run window) or all (from the main page) depending on parameter)

• Added windows compile check to the build

• #61 stats package can merge histograms from different ranges (thanks olimpias for the contribution!)

• #67 Changed JS style/format to match standardjs.com

• #68 Fixed 2 UI bugs related to cases where no percentiles are requested/present in the json result (in making the title for single graphs, and in getting the data for multi graphs)

fortio v0.5.1

Changes since 0.5.0: #59 (Addresses #42, #58, #60)

• Report only option (fortio report command reporting/graphing only UI on http://localhost:8080/ vs the full UI and server endpoints of fortio server on http://localhost:8080/fortio/)

• Adding -a flag to fortio load for autosave and changed default label generation to include the target url and only the first part of the hostname (to fit more in the 64 characters length)

• Updated README and FAQ

Happy Holidays!

fortio v0.5.0

Starting the January 2018 (0.5) series early (Happy Holidays!):

#56, #57 (fixes #50)

• Adding ?delay=<duration> to echo urls will delay the response up to a max duration of 1 second.

• Support status param as list with probability

  http://localhost:8080/echo/?delay=1ms&status=567:33.33,568:33.33
  For instance delays the response by 1ms and has 33.33% chance of returning
  567, 33.33% 568 and 33.34% 200

• % summary is output for each return code, for instance
  with http://localhost:8080/echo?status=503:10,504:20

  Code 200 : 2060 (68.7 %)
  Code 503 : 318 (10.6 %)
  Code 504 : 622 (20.7 %)
  

• new flag -allow-initial-errors if you don't want fortio fail fast on errors during warmup

• bug fix: handle 100% errors in graph title (though that was impossible before without the flag)

fortio v0.4.4

New since 0.4.3:

#55

Added UI for infinite runs
Show error % / no error summary in graph title

fortio v0.4.3

New since 0.4.2:

#51 and #53:

• Fortio UI now shows a progress bar while the run is progressing and a button to stop the run earlier (thanks @vii for the contribution!)

fortio v0.4.2

Changes since 0.4.1:

#44:

• The default data directory for "go get" or built from source (dev) fortio is now .. It remains /var/lib/istio/fortio for the docker image and the binary release (where we can create the directory ahead of time)

• Renamed the directory flags -data-dir and -static-dir, leaving "path" for URL related flags.

• The binary release/ build is now reusing the base docker build.

• Fix security issue #45:

properly html escape errors and regular writer output

ps: from this version onward - changing github tag to be "vX.Y.Z" (from X.Y.Z), docker image remain istio/fortio-X.Y.Z

fortio v0.4.1

New since 0.4.0:

#41:
Multi graph of latencies and percentiles

Allow in-page load of any results from a select box while still also having single result link supported

Data is updated instead of creating a new chart for smooth transition/animation.

Now using cubicInterpolation for percent graph

Misc changes:

fortio -version prints the version (#39)