Releases: fortio/fortio
fortio v0.5.1
Changes since 0.5.0: #59 (Addresses #42, #58, #60)
-
Report only option (
fortio reportcommand reporting/graphing only UI on http://localhost:8080/ vs the full UI and server endpoints offortio serveron http://localhost:8080/fortio/) -
Adding
-aflag tofortio loadfor 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)
Happy Holidays!
fortio v0.5.0
Starting the January 2018 (0.5) series early (Happy Holidays!):
-
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
withhttp://localhost:8080/echo?status=503:10,504:20Code 200 : 2060 (68.7 %) Code 503 : 318 (10.6 %) Code 504 : 622 (20.7 %) -
new flag
-allow-initial-errorsif 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
fortio v0.4.3
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/fortiofor the docker image and the binary release (where we can create the directory ahead of time) -
Renamed the directory flags
-data-dirand-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)
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
-curlmode, 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