diff options
| author | tv <tv@krebsco.de> | 2026-11-18 12:48:29 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-18 13:59:42 +0100 |
| commit | d130c0612b4c63f2d30da65ebcc231018c1f2606 (patch) | |
| tree | 8700f2d53351cbbecbe772ea7701bf6240d5210c /docs/guides/federation/watching.md | |
| parent | 0bfe07af92a775b0e896e0fc5a989a1d9b65f7b3 (diff) | |
docs: references to another document's section linked to it
Where a document names a section of another after linking to it
("([`store.md`](store.md), Pinned checkpoints)"), the name links to that
section too, by the id both GitHub and cgit's about filter give its
heading; paragraphs that grew past the width are wrapped anew, links and
code kept on one line each.
Diffstat (limited to 'docs/guides/federation/watching.md')
| -rw-r--r-- | docs/guides/federation/watching.md | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/guides/federation/watching.md b/docs/guides/federation/watching.md index c04a6a3..f55005a 100644 --- a/docs/guides/federation/watching.md +++ b/docs/guides/federation/watching.md @@ -1,8 +1,9 @@ # What to watch What tells an operator, or a party, that a federated swarm needs them. Watch what every -node needs watching ([`operations.md`](../../operations.md), What to alert on), and -besides it, the node's store, through its API and its log. +node needs watching ([`operations.md`](../../operations.md), +[What to alert on](../../operations.md#what-to-alert-on)), and besides it, the node's +store, through its API and its log. ## Through the API @@ -10,8 +11,8 @@ besides it, the node's store, through its API and its log. twice, and nodes may be apart. Act on it at once ([`when-things-go-wrong.md`](when-things-go-wrong.md)). * **No store** (`404` from `GET /events` for longer than a start takes): the node can't - read its store ([`when-things-go-wrong.md`](when-things-go-wrong.md), A node doing less - than it should). + read its store ([`when-things-go-wrong.md`](when-things-go-wrong.md), + [A node doing less than it should](when-things-go-wrong.md#a-node-doing-less-than-it-should)). * **Proposals on the current version** (`proposals` in `GET /events/counts`): each with who voted what, and whether it passed or is dead; the party's record says what it voted. @@ -28,7 +29,7 @@ besides it, the node's store, through its API and its log. A node's dashboard (`/admin/dashboard`) shows the same in its document box, read every 5 s: the version, the parties and which of their nodes are members, the values, the proposals with who voted what and what each changes, and what the node refused -([`dashboard.md`](../../dashboard.md), Federation). +([`dashboard.md`](../../dashboard.md), [Federation](../../dashboard.md#federation)). ## In the log |
