CORE-15382 Dedicated Nodes Monitoring page

[redikultsevsilver]

No description provided.

[infra-bot-atlantis]

Error: This repo is not allowlisted for Atlantis.

[coderabbitai]

Warning

Review limit reached

@redikultsevsilver, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 64f782e1-c989-43df-81f4-eff92ef1d5b8

📥 Commits

Reviewing files that changed from the base of the PR and between 385893f and 2db0f44.

📒 Files selected for processing (2)

• docs.json
• docs/dedicated-node-monitoring.mdx

📝 Walkthrough

Walkthrough

Adds a navigated documentation page for Dedicated Node monitoring, covering the Prometheus-compatible metrics endpoint, authentication, available metrics, Prometheus and Grafana integration, quick checks, and rate-limit behavior.

Changes

Dedicated Node monitoring

Layer / File(s)	Summary
Endpoint availability and contract docs.json, docs/dedicated-node-monitoring.mdx	Adds the monitoring page to Guides navigation and documents Dedicated Node availability, endpoint construction, authentication, isolation, and allowed methods.
Metrics and collection workflows docs/dedicated-node-monitoring.mdx	Lists available metrics, shows example exposition output, and provides curl and Prometheus scrape configuration examples.
Visualization and rate limits docs/dedicated-node-monitoring.mdx	Provides Grafana PromQL examples and documents 429 responses, Retry-After, and rate-limit behavior.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: zaslavskii, akegaviar

Poem

A rabbit hops through metrics bright,
With Prometheus guiding the night.
Grafana graphs bloom,
Curl checks clear the room,
While rate limits keep traffic light.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided, so the change intent can't be assessed from the description.	Add a brief description summarizing the change so reviewers can confirm the PR intent.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: adding a dedicated nodes monitoring page.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/CORE-15382-document-dedicated-nodes-monitoring

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/dedicated-node-monitoring.mdx`:
- Around line 22-24: Add the text language tag to the fenced code block
containing the metrics endpoint URL, without changing the URL or surrounding
documentation.
- Line 6: Remove the spaces surrounding em dashes throughout the dedicated node
monitoring prose, including the referenced occurrences, so phrases use the
`word—word` style consistently.
- Line 128: Remove the internal publication TODO comment from the dedicated node
monitoring documentation, including the test-node rate-limit result and
release-validation reference. Leave the surrounding documentation unchanged and
retain only verified public guidance.
- Line 9: Update the Availability heading in the dedicated node monitoring
documentation from h3 to h2 so the document heading hierarchy begins at h2.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 913a1730-9fd8-4237-8a31-628bb0c4c272

📥 Commits

Reviewing files that changed from the base of the PR and between 787c255 and 92040c4.

📒 Files selected for processing (2)

• docs.json
• docs/dedicated-node-monitoring.mdx

[mintlify]

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

Project	Status	Preview	Updated (UTC)
chainstack	🟢 Ready	View Preview	Jul 24, 2026, 7:03 AM

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

[mintlify]

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

Project	Status	Preview	Updated (UTC)
chainstack	🟡 Building	–	Jul 24, 2026, 6:59 AM

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

[coderabbitai]

Actionable comments posted: 5

🧹 Nitpick comments (1)

docs/dedicated-node-monitoring.mdx (1)

83-96: 🔒 Security & Privacy | 🔵 Trivial

Warn readers to protect the access token.

metrics_path embeds a credential, so copied configurations and URL-bearing logs can expose it. Add a short <Warning> recommending protected configuration and log handling, plus token rotation if the token is exposed.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/dedicated-node-monitoring.mdx` around lines 83 - 96, Add a short
<Warning> near the Prometheus scrape configuration explaining that the access
token in metrics_path must be kept in protected configuration and prevented from
appearing in copied configs or URL-bearing logs; instruct readers to rotate the
token if it is exposed.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/dedicated-node-monitoring.mdx`:
- Around line 61-81: Update the API examples in the dedicated node monitoring
documentation: wrap the Prometheus metrics output in a ResponseExample component
and the curl request in a RequestExample component, replacing the plain fenced
blocks while preserving their content.
- Around line 2-6: Update the first introductory paragraph’s “SLOs” reference to
“service-level objectives (SLOs),” while keeping subsequent mentions
abbreviated.
- Around line 112-121: Update the “Memory usage” and “Storage usage” headings in
the monitoring documentation to label the displayed values as GiB, preserving
the existing binary conversion expressions that divide bytes by 1024 three
times.
- Line 11: Update the Pricing link in the Dedicated Nodes monitoring
documentation to use a descriptive 5–10 word label, such as “Chainstack pricing
and subscription plans,” and update the corresponding Limits link to “Dedicated
Node metrics rate limits.” Preserve both existing destinations and surrounding
content.
- Line 39: Update the Chainstack API link in the dedicated node monitoring
documentation to use the existing platform API getting-started route, such as
/reference/platform-api-getting-started, instead of /reference/getting-started.

---

Nitpick comments:
In `@docs/dedicated-node-monitoring.mdx`:
- Around line 83-96: Add a short <Warning> near the Prometheus scrape
configuration explaining that the access token in metrics_path must be kept in
protected configuration and prevented from appearing in copied configs or
URL-bearing logs; instruct readers to rotate the token if it is exposed.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6df962c5-7217-44e3-a721-247e5a069859

📥 Commits

Reviewing files that changed from the base of the PR and between 92040c4 and 9b63166.

📒 Files selected for processing (2)

• docs.json
• docs/dedicated-node-monitoring.mdx

🚧 Files skipped from review as they are similar to previous changes (1)

• docs.json