Fortio 1.57.5

What's Changed

• Go 1.20.7 build image + log/cli/scli console/color output improvements + other deps (#811)

Full Changelog: v1.57.4...v1.57.5

Fortio 1.57.4

What's Changed

• Save the async result file even on init error (like invalid host/target) - fixes #796 (#797)

Also update to fortio.org/log and scli with support for logging goRoutine ID (r= in json logs, [] after timestamp in colorized output)

Full Changelog: v1.57.3...v1.57.4

Fortio 1.57.3

What's Changed

• Rebuilt with go 1.20.6 (security fix)

(1.57.1 and .2 were miss build due to #793 / docker ce upstream image error)

Full Changelog: v1.57.0...v1.57.3

Fortio 1.57.0

What's Changed

• Update to color supporting version of log/cli/scli console/terminal logs are now colorized by default (JSON when redirected unless changed by flags) by @ldemailly in #789

Full Changelog: v1.56.0...v1.57.0

Fortio 1.56.0

What's Changed

• #783
  • Add -X (or &X= in rapi and web UI) to override the method from GET/POST auto default.
  • Treat content-type in header as ContentType on http options
• #785
  • Don't run with invalid URLs / bad hosts for 100% errors with std client (ie detect errors early like fast client)
  • Allow most of the same query args/form parameters for proxy fetcher than for load test, ie change the method, add headers, payload etc... (e.g. http://localhost:8080/fortio/fetch2/?url=debug.fortio.org&H=foo:bar&payload=Blah&X=PUT for a PUT with payload and header)
• fortio/scli#15 / https://github.com/fortio/scli/releases/tag/v1.7.0
  • add -logger-file-line=false flag to turn off filename and line numbers (useful along with -logger-timestamp=false when diff'ing output of 2 server logs between good/bad for instance)

Full Changelog: v1.55.2...v1.56.0

Fortio 1.55.2

What's Changed

#782

Switch to new log 1.5.0 format where the timestamp is (float64) sec.usec instead of a large (int64) usec since unix epoch {like uber zap}

https://github.com/fortio/log/releases/tag/v1.5.0

Update / use scli with flag (-logger-timestamp=false) for not logging TS (and not doing JSON under a new name, was -json-log=false, now -logger-json=false)

https://github.com/fortio/scli/releases/tag/v1.6.0

Requires logc 1.1.0 or newer to parse the new log format back to colorized text

https://github.com/fortio/logc/releases/tag/v1.1.0

Full Changelog: v1.55.1...v1.55.2

Fortio 1.55.1

What's Changed

• Use fixed log package for log.Printf, remove bogus \n in log.Printf (#775)
• Change all the http client logs (info level and up) to structured (#778)

Full Changelog: v1.55.0...v1.55.1

Fortio 1.55.0

What's Changed

• Big change is to be using JSON structured logging (unless calling -json-log=false) (#768)
  • Also add log-errors=on option setting to rest api and web UI
  • Also add the runid to the structured logs (run=...) so errors from specific runs can be identified even if more than one are currently running

Structured JSON logging is coming from fortio.org/log 1.4.0 / fortio/log#22 - it includes http request logging in that format too (log.LogRequest)

Other changes:

• go1.20.5 build image (#762)
• dependency updates

Full Changelog: v1.54.3...v1.55.0

Fortio 1.54.3

What's Changed

• Rebuilt with Go 1.20.4 (#755)
• Remove non idiomatic use of new() and use recommended var buf bytes.Buffer directly (#751)
• Dependency updates

Full Changelog: v1.54.2...v1.54.3

Fortio 1.54.2

What's Changed

• Fix long standing boundary condition rare bug with histogram buckets (in #746)
• Fix error handling so passing an invalid -payload-file cause fortio to not proceed with curl/load test (abort, fixes #748 )
• Dep updates

Full Changelog: v1.54.1...v1.54.2