List specs, traces, or events that are stored in the Akita cloud.
Downloads API specs as OpenAPI specifications in YAML format.
Lists the available traces.
Lists captured API calls in time order. This feature is available only for traces which were captured with the
AKITA_DEPLOYMENT environment variable set (e.g., to "staging" or "deployment" or "test".)
Show the API service graph. This feature is available only for traces which were captured with the
AKITA_DEPLOYMENT environment variable set, in a multi-service deployment.
$ akita get traces --service my-service
List all the latest ten traces for
my-services along with their attached tags,
$ akita get akita://my-service:spec
List the most recent API specs for
$ akita get akita://my-service:spec:orange-giraffe-123456
Download an API spec by AkitaURI, to a file named
$ akita get timeline --service my-service --deployment staging --start 2020-09-02T12:00:00Z --limit 100
List the first 100 captured HTTP requests, in time order, starting at 2020/09/02 12:00:00 UTC.
Instead of the subcommands
akita get trace or
akita get spec, you can specify akita get [AKITAURI]`. The correct subcommand will be used based on the type of the URI.
You must specify at least a service name and a type, either in the Akita URI or with the
When downloading a spec, you may specify an output file name as a second argument.
Specify the name of the service.
Specify the name of the deployment to view. (
get timeline only.)
Limit the number of items shown when listing objects. The default limit is 10; you may specify 0 for no limit. No effect when downloading an object.
Filter the objects by tags. All specified tags must match. No effect when downloading an object.
Specify the range of times to see for
get timeline. Timestamps must be given in RFC3339 format, like
It is not currently possible to download an API trace, or to specify an output format.
Updated 9 months ago