Skip to content

feat(genlayernode): add portal step + monitoring - #32

Open
rasca wants to merge 2 commits into
genlayerlabs:mainfrom
rasca:docs/monitoring-credentials
Open

rasca wants to merge 2 commits into
genlayerlabs:mainfrom
rasca:docs/monitoring-credentials

Conversation

@rasca

@rasca rasca commented Jun 17, 2026 •

Copy link
Copy Markdown
Contributor

Description

Updates the genlayernode setup skill with monitoring credentials and a new portal account-linking step. Fills in the Prometheus/Loki instance IDs and documents the shared Telegram-provided auth token, adds a step to link the operator wallet (plus profile image and banner) at portal.genlayer.foundation, and makes telemetry monitoring mandatory on testnet.

Release Notes

  • Validator setup now includes linking your account in the portal: link the operator wallet, which auto-attaches all your validators across Asimov and Bradbury, and set your profile image and banner
  • Monitoring is now required for every validator during testnet (previously optional)
  • Pre-filled Prometheus/Loki instance IDs; the auth token is shared for both and provided privately via the Telegram group

Types of Changes

  • New feature (non-breaking change that adds functionality)

Checklist

  • My code follows the code style of this project
  • I have added the necessary documentation (if appropriate)

Summary by CodeRabbit

  • Documentation
    • Monitoring is now required for all testnet validators.
    • Added new setup step to link your operator wallet in the GenLayer portal with profile customization.
    • Updated validator setup procedure with revised step numbering.
    • Enhanced monitoring configuration guidance with clearer instance ID specifications.

@coderabbitai

coderabbitai Bot commented Jun 17, 2026 •

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@rasca, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 49 minutes and 18 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fc2a6ff1-3f0c-4cbc-93f8-2e392180d09f

📥 Commits

Reviewing files that changed from the base of the PR and between 26f2466 and 1723615.

📒 Files selected for processing (6)
  • index.html
  • plugins/genlayernode/skills/genlayernode/SKILL.md
  • plugins/genlayernode/skills/genlayernode/install-procedure.md
  • plugins/genlayernode/skills/genlayernode/monitoring-procedure.md
  • plugins/genlayernode/skills/genlayernode/skill.yaml
  • plugins/genlayernode/skills/genlayernode/staking-wizard-procedure.md
📝 Walkthrough

Walkthrough

Across six files, monitoring is changed from optional to required for testnet validators, a new "Link Your Account in the Portal" step is introduced into the onboarding wizard and all procedure documents, and step numbering is updated consistently throughout skill.yaml, SKILL.md, index.html, install-procedure.md, monitoring-procedure.md, and staking-wizard-procedure.md.

Changes

Validator Onboarding: Mandatory Monitoring and Portal Linking

Layer / File(s) Summary
Monitoring made mandatory in skill config and .env template
plugins/genlayernode/skills/genlayernode/skill.yaml
enable_monitoring input changed to required: true with default true; .env template updated with a "REQUIRED on testnet" central monitoring/Loki block; the "Decide: Enable monitoring?" yes/no flow is replaced with a direct mandatory monitoring step.
Monitoring procedure: required notice and credential guidance
plugins/genlayernode/skills/genlayernode/monitoring-procedure.md
Opening notice added stating monitoring is mandatory for every testnet validator; .env example updated with numeric Prometheus/Loki IDs and shared auth-token placeholder; guidance added that usernames are different numeric IDs but share one password from Telegram; environment-variables reference table updated to match.
New portal wallet-linking step in wizard and procedures
plugins/genlayernode/skills/genlayernode/skill.yaml, plugins/genlayernode/skills/genlayernode/staking-wizard-procedure.md, plugins/genlayernode/skills/genlayernode/install-procedure.md
New link-operator-wallet-portal wizard step and ordered procedure step added to skill.yaml; staking-wizard-procedure.md inserts an early "Tip — link the portal early" at Step 4; install-procedure.md renumbers next steps and inserts the portal-linking instruction before monitoring.
SKILL.md and index.html surface updates
plugins/genlayernode/skills/genlayernode/SKILL.md, index.html
Process overview gains "Enable monitoring" as required step 10; new portal-linking and mandatory-monitoring sections added; installation steps table updated to steps 11–12; yes/no monitoring phrasing replaced; index.html wizard step list updated to match.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

  • dohernandez
  • jmlago
  • MuncleUscles

Poem

🐇 Hop, hop, the portal calls,
Link your wallet through the halls!
Monitoring? Required now—
Testnet validators, take a bow.
No more "maybe," no more choice,
Prometheus speaks with one clear voice! 📊

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main changes: adding a portal account-linking step and making monitoring a required feature for testnet validators.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands and usage tips.

dohernandez
dohernandez previously approved these changes Jun 17, 2026
rasca added 2 commits June 17, 2026 12:14
Fill in the Prometheus/Loki instance IDs and document that both
share one auth token provided privately via the Telegram group.
Add a portal account-linking step (operator wallet, profile image,
banner) and make telemetry monitoring mandatory on testnet.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
plugins/genlayernode/skills/genlayernode/install-procedure.md (1)

390-392: ⚡ Quick win

Portal linking and mandatory monitoring integrated into post-installation guidance.

The Next Steps section correctly sequences portal account linking before monitoring setup and marks monitoring as required on testnet. The portal linking reference includes the correct URL and navigation path, and monitoring guidance appropriately defers to monitoring-procedure.md for full setup. However, the step numbering (3, 4, 5) in this section may lack clarity since the preceding installation phases are numbered 1–9 — consider clarifying that these are post-installation follow-up items rather than continuation of the installation phases.

💡 Optional refinement for clarity

Consider adding a brief transitional note before the numbered list to clarify these are post-installation follow-ups:

 ## Next Steps
 
 After installation completes:
-1. Wait for sync to complete (check `journalctl` for progress)
-2. Verify validator is active: `genlayer staking validator-info --validator 0xYOUR_WALLET`
-3. Link your account in the portal: ...
-4. Enable monitoring (REQUIRED on testnet) ...
-5. Optional: Set validator identity ...
+1. Wait for sync to complete (check `journalctl` for progress)
+2. Verify validator is active: `genlayer staking validator-info --validator 0xYOUR_WALLET`
+
+### Post-Installation Setup
+
+3. **Link your account in the portal**: ...
+4. **Enable monitoring (REQUIRED on testnet)**: ...
+5. **Optional: Set validator identity**: ...

This clarifies the progression and makes the mandatory/optional distinction more visually prominent.

🤖 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 `@plugins/genlayernode/skills/genlayernode/install-procedure.md` around lines
390 - 392, The step numbering (3, 4, 5) for portal linking, monitoring setup,
and validator identity creates ambiguity since the preceding installation phases
are numbered 1-9, making it unclear whether these are continuations of the main
phases or separate post-installation follow-ups. Add a clear transitional
heading or introductory note before the numbered list of portal linking,
monitoring, and validator identity steps to explicitly indicate these are
post-installation follow-up items rather than additional installation phases.
This will clarify the progression and make the mandatory versus optional
distinctions more prominent.
🤖 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.

Nitpick comments:
In `@plugins/genlayernode/skills/genlayernode/install-procedure.md`:
- Around line 390-392: The step numbering (3, 4, 5) for portal linking,
monitoring setup, and validator identity creates ambiguity since the preceding
installation phases are numbered 1-9, making it unclear whether these are
continuations of the main phases or separate post-installation follow-ups. Add a
clear transitional heading or introductory note before the numbered list of
portal linking, monitoring, and validator identity steps to explicitly indicate
these are post-installation follow-up items rather than additional installation
phases. This will clarify the progression and make the mandatory versus optional
distinctions more prominent.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c090ca18-ea56-4ce0-814b-487a60c5c6d3

📥 Commits

Reviewing files that changed from the base of the PR and between 0fb6701 and 26f2466.

📒 Files selected for processing (6)
  • index.html
  • plugins/genlayernode/skills/genlayernode/SKILL.md
  • plugins/genlayernode/skills/genlayernode/install-procedure.md
  • plugins/genlayernode/skills/genlayernode/monitoring-procedure.md
  • plugins/genlayernode/skills/genlayernode/skill.yaml
  • plugins/genlayernode/skills/genlayernode/staking-wizard-procedure.md

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants