get graph
Description
Visualize or download the service graph from the Akita cloud.
This feature is available only for traces which were captured with the AKITA_DEPLOYMENT
environment variable set, in a multi-service deployment.
Examples
$ akita get graph --service my-service --deployment prod
Return a textual representation of the API service graph. This shows which services have communicated with other services in your environment.
Flags
--service string
--service string
Specify the name of the service.
--deployment string
--deployment string
Specify the name of the deployment to view. (get timeline
only.)
--start timestamp
, --end timestamp
--start timestamp
, --end timestamp
Specify the range of times to include in the graph. Timestamps must be given in RFC3339 format, like 2019-12-25T07:08:09Z
.
--hide-unknown
--hide-unknown
Hide unknown vertices from the service graph. These vertices are those for which no service name could be discovered.
--output string
--output string
Specify an output format. The supported formats are:
source
(default): group the edges by source, so that you can see all the services used by one client. This is a textual representation with source on the left and target on the right.target
: group the edges by target, so that you can see all the clients of one service. This is the same textual representation assource
.dot
: output a Dot representation of the service graph. This can be visualized with Graphviz or other tools. The edges in the graph are labeled with the number of API calls observed.
--vertices string
--vertices string
Determine what the target vertices of the graph represent. The supported values are:
services
(default): each node in the graph is a single serviceendpoints
: the source vertex of each edge is a service, but the target vertex is a single API endpoint
Updated 9 months ago