Documentation Index
Fetch the complete documentation index at: https://docs.polystack.tech/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Monitoring scrapes metrics from standardized metric endpoints exposed by services across the infrastructure. Most infrastructure services are auto-detected via agent registration. This page covers configuring additional endpoints for application-specific exporters and managing the namespace organization of collected metrics.Prerequisites
- Administrator credentials with the
adminrole - Target endpoints must be reachable from the Monitoring collector nodes
Viewing Configured Targets
- Dashboard
- CLI
Navigate to Monitor Center > Monitoring (Scrape Targets, admin view). Each entry shows:
- URL: The endpoint being scraped
- Status:
UP(healthy) orDOWN(not reachable) - Last Scrape: Timestamp of the most recent successful scrape
- Labels: Metadata tags applied to all metrics from this target
Adding Custom Metric Endpoints
- Dashboard
- CLI
Navigate to Monitor Center > Monitoring (Add Scrape Target, admin view):
| Field | Description |
|---|---|
| URL | Full endpoint URL (e.g., http://10.0.1.71:9399/metrics) |
| Scrape Interval | How often to collect (default: 30s) |
| Labels | Key-value metadata tags for the target (e.g., service=polystack-filefs) |
| TLS Config | CA certificate path for HTTPS endpoints |
| Auth | Basic auth credentials or bearer token for secured endpoints |
Metric Namespaces
Monitoring organizes metrics by namespace. Use the namespace prefix when writing alert rules and dashboard queries:| Namespace | Source | Example Metrics |
|---|---|---|
polystack_compute | Compute node agents | cpu_utilization, memory_used_bytes |
polystack_storage | Software-Defined-Storage cluster | pool_used_bytes, osd_latency_ms |
polystack_network | Network agents | interface_rx_bytes, packet_loss_pct |
polystack_vm | Ironcore Guest Agent | vm_cpu_usage, vm_memory_rss |
polystack_filefs | File FS service | requests_total, guestfs_handles_active |
disaster-recovery | Disaster recovery agent | replication_lag_seconds, site_health |
Firewall Requirements
Metric endpoints must be accessible from the Monitoring collector nodes. Configure security groups or firewall rules to permit:| Source | Destination | Port | Protocol |
|---|---|---|---|
| Monitoring collector IP | Target node | Configured scrape port | TCP |
| Monitoring collector IP | 9100 (node exporter default) | All nodes | TCP |
| Monitoring collector IP | 9283 (Software-Defined-Storage metrics) | Storage nodes | TCP |
Monitoring collector IPs are listed under Monitor Center > Monitoring (Collectors, admin view).
Update security group rules to include all collector IPs when adding new collectors
during scale-out.
Next Steps
Agent Configuration
Configure agents and their default scrape targets on managed nodes
Alert Channels
Configure notification channels using the metric namespaces defined here
Retention Policies
Configure how long metric data from each namespace is retained
Troubleshooting
Diagnose targets in DOWN state and missing metric series