Topology and Observatory

Guara Cloud builds a live map of every service in a project and the traffic flowing between them, plus a real-time mission-control dashboard for the project as a whole.

Project map

The project map shows each service as a node and each inter-service interaction as an edge. Edges come from two complementary sources:

• Paired (paired): built from Tempo’s service-graph processor by matching client and server spans inside the same trace. This works for HTTP-based service-to-service calls and carries full latency percentiles, error rate and request rate.
• L4 flow (l4_flow): built from Beyla’s kernel-level TCP flow metrics. This works for every TCP protocol — including Redis, NATS, Postgres and MongoDB — that Tempo cannot pair across traces. Latency and error rate are not derivable from L4 flows, so the dashboard renders these edges with a dashed style and a byte-rate label, instead of fabricating zero values.

The two kinds coexist on the same map so you can see HTTP traffic with full request/error metrics alongside backing-service traffic that would otherwise be invisible.

Cron workers on the map

Cron workers appear on the same canvas as services. They render as nodes with a clock icon and a dashed border so they’re instantly distinguishable from services. A cron_trigger edge connects each worker to its destination, drawn as a dashed animated line in the platform’s secondary brand color so the scheduled call path stays visible without being confused with measured live request traffic.

Cron edges are intentionally excluded from the request-rate and error-rate aggregations on the topology, so a chatty cron worker does not skew the traffic metrics on the destination service. Click a cron worker node to jump to its detail page.

Observatory

The Observatory is the per-project mission-control view: aggregate health (services healthy, requests per minute, error rate, average and p99 latency), a scrolling event feed (errors, deploys, alerts) and a live trace timeline. It is the fastest way to see whether a project is healthy right now and where to look first when it is not.

CLI parity

Both surfaces have first-class CLI counterparts that render the same data in your terminal:

• guara projects map — renders the topology as a nodes table plus an edges table by default; pass --graph to render a best-effort layered ASCII graph (with automatic fallback to the edges table on narrow terminals). Edges show the same paired vs l4_flow distinction the dashboard uses.
• guara projects observatory — streams the health bar, event feed and live traces in place. Pass --no-watch for a single snapshot suitable for scripts and CI checks.