Collector Reference: Infrastructure

Parascope's infrastructure collectors discover and monitor the foundational platforms that run your workloads — container orchestrators, hypervisors, cloud platforms, and network source-of-truth systems. Each collector connects to one or more instances of its target platform and periodically scans for configuration items, relationships, and changes.

---

Kubernetes Collector

The Kubernetes collector discovers workloads, configuration, and infrastructure across one or more Kubernetes clusters.

CI Types Discovered (16)

Authentication

• In-cluster ServiceAccount — automatic when running inside the target cluster
• Kubeconfig — for remote clusters, uses standard kubeconfig files

Collection Modes

• Periodic — Full inventory scan on a fixed interval
• Watch — Real-time event streaming for near-instant change detection

Multi-Cluster Support

Configure multiple Kubernetes clusters as separate sources. Each cluster gets its own scope ID for data isolation and independent health tracking.

Key Relationships

• Pods runs_on Nodes
• Pods is_contained_by Namespaces
• Deployments manages ReplicaSets manages Pods
• Services selects Pods
• PVCs mounts PVs

---

Proxmox Collector

The Proxmox collector discovers virtualization infrastructure from Proxmox VE clusters.

CI Types Discovered (5)

Authentication

• API Token — recommended, uses Proxmox API tokens with configurable privileges
• Username/Password — falls back to ticket-based authentication

What Gets Collected

• Config (tracked): VM/container hardware config (CPU, memory, disk, network), status, node membership
• Metrics (not tracked): CPU utilization, memory usage, disk I/O, uptime

Key Relationships

• VMs/Containers runs_on Nodes
• Nodes member_of Cluster
• VMs/Containers use Storage

---

OpenStack Collector

The OpenStack collector discovers cloud resources across one or more OpenStack deployments, including both private clouds and public OpenStack deployments.

CI Types Discovered (17)

Authentication

• Application Credentials — recommended, scoped to specific project access
• Username/Password — standard Keystone authentication

Multi-Cloud Support

Configure multiple OpenStack deployments as separate sources with independent credentials and scoping. Per-source configuration supports:

• all_projects: false — limit to authenticated project only
• Selective collector disabling (e.g., skip image collector if credentials lack permission)

Key Relationships

• Instances runs_on Hypervisors (when admin access available)
• Instances use Flavors, Images, Networks
• Ports connects_to Networks/Subnets
• Volumes attached_to Instances

---

Netbox Collector

The Netbox collector synchronizes network infrastructure data from NetBox, the network source of truth.

CI Types Discovered (14)

Authentication

• API Token — standard NetBox API token with read permissions

Key Features

• IPAM Sync — IP address and prefix data for network planning
• DCIM Sync — Physical device, rack, and site inventory
• API Pagination — Handles large NetBox instances with automatic pagination
• Enrichment Source — Netbox data enriches CIs from other collectors (e.g., adding physical location to a Proxmox node)

Key Relationships

• Devices located_in Racks located_in Sites
• Interfaces member_of Devices
• IP Addresses assigned_to Interfaces
• Cables connects Interfaces

---

Related Documentation

• Managing Collectors — Collector health and configuration
• Collector Reference: Platform Services — Ceph, PostgreSQL, Prometheus, Grafana, Vault, DNS collectors
• Collector Reference: Discovery — OS and SNMP collectors
• CI Types — Complete CI type reference