feat(presets): add ClawMetry observability preset and monitoring docs

[vivekchand]

What this adds

Two additions to make ClawMetry (https://clawmetry.com/nemoclaw) a first-class observability option for NemoClaw users.

1. nemoclaw-blueprint/policies/presets/clawmetry.yaml

A network policy preset for ClawMetry Cloud sync. Follows the same pattern as existing presets (discord.yaml, telegram.yaml, etc.). Allows ClawMetry's sync process inside sandboxes to reach clawmetry.com for structured telemetry upload.

Users apply it with:

nemoclaw <name> policy-add clawmetry

2. docs/monitoring/monitor-with-clawmetry.md

A how-to guide following the exact format and structure of the existing monitor-sandbox-activity.md. Covers:

• Installing ClawMetry on the host
• Applying the preset to sandboxes
• Connecting to ClawMetry Cloud
• Running ClawMetry inside a sandbox

Why ClawMetry

NemoClaw's built-in TUI provides ephemeral, terminal-only visibility. ClawMetry adds what production deployments need: structured persistent logs, token cost tracking, memory file diff detection, and fleet-level visibility across all sandboxes from any browser.

ClawMetry is open source (MIT), free to install, and E2E encrypted. GitHub: https://github.com/vivekchand/clawmetry

Testing

The preset follows the same YAML schema as all other presets in the presets/ directory. The docs page follows the exact frontmatter format and section structure of monitor-sandbox-activity.md.

Summary by CodeRabbit

• New Features

  • Added ClawMetry monitoring preset enabling telemetry tracking and performance analytics for sandboxes

• Documentation

  • Added comprehensive guide for monitoring sandboxes with ClawMetry, covering cloud dashboard setup, local deployment options, and monitored metrics

[coderabbitai]

📝 Walkthrough

Walkthrough

ClawMetry monitoring support is added through a new documentation guide and accompanying network preset configuration. The documentation explains installation, cloud connection, dashboard access, and both cloud and local monitoring modes. The preset defines network policies allowing ClawMetry agents to communicate with ClawMetry endpoints via HTTPS.

Changes

Cohort / File(s)	Summary
ClawMetry Documentation docs/monitoring/monitor-with-clawmetry.md	New guide covering ClawMetry installation, cloud connection with OTP authentication, dashboard access, per-sandbox preset application, and local dashboard deployment within sandboxes.
ClawMetry Network Preset nemoclaw-blueprint/policies/presets/clawmetry.yaml	New preset defining HTTPS network policies for ClawMetry endpoints (*.clawmetry.com and clawmetry.com on port 443) with rule specifications and applicable binary paths.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A rabbit hops with glee,
Watching metrics flow so free,
ClawMetry's eyes now see,
Each sandbox's vitality! 📊

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically describes the main changes: adding a ClawMetry observability preset and its corresponding monitoring documentation. It is concise, clear, and directly summarizes the primary purpose of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

🧹 Nitpick comments (4)

docs/monitoring/monitor-with-clawmetry.md (4)

27-31: Add an introductory sentence under Prerequisites.

The section starts directly with bullets; add a short intro sentence immediately below the H2.

As per coding guidelines, "Sections use H2 and H3, each starting with an introductory sentence."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/monitoring/monitor-with-clawmetry.md` around lines 27 - 31, The "##
Prerequisites" section is missing its required introductory sentence; add one
sentence immediately below the "## Prerequisites" heading and above the bullet
list (for example: "Before proceeding, ensure you have the following
prerequisites:") so the section follows the guideline that H2/H3 sections start
with a brief introductory sentence.

---

23-23: Hyphenate “open-source” in prose.

Line 23 and Line 100 use “open source” as an adjective; use “open-source”.

As per coding guidelines, this is a documentation text-quality fix and should be flagged inline for correction.

Also applies to: 100-100

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/monitoring/monitor-with-clawmetry.md` at line 23, Replace the adjective
phrase "open source" with the hyphenated form "open-source" in the ClawMetry
description sentence(s); locate the sentence containing "ClawMetry ... is an
open source observability dashboard" (and the other occurrence near the same
paragraph referencing ClawMetry) in monitor-with-clawmetry.md and update both
occurrences to "open-source" so the prose follows the documentation style guide.

---

95-100: Use a Next Steps section at the bottom instead of Related Topics.

Please rename and structure the final section as Next Steps with related links.

As per coding guidelines, "A 'Next Steps' section at the bottom links to related pages."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/monitoring/monitor-with-clawmetry.md` around lines 95 - 100, Rename the
"Related Topics" section heading to "Next Steps" and keep the existing bullet
links under it; update the heading text "Related Topics" to "Next Steps" and
ensure the list items (Monitor Sandbox Activity, Network Policies, ClawMetry for
NemoClaw, ClawMetry GitHub) remain as related links formatted as bullets so the
section conforms to the guideline that a "Next Steps" section at the bottom
links to related pages.

---

23-61: Split multi-sentence lines to one sentence per source line.

Line 23, Line 41, Line 57, and Line 61 each contain multiple sentences on a single line. Please place each sentence on its own line for diff readability.

As per coding guidelines, "One sentence per line in source (makes diffs readable)."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/monitoring/monitor-with-clawmetry.md` around lines 23 - 61, Several
paragraphs in the markdown contain multiple sentences on one source line, making
diffs hard to read; split each sentence onto its own line. Specifically: the
opening paragraph that begins with "[ClawMetry](https://clawmetry.com/nemoclaw)
is...", the paragraph starting "The installer detects NemoClaw automatically and
applies the `clawmetry` preset...", the "After installation, connect your node
to ClawMetry Cloud:" paragraph that begins with "After installation, connect
your node to ClawMetry Cloud:", and the final "Open [app.clawmetry.com]..."
sentence should each be rewritten so every sentence is on its own line while
preserving the exact wording and punctuation.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@docs/monitoring/monitor-with-clawmetry.md`:
- Around line 27-31: The "## Prerequisites" section is missing its required
introductory sentence; add one sentence immediately below the "## Prerequisites"
heading and above the bullet list (for example: "Before proceeding, ensure you
have the following prerequisites:") so the section follows the guideline that
H2/H3 sections start with a brief introductory sentence.
- Line 23: Replace the adjective phrase "open source" with the hyphenated form
"open-source" in the ClawMetry description sentence(s); locate the sentence
containing "ClawMetry ... is an open source observability dashboard" (and the
other occurrence near the same paragraph referencing ClawMetry) in
monitor-with-clawmetry.md and update both occurrences to "open-source" so the
prose follows the documentation style guide.
- Around line 95-100: Rename the "Related Topics" section heading to "Next
Steps" and keep the existing bullet links under it; update the heading text
"Related Topics" to "Next Steps" and ensure the list items (Monitor Sandbox
Activity, Network Policies, ClawMetry for NemoClaw, ClawMetry GitHub) remain as
related links formatted as bullets so the section conforms to the guideline that
a "Next Steps" section at the bottom links to related pages.
- Around line 23-61: Several paragraphs in the markdown contain multiple
sentences on one source line, making diffs hard to read; split each sentence
onto its own line. Specifically: the opening paragraph that begins with
"[ClawMetry](https://clawmetry.com/nemoclaw) is...", the paragraph starting "The
installer detects NemoClaw automatically and applies the `clawmetry` preset...",
the "After installation, connect your node to ClawMetry Cloud:" paragraph that
begins with "After installation, connect your node to ClawMetry Cloud:", and the
final "Open [app.clawmetry.com]..." sentence should each be rewritten so every
sentence is on its own line while preserving the exact wording and punctuation.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fd528f69-214c-4ffd-bf9d-1c1b29fe7d4e

📥 Commits

Reviewing files that changed from the base of the PR and between eb4ba8c and 9abaaf8.

📒 Files selected for processing (2)

• docs/monitoring/monitor-with-clawmetry.md
• nemoclaw-blueprint/policies/presets/clawmetry.yaml

[wscurran]

✨ Thanks for submitting this proposal with a detailed summary, it proposes integrating ClawMetry into NemoClaw, which could enhance the observability features of NemoClaw and provide more insights for users.