Skip to main content

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.
Administrator Access Required — This operation requires the admin role. Contact your Polystack administrator if you do not have sufficient permissions.
Prerequisites
  • Administrator credentials with the admin role
  • Target endpoints must be reachable from the Monitoring collector nodes

Viewing Configured Targets

Navigate to Monitor Center > Monitoring (Scrape Targets, admin view). Each entry shows:
  • URL: The endpoint being scraped
  • Status: UP (healthy) or DOWN (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

Navigate to Monitor Center > Monitoring (Add Scrape Target, admin view):

Metric Namespaces

Monitoring organizes metrics by namespace. Use the namespace prefix when writing alert rules and dashboard queries:

Firewall Requirements

Metric endpoints must be accessible from the Monitoring collector nodes. Configure security groups or firewall rules to permit:
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