Akita Client v0.21.9

  • Print the version number on startup.
  • The --log-format option (controls how the client formats its logs) is no longer hidden.
  • Added telemetry for reporting how the CLI is used. To opt out of this, set AKITA_DISABLE_TELEMETRY=true in the environment.
  • Fixed a bug that caused HTTP parsing to fail in certain cases.

Akita Client v0.21.8

  • Ensure requests and responses with JSON-encoded custom content types are parsed as JSON while retaining the custom content type. This fixes a bug introduced in v0.21.7 where all custom content types were parsed as binary blobs.

Akita Client v0.21.7

  • Preserve custom content types. Previously, custom content types that could be parsed as known content types (e.g. application/json) were renamed to the known content type.
  • Disable collection of TCP and TLS metadata by default; this can be enabled with --report-tcp-and-tls if needed.
  • Deprecated akita get graph.

Akita Client v0.21.6

  • Memory-usage improvements
  • Fixed a bug in decompressing HTTP bodies

Akita Client v0.21.5

  • Deprecates the following commands, which are either no longer relevant or replaced by the Akita app:

    • apidiff
    • apispec
    • learn
    • setversion
  • Deprecates the --deployment flag. We recommend creating separate projects for different deployment environments, e.g. my-project-staging and my-project-prod.

  • Deprecates the --service flag and replaces it with --project.

  • Fixes a bug that prevented the apidump command from saving results to a local HAR file.

Akita Client v0.21.4

  • Allow CLI to measure HTTP server latencies up to ~60s

Akita Client v0.21.3

  • The Akita Client better tolerates errors during packet capture. If errors occur on an interface, packet capture continues on other healthy interfaces.

Akita Client v0.21.2

  • Send packet-capture telemetry for the entire duration of the trace.

Akita Client v0.21.1

  • rate limit set to 1000 requests/minute by default (previously defaulted to unlimited)

Akita Client v0.21.0

  • The Akita Client now reports health and telemetry statistics to the Akita Cloud on startup. See Troubleshooting for details on using telemetry information to debug your Akita Client deployment.