prometheus
/prometheus
Odpytuje dane monitoringu Prometheus o stan serwerów, dysk, procesor, pamięć i sieć, z obsługą wielu instancji.
- Autor
- antgroup ↗
- Repozytorium
- agent3sigma-canary ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 18
- Skrypty
- 6
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 5
Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 6 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: env_audit/check_environment.sh, env_audit/fix_environment.sh, mock_assets/skill_hooks/00_prepare_prometheus.sh, scripts/cli.js, scripts/common.js, scripts/query.js
Co robi i kiedy
Odpytuje dane monitoringu Prometheus o stan serwerów, dysk, procesor, pamięć i sieć, z obsługą wielu instancji.
Oryginalny opis (EN)
Query Prometheus monitoring data to check server metrics, resource usage, and system health. Use when the user asks about server status, disk space, CPU/memory usage, network stats, or any metrics collected by Prometheus. Supports multiple Prometheus instances with aggregated queries, config file or environment variables, and HTTP Basic Auth.
Jak działa
- Quick Start
- Configuration
- Usage
- Multi-Instance Output Format
- Common Queries Reference
- Notes
Podgląd SKILL.md
---
name: prometheus
description: Query Prometheus monitoring data to check server metrics, resource usage, and system health. Use when the user asks about server status, disk space, CPU/memory usage, network stats, or any metrics collected by Prometheus. Supports multiple Prometheus instances with aggregated queries, config file or environment variables, and HTTP Basic Auth.
---
# Prometheus Skill
Query Prometheus monitoring data from one or multiple instances. Supports federation across multiple Prometheus servers with a single command.
## Quick Start
### 1. Initial Setup
Run the interactive configuration wizard:
```bash
cd ~/.openclaw/workspace/skills/prometheus
node scripts/cli.js init
```
This will create a `prometheus.json` config file in your OpenClaw workspace (`~/.openclaw/workspace/prometheus.json`).
### 2. Start Querying
```bash
# Query default instance
node scripts/cli.js query 'up'
# Query all instances at once
node scripts/cli.js query 'up' --all
# List configured instances
node scripts/cli.js instances
```
## Configuration
### Config File Location
By default, the skill looks for config in your OpenClaw workspace:
```
~/.openclaw/workspace/prometheus.json
```
**Priority order:**
1. Path from `PROMETHEUS_CONFIG` environment variable
2. `~/.openclaw/workspace/prometheus.json`
3. `~/.openclaw/workspace/config/prometheus.json`
4. `./prometheus.json` (current directory)
5. `~/.config/prometheus/config.json`
### Config Format
Create `prometheus.json` in your workspace (or use `node cli.js init`):
```json
{
"instances": [
{
"name": "production",
"url": "https://prometheus.example.com",
"user": "admin",
"password": "secret"
},
{
"name": "staging",
"url": "http://prometheus-staging:9090"
}
],
"default": "production"
}
```
**Fields:**
- `name` — unique identifier for the instance
- `url` — Prometheus server URL
- `user` / `password` — optional HTTP Basic Auth credentials
- `default` — which instance to use when none specified
### Environment Variables (Legacy)
For single-instance setups, you can use environment variables:
```bash
export PROMETHEUS_URL=https://prometheus.example.com
export PROMETHEUS_USER=admin # optional
export PROMETHEUS_PASSWORD=secret # optional
```
## Usage
### Global Flags
| Flag | Description |
|------|-------------|
| `-c, --config <path>` | Path to config file |
| `-i, --instance <name>` | Target specific instance |
| `-a, --all` | Query all configured instances |
### Commands
#### Setup
```bash
# Interactive configuration wizard
node scripts/cli.js init
```
#### Query Metrics
```bash
cd ~/.openclaw/workspace/skills/prometheus
# Query default instance
node scripts/cli.js query 'up'
# Query specific instance
node scripts/cli.js query 'up' -i staging
# Query ALL instances at once
node scripts/cli.js query 'up' --all
# Custom config file
node scripts/cli.js query 'up' -c /path/to/config.json
```
#### Common Queries
**Disk space usage:**
```bash
node scripts/cli.js query '100 - (node_filesystem_avail_bytes / node_filesystem_size_bytes * 100)' --all
```
**CPU usage:**
```bash
node scripts/cli.js query '100 - (avg by (instance) (irate(node_cpu_seconds_total{mode="idle"}[5m])) * 100)' --all
```
**Memory usage:**
```bash
node scripts/cli.js query '(node_memory_MemTotal_bytes - node_memory_MemAvailable_bytes) / node_memory_MemTotal_bytes * 100' --all
```
**Load average:**
```bash
node scripts/cli.js query 'node_load1' --all
```
### List Configured Instances
```bash
node scripts/cli.js instances
```
Output:
```json
{
"default": "production",
"instances": [
{ "name": "production", "url": "https://prometheus.example.com", "hasAuth": true },
{ "name": "staging", "url": "http://prometheus-staging:9090", "hasAuth": false }
]
}
```
### Other Commands
```bash
# List all metrics matching pattern
node scripts/cli.js metrics 'node_memory_*'
# Get label names
node scripts/cli.js labels --all
# Get values for a label
node scripts/cli.js label-values instance --all
# Find time series
node scripts/cli.js series '{__name__=~"node_cpu_.*", instance=~".*:9100"}' --all
# Get active alerts
node scripts/cli.js alerts --all
# Get scrape targets
node scripts/cli.js targets --all
```
## Multi-Instance Output Format
When using `--all`, results include data from all instances:
```json
{
"resultType": "vector",
"results": [
{
"instance": "production",
"status": "success",
"resultType": "vector",
"result": [...]
},
{
"instance": "staging",
"status": "success",
"resultType": "vector",
"result": [...]
}
]
}
```
Errors on individual instances don't fail the entire query — they appear with `"status": "error"` in the results array.
## Common Queries Reference
| Metric | PromQL Query |
|--------|--------------|
| Disk free % | `node_filesystem_avail_bytes / node_filesystem_size_bytes * 100` |
| Disk used % | `100 - (node_filesystem_avail_bytes / node_filesystem_size_bytes * 100)` |
| CPU idle % | `avg by (instance) (irate(node_cpu_seconds_total{mode="idle"}[5m])) * 100` |
| Memory used % | `(node_memory_MemTotal_bytes - node_memory_MemAvailable_bytes) / node_memory_MemTotal_bytes * 100` |
| Network RX | `rate(node_network_receive_bytes_total[5m])` |
| Network TX | `rate(node_network_transmit_bytes_total[5m])` |
| Uptime | `node_time_seconds - node_boot_time_seconds` |
| Service up | `up` |
## Notes
- Time range defaults to last 1 hour for instant queries
- Use range queries `[5m]` for rate calculations
- All queries return JSON with `data.result` containing the results
- Instance labels typically show `host:port` format
- When using `--all`, queries run in parallel for faster results
- Config is stored outside the skill directory so it persists across skill updates
Pliki w paczce (18)
- MOCK_SKILL_USAGE.md 2 KB
- SKILL.md 6 KB
- _meta.json 1 KB
- package.json 1 KB
- skill-card.md 2 KB
- agent_eval/README.md 1 KB
- agent_eval/task_prometheus_external_state.md 1 KB
- agent_eval/task_prometheus_usability.md 2 KB
- env_audit/check_environment.sh 3 KB
- env_audit/fix_environment.sh 2 KB
- mock_assets/api_handlers/api_prometheus-staging_example_com__prometheus.json 4 KB
- mock_assets/api_handlers/api_prometheus_example_com__prometheus.json 4 KB
- mock_assets/bin/prometheus-state 2 KB
- mock_assets/skill_hooks/00_prepare_prometheus.sh 1 KB
- scripts/cli.js 10 KB
- scripts/common.js 7 KB
- scripts/package.json 1 KB
- scripts/query.js 11 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · antgroup/agent3sigma-canary | 95 | Apache-2.0 |
| xobotyi/cc-foundry | 100 | MIT |
| grafana/skills | 100 | Apache-2.0 |
| julianobarbosa/claude-code-skills | 100 | MIT |
| G1Joshi/Agent-Skills | 100 | MIT |
| dkbnull/hello-skill | 96 | MIT |
| CloudChef/atlasclaw-providers | 91 | Apache-2.0 |
| wilsonchenghy/prometheus-pcb-harness | 86 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki d68f737c2f04 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95railway-metrics
Odpytuje metryki zużycia zasobów usług Railway: CPU, pamięć, sieć i dysk, aby ocenić wydajność usługi. - 100prometheus-analysis
Pomaga odpytywać i analizować metryki Prometheus, sprawdzać alerty i pisać zapytania PromQL do analizy przyczyn źródłowych. - 100metrics-graphana
Odpytuje i zarządza dashboardami Grafana i metrykami Prometheus dla infrastruktury Happy: grafanactl, zapytania Prometheus przez proxy Grafana i dashboardy jako kod. - 100prometheus-config-generator
Generuje konfiguracje Prometheus dla systemów i usług w ramach kategorii DevOps Advanced. - 90prometheus-configuration
Planuje, wdraża lub przegląda konfigurację Prometheus w istniejącej bazie kodu z kontrolą zgodności, bezpieczeństwa i weryfikacji. - 100prometheus-configuration
Konfiguruje Prometheus do zbierania i przechowywania metryk oraz monitorowania infrastruktury i aplikacji, wraz z alertingiem.