fortio v0.4.0

Cyber monday special: A new fortio release ! first of the 0.4 series!

New since 0.3.8:

#37:

• Allow save/retrieve/graph results

Default data dir is /var/lib/istio/fortio, create it if you want files saved there. use -data-path to change it, set to "" to not even attempt to save

• Moved result -> chart logic entirely in javascript

So a page can directly graph a fortio JSON

Also added the version in the virtual static prefix (so fortio
upgrades/version bump yield a reload of the code)

• Fixed thread safety (#22)

• Accelerate the build and made an image for linters (#36)

• Bug fix: Fixed hanging case with chunked mode

when the last read covered more than 1 chunk, which happens at the
moment with the main url. Fortio was doing 1 more read and hanging

Added option to change debug level in webtest

fortio v0.3.8

Happy thanksgiving !

Big internal change in this release:

UI Resources (chart js, html template, js code) that used to be embedded into go code until 0.3.7 in order to keep binary self contained have been externalized into their own files which will let us add and maintain features much more easily.

go get -u istio.io/fortio still works by finding the resources in the source tree through introspection

For docker and future binary distributions -ldflags '-X istio.io/fortio/ui.dataDirectory=/usr/local/lib/fortio -s' let's you specify where the files are installed, or you can pass -static-path to the command line.

Also changed since 0.3.7:

• Improved integration test (Webtest.sh)
• In -curl mode, exit with non 0 for non 200 http code (like curl -f)

fortio v0.3.7

Changes since 0.3.6:

Adding Labels, URL and Run StartTime to JSON and Chart (#30)
(and doc and tests and CI updates)

ps: this is the last "single binary" release (with embedded html/js)

fortio v0.3.6

Changes since 0.3.5:

• Fix/workaround for half close

Adding a flag (-halfclose) and http cli option to do/not do half close
(To workaround envoyproxy/envoy#2066 set the
default to false)
Also pass the keep alive flag to the standard client

• Fix for #24 (proxy erroneous More data is available... error)

Needed to reset max when switching from expected keep alive to not keep
alive

fortio v0.3.5

Changes:

Bug fix: Host header was silently stuck if ever set in UI (#20)

#21:
New "-curl" flag to fortio command line to fetch the URL content (and headers when using the fast client)

When using the ui server /fortio/fetch/X will fetch http://X
(not to be used as a proxy but handy for debugging inside a cluster)

fortio v0.3.4

New in this release: use relative path for the UI dependencies so fortio can easily be placed behind prefixed ingresses

fortio v0.3.3

New in 0.3.3:

The graphical representation can be dynamically modified to change the X axis min max (to compare graphs against the same scale) and to set logarithmic scale on either axis.

The graph title now also includes the input parameter as well as the achieved qps, avg, min, max and percentile results...

Also includes latest Chart.js bug fixes and a trimmed down distribution to keep the binary size minimal

fortio v0.3.2

Now with a graphical representation of the histogram data !

Try running fortio server and visit http://localhost:8080/fortio to control the UI and launch a load test and get the resulting histogram and cumulative % graphically.

fortio v0.3.1

New since 0.3.0:

fortio server now has an optional (controlled by -ui-path flag) /fortio path with a basic UI to trigger remote load tests and get the results in text or JSON

fortio v0.3.0

New big features:

• you can run fortio with infinite duration - until ^C is sent and it will report the results then,
• likewise you can interrupt fortio before the requested duration and it will report the results
• new JSON output for the all the results, including the Histograms - through a new HistogramData type
• try fortio load -json - http://www.google.com/ to output JSON to stdout while the rest of the output is now on stderr

Note the new HistogramData pure data object returned by the APIs - this is an incompatible change but yield very good benefits (ability to programmatically access all the data, json export etc) thus the 0.3.x bump

It also matches the Istio 0.3 dev cycle