diff options
| author | tv <tv@krebsco.de> | 2026-11-18 18:50:46 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-18 20:31:30 +0100 |
| commit | 56837530e17d95814d21076c527c8577f0a6da97 (patch) | |
| tree | e9d48d3645c188e07a0e12b75f8805a1ad0f8e83 /docs/guides | |
| parent | c64fcc05d8c53bee99ab039bd709039afb730cdd (diff) | |
dashboard: the event a federation's store stopped at
The federation view shows, below this node's party, the event its store stopped at
(`stopped` in `GET /events`), why, and how many events it holds back, with what to do:
run a continuum that reads it, or drop it. The page check renders one.
Diffstat (limited to 'docs/guides')
| -rw-r--r-- | docs/guides/federation/watching.md | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/guides/federation/watching.md b/docs/guides/federation/watching.md index ec7ce6a..a54dd7f 100644 --- a/docs/guides/federation/watching.md +++ b/docs/guides/federation/watching.md @@ -32,8 +32,9 @@ store, through its API and its log. ## On the dashboard 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 +5 s: the version, where the store stopped, 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#federation)). ## In the log |
