ezgh obs services deps

ezgh obs services deps <service> [--environment e] [--from t] [--to t] [flags]

Show a service’s upstream (what calls it) and downstream (what it calls) from the service graph obs builds by pairing client and server spans, with each edge’s requests per second, error rate and p95 latency (the server’s upstream, the client’s downstream), over --from (default 1h ago) to --to (default now), in one environment or all of them.

A callee that sends no spans of its own (a database, a queue, an external API) is a virtual node, named from the client span’s attributes, with its connection type; requests that enter from outside come from “user”. The service is a key as the graph names it, cataloged or not (a virtual node such as postgresql/orders works too), or a cataloged service’s ID or slug. These are PromQL reads, which need obs.metrics.query.

Part of ezgh obs services.

Examples

ezgh obs services deps checkout/api
ezgh obs services deps checkout/api --environment production --from 24h -o json

Flags

This command also takes the global flags.