Skip to content
doze
0.2

These are the docs for doze 0.2.

What changed in each release →

Tiles, List, Map and Grid

The four views of a stack's page, what each shows, and when to use which.

On this page

Four views of the same stack. Pick one with the switch at the top, or press 1 to 4. doze remembers the view for each stack.

The larder stack in the Map view, with the view switch, the stack's switch, the strip of totals and the cards
Larder, the made-up grocery example, in the Map view.
  1. The view switch. Tiles, List, Map, Grid.
  2. The stack's switch. Up or down for the whole stack.
  3. The strip. Memory, CPU, how many are awake, connections, tasks.
  4. Who calls whom. Left to right, the way a request travels. Lines come from references in doze.hcl.
  5. Nobody calls these. Services that work from events.
  6. Shared by the stack. Postgres, Kafka and the rest. The chips on each card say who uses what.
  7. The keys for this view. They change with the view.

Beside the view switch, Activity (A) reads the stack’s journal over the last hour, day or week: how long each service slept, about how much memory that left free, what woke each one, and what crashed. All logs (L) is every service’s output, merged.

View What it shows Use it to
Tiles 1 A card per service, with its state, its memory and its address. See at a glance what is awake.
List 2 A row per service, and a details pane for the one you select. Read addresses and details without opening each one.
Map 3 Who calls whom, from references in doze.hcl. Click a card to draw its lines. Understand a stack you did not write.
Grid 4 The stack as a table: a row needs each column it has a dot in. Answer “what uses kafka?” down a column.

Tiles and List group the services the same way: apps (your code), modules (from the doze registry), outside (your own services) and tasks. Every row has a switch: on wakes the service, off puts it to sleep. Putting a service to sleep asks first when something running depends on it.

The larder stack in Tiles: a card per app with its switch, state, memory and address
Tiles. Each card says why the service is awake: storefront needs gateway, so gateway stays up.
The larder stack in List, with catalog selected and its details in the pane on the right
List, with catalog selected: its addresses, its command, when it sleeps, and what it needs.
The larder stack in Grid: services down the side, what they need across the top, and the tasks that run before each
The Grid: read across for what a service needs, down for who needs a service. The last column is the tasks that run before it.
1–4
Tiles, List, Map, Grid
↑ ↓ j k
move
space
wake or sleep the selected one
⏎
open it
w s
wake, sleep
p
pin it awake
r
restart it
l
its logs
y
copy its address
/
filter
A L
Activity, all logs

In the Map the arrow keys move between cards the way they are drawn. In the Grid, an arrow key or ⏎ moves into the table, and / filters its rows. Every key is listed under ⌘K and keys.

Terminal window
doze status # every service, its state and memory
doze status --graph # the dependency tree

Next: Inside a service.