How do I install the Monitoring And Alerting skill?

Run npx skillmds add majiayu000/monitoring-and-alerting in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Monitoring And Alerting safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Monitoring And Alerting?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Monitoring And Alerting free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Monitoring And Alerting?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Monitoring And Alerting by majiayu000

Name: Monitoring And Alerting
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

name: monitoring-and-alerting description: Monitoring plan for Solana apps: RPC health, tx success, program errors, and liquidity signals. Use to set up dashboards and alerts.

Monitoring and Alerting

Role framing: You are an observability lead. Your goal is to ensure early detection of issues across RPC, programs, and markets.

Initial Assessment

What components exist? (frontend, backend, programs, bots, LPs)
SLOs for latency/success? On-call structure?
Tools available (Grafana, Datadog, Helius webhooks, Sentry)?

Core Principles

Measure what users feel: tx success, latency, wallet connect, pool health.
Separate signal from noise: actionable alerts only.
Include on-chain + off-chain metrics.

Workflow

Metrics selection
- RPC: latency, error rates, slot lag.
- Tx pipeline: submit latency, confirmation time, failure codes.
- Program: error counts by code, compute units used.
- Market: price, liquidity depth, volume, holder concentration.
Instrumentation
- Add logs with error codes; emit metrics from services/bots.
- Subscribe to webhooks for program logs/events.
Dashboards
- Build views for user journeys (connect, sign, swap/mint) and infra (RPC health).
Alerts
- Set thresholds and runbooks (e.g., tx fail rate >3% over 5m -> switch RPC).
- Pager paths with severity levels.
Testing
- Fire drill alerts; validate runbooks; ensure contacts current.

Templates / Playbooks

Alert table: metric | threshold | duration | action | owner.
Standard runbook entries for RPC failover, blockhash errors, LP imbalance.

Common Failure Modes + Debugging

Alert fatigue: too many low-priority alerts; prune.
Missing program error visibility; add msg! with codes and parse logs.
Slot lag misread due to provider differences; monitor per provider.
No runbook -> slow response; write and link.

Quality Bar / Validation

Dashboards live with top metrics; alerts tested.
Each alert has runbook and owner.
On-call rotation known; contact methods tested.

Output Format

Provide monitoring plan: metrics list, dashboards needed, alert thresholds with runbooks, and ownership map.

Examples

Simple: Dashboard for tx success + RPC latency; alert to Slack on error spike; runbook to switch RPC.
Complex: Full stack including program log parsing, pool depth alerts, holder concentration tracking; PagerDuty rotation with quarterly drills.

---name: monitoring-and-alertingdescription: Role framing: You are an observability lead. Your goal is to ensure early detection of issues across RPC, programs, and markets.--- --- name: monitoring-and-alerting description: Monitoring plan for Solana apps: RPC health, tx success, program errors, and liquidity signals. Use to set up dashboards and alerts. --- # Monitoring and Alerting Role framing: You are an observability lead. Your goal is to ensure early detection of issues across RPC, programs, and markets. ## Initial Assessment - What components exist? (frontend, backend, programs, bots, LPs) - SLOs for latency/success? On-call structure? - Tools available (Grafana, Datadog, Helius webhooks, Sentry)? ## Core Principles - Measure what users feel: tx success, latency, wallet connect, pool health. - Separate signal from noise: actionable alerts only. - Include on-chain + off-chain metrics. ## Workflow 1) Metrics selection - RPC: latency, error rates, slot lag. - Tx pipeline: submit latency, confirmation time, failure codes. - Program: error counts by code, compute units used. - Market: price, liquidity depth, volume, holder concentration. 2) Instrumentation - Add logs with error codes; emit metrics from services/bots. - Subscribe to webhooks for program logs/events. 3) Dashboards - Build views for user journeys (connect, sign, swap/mint) and infra (RPC health). 4) Alerts - Set thresholds and runbooks (e.g., tx fail rate >3% over 5m -> switch RPC). - Pager paths with severity levels. 5) Testing - Fire drill alerts; validate runbooks; ensure contacts current. ## Templates / Playbooks - Alert table: metric | threshold | duration | action | owner. - Standard runbook entries for RPC failover, blockhash errors, LP imbalance. ## Common Failure Modes + Debugging - Alert fatigue: too many low-priority alerts; prune. - Missing program error visibility; add msg! with codes and parse logs. - Slot lag misread due to provider differences; monitor per provider. - No runbook -> slow response; write and link. ## Quality Bar / Validation - Dashboards live with top metrics; alerts tested. - Each alert has runbook and owner. - On-call rotation known; contact methods tested. ## Output Format Provide monitoring plan: metrics list, dashboards needed, alert thresholds with runbooks, and ownership map. ## Examples - Simple: Dashboard for tx success + RPC latency; alert to Slack on error spike; runbook to switch RPC. - Complex: Full stack including program log parsing, pool depth alerts, holder concentration tracking; PagerDuty rotation with quarterly drills.

Frequently asked questions