Skip to content

docs: v6.7.2 catch-up - #107

Draft
seidroid[bot] wants to merge 1 commit into
mainfrom
docs-bridge/release-v6.7.2
Draft

seidroid[bot] wants to merge 1 commit into
mainfrom
docs-bridge/release-v6.7.2

Conversation

@seidroid

@seidroid seidroid Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Documentation catch-up for v6.7.2.

1 source PR(s) produced changes across 1 commit(s). Each source PR is a separate commit, so this reviews commit-by-commit.

source PR pages touched summary
sei-protocol/sei-chain#4520 node/advanced-config-monitoring.mdx A new Prometheus metric tendermint_p2p_known_addresses was added to track the number of distinct peers with a known address (connected peers plus those learned via PEX).

Reviewer notes

  • Backport release/v6.7: Export known peer address count as a Prometheus gauge sei-chain#4520 — The page already references tendermint_p2p_peers (for example in the seed-node section) but has no dedicated listing of p2p gauges, so a short addition documenting tendermint_p2p_known_addresses is the cleanest fit. The metric is published at router construction and refreshed every 10s, which matches the existing published-at-construction behavior described for tendermint_p2p_peers.

⚠️ Possible contradictions or misplaced sections

Flagged by a review of every touched page's final text. Each source PR was analysed in isolation, so these were invisible to the per-PR checks. Verify before merging — the checker cannot tell which side of a contradiction is correct.

Analyzing the text for the specified issues:

  • sc-hash-logger-max-disk-size default contradicts the surrounding text. The prose says "With the default settings, it keeps up to 16 GiB of closed log files," and the table lists the default as 17179869184 (16 GiB) — consistent. However, sc-hash-logger-target-file-size is labeled 16777216 (16 MiB), while 17179869184 is labeled 16 GiB; these are internally consistent, so no contradiction here. (No issue.)

  • Pebble metrics described as both always-on-by-default and configurable/off-by-default. Under "Pebble internal metrics," the text says: "FlatKV turns on Pebble's internal metrics for each data DB by default. The node does not apply an enable-pebble-metrics key from app.toml." But under "Pebble estimated read/write metrics," the counters are described as "off by default" and configurable via enable-read-write-metrics / ss-enable-read-write-metrics. These describe two different metric sets (full internal metrics vs. estimated read/write counters), so not a direct contradiction. (No issue.)

NONE


Generated by sei-docs-bridge. Every change is a proposal — verify against the source PRs before merging.

…ded to track the number of distinct peers with a known address (connected peers plus those learned via PEX). (sei-protocol/sei-chain#4520)
@seidroid seidroid Bot added the automated Automated PR from sei-docs-bridge label Nov 14, 2026
@mintlify

mintlify Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
sei-docs 🟢 Ready View Preview Nov 14, 2026, 12:27 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

This branch was successfully deployed

1 active deployment
staging — c79ce9e3 Deployed Nov 14, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated PR from sei-docs-bridge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants