monitoring-stack

Included with Lifetime

$97 forever

Manage the homelab monitoring stack at ~/docker/stacks/monitoring/. Services: Prometheus, Grafana, Alertmanager (Telegram via DeLoNETBot), cadvisor, node-exporter, process-exporter, Loki, OTEL collector, Dockge, Uptime Kuma, health-monitor. Use when: (1) adding, editing, or debugging Prometheus alert rules, (2) managing or restarting monitoring services, (3) checking alert delivery or Telegram bot status, (4) diagnosing system performance issues (CPU hogs, memory bloat, swap pressure), (5) adding new scrape targets to Prometheus, (6) configuring Grafana dashboards or datasources, (7) any task referencing "monitoring", "alerts", "prometheus", "grafana", "cadvisor", "process-exporter", "alertmanager", "telegram alerts", or "DeLoNETBot".

Backend & APIsscripts

What this skill does


# Monitoring Stack

Stack root: `~/docker/stacks/monitoring/`

## Architecture

See [references/architecture.md](references/architecture.md) for full service map, ports, URLs, and data flow.

## Common Operations

### Restart the full stack
```bash
cd ~/docker/stacks/monitoring && docker compose up -d
```

### Restart a single service
```bash
cd ~/docker/stacks/monitoring && docker compose up -d <service-name>
```

### Hot-reload Prometheus rules (no restart needed)
```bash
curl -s -X POST http://localhost:9472/-/reload
```

### Hot-reload Alertmanager config (no restart needed)
```bash
curl -s -X POST http://localhost:9784/-/reload
```

### Verify process-exporter is scraping
```bash
curl -s http://localhost:9256/metrics | grep namedprocess | head -5
```

### Test Telegram alert delivery
```python
import urllib.request, json
url = "https://api.telegram.org/bot<TOKEN>/sendMessage"
data = json.dumps({"chat_id": 7564050286, "text": "Test alert", "parse_mode": "HTML"}).encode()
req = urllib.request.Request(url, data=data, headers={"Content-Type": "application/json"})
urllib.request.urlopen(req)
```

Bot token is in `~/docker/stacks/monitoring/alertmanager/config.yml`.

## Adding New Alert Rules

See [references/alert-rules-guide.md](references/alert-rules-guide.md) for rule file locations, PromQL patterns, severity conventions, and examples.

**Quick path:** Edit the appropriate rule file, then hot-reload Prometheus:
```bash
curl -s -X POST http://localhost:9472/-/reload
```

### Rule file locations
| File | Scope |
|------|-------|
| `prometheus/alert_rules.yml` | Container CPU, memory, availability |
| `prometheus/system_alerts.yml` | Host system + per-process hogs |
| `prometheus/rules/docker-health.yml` | Container health checks, restart loops |

## Alerting

Alerts route to Telegram via **@DeLoNETBot** (chat_id: `7564050286`).

Config: `alertmanager/config.yml`

Severity routing:
- `critical`: repeat every 1h
- `warning`: repeat every 4h

## Key Design Decisions

- **cadvisor is resource-capped**: 1 CPU, 512M memory, 30s housekeeping interval, pruned metrics. Without these limits it will eat an entire core scanning 69+ containers.
- **process-exporter exists specifically to catch host-level hogs** that cadvisor and node-exporter miss (per-process CPU/memory).
- **Duplicate rules were consolidated**: `docker-health.yml` only has health-check and restart-loop rules. CPU/memory rules live in `alert_rules.yml`.

## Diagnosing Performance Issues

When the system stutters, check in this order:

1. `ps aux --sort=-%cpu | head -15` - find CPU hogs
2. `free -h` - check swap pressure
3. `sensors` - check thermals (Tctl)
4. `docker stats --no-stream` - find container hogs

The alert rules should catch most of these automatically now. If they don't fire, check:
- Prometheus is up: `curl http://localhost:9472/-/healthy`
- Alertmanager is up: `curl http://localhost:9784/-/healthy`
- Rules loaded: `curl http://localhost:9472/api/v1/rules | python3 -m json.tool | head -40`

Files: 4

Size: 12.7 KB

Complexity: 49/100

Category: Backend & APIs

Source: https://github.com/delorenj/skills/tree/main/monitoring-stack

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts