Collectors that monitor the services and platforms supporting your infrastructure — storage clusters, databases, monitoring systems, secret management, and DNS

These collectors monitor the services and platforms that support your infrastructure — storage clusters, databases, monitoring systems, secret management, and DNS. Each collector connects to a platform's API, discovers its components, and publishes configuration items into Parascope for tracking and correlation.

Ceph Collector

The Ceph collector discovers storage infrastructure from Ceph clusters via the Ceph Dashboard/Manager REST API.

CI Types Discovered (11)

CI Type	Description
`ceph.cluster`	Cluster identity, health status, and capacity
`ceph.mon`	Monitor daemons (consensus/quorum)
`ceph.osd`	Object Storage Daemons (data storage)
`ceph.pool`	Storage pools with replication/erasure coding config
`ceph.host`	Cluster member hosts
`ceph.mds`	Metadata Server daemons (CephFS)
`ceph.mgr`	Manager daemons
`ceph.rgw`	RADOS Gateway daemons (S3/Swift)
`ceph.rbd`	RBD block device images
`ceph.pg`	Placement groups
`ceph.filesystem`	CephFS filesystems

Authentication

Ceph Dashboard API — username/password for the Ceph Manager Dashboard REST API
Connects via the Ceph Dashboard URL (typically port 8443)

What Gets Collected

Config (tracked): Cluster health status, CRUSH map, pool configuration, OSD class and weight, daemon versions
Metrics (not tracked): Capacity usage, IOPS, throughput, OSD utilization percentages

Health Dashboard Integration

The Ceph collector feeds the Ceph Health Widget on the Parascope dashboard, showing cluster health status and capacity at a glance.

Key Relationships

OSDs member_of Cluster
Monitors member_of Cluster
Hosts member_of Cluster
Pools member_of Cluster

PostgreSQL Collector

The PostgreSQL collector discovers database infrastructure, schemas, and configuration across one or more PostgreSQL servers.

CI Types Discovered (8)

CI Type	Description
`postgresql.server`	PostgreSQL server instances
`postgresql.database`	Individual databases
`postgresql.schema`	Database schemas
`postgresql.table`	Tables with row counts and sizes
`postgresql.tableindex`	Table indexes
`postgresql.extension`	Installed extensions
`postgresql.role`	Database roles and permissions
`postgresql.replication_slot`	Replication slots

Authentication

Connection string — standard PostgreSQL connection parameters (host, port, database, user, password)
Read-only access is sufficient for collection

What Gets Collected

Config (tracked): Server version, configuration parameters, database sizes, table structures, installed extensions, replication config
Metrics (not tracked): Connection count, transaction rates, cache hit ratios

Multi-Server Support

Configure multiple PostgreSQL servers as separate sources, each with independent credentials and health tracking.

Key Relationships

Databases is_contained_by Servers
Schemas is_contained_by Databases
Tables is_contained_by Schemas

Prometheus Collector

The Prometheus collector discovers monitoring infrastructure from Prometheus servers — what targets are being monitored and what alerting rules are configured.

CI Types Discovered (3)

CI Type	Description
`prometheus.instance`	Prometheus server instances
`prometheus.target`	Monitored scrape targets with health
`prometheus.rule`	Alerting and recording rules

Authentication

HTTP — Prometheus API (typically unauthenticated or via reverse proxy)

What Gets Collected

Config (tracked): Server configuration, target endpoints and labels, rule definitions and expressions
Metrics (not tracked): Target scrape duration, sample counts

Key Relationships

Targets member_of Instance
Rules member_of Instance

Grafana Collector

The Grafana collector discovers dashboards and data sources from Grafana instances.

CI Types Discovered (3)

CI Type	Description
`grafana.instance`	Grafana server instances
`grafana.dashboard`	Dashboard definitions
`grafana.datasource`	Configured data sources

Authentication

API Key — Grafana API key or service account token with viewer permissions

What Gets Collected

Config (tracked): Dashboard titles, folder organization, panel configurations, data source types and connection details
Metrics (not tracked): Dashboard view counts

Key Relationships

Dashboards member_of Instance
Datasources member_of Instance

OpenBao Collector

The OpenBao collector discovers secret management infrastructure from OpenBao instances, with a focus on PKI certificate tracking.

CI Types Discovered (5)

CI Type	Description
`vault.instance`	OpenBao server/cluster instances
`vault.secret_engine`	Enabled secret engines (KV, PKI, Transit, etc.)
`vault.auth_method`	Authentication methods (LDAP, OIDC, AppRole, etc.)
`vault.policy`	Access control policies
`vault.pki_certificate`	Issued PKI certificates with expiration tracking

Authentication

OpenBao Token — with read-only access to sys/mounts, sys/auth, and PKI engine paths

Key Features

PKI Certificate Tracking — Monitors issued certificates and their expiration dates
Secret Engine Inventory — What secret engines are enabled and how they are configured
Auth Method Discovery — What authentication methods are available

Key Relationships

Secret Engines member_of Server
Auth Methods member_of Server
PKI Roles is_contained_by Secret Engines
PKI Certificates issued_by PKI Roles

Backstage Collector

The Backstage collector discovers service catalog entities from Backstage instances, providing visibility into your software catalog alongside your infrastructure.

CI Types Discovered (4)

CI Type	Description
`backstage.component`	Software components (services, libraries, websites)
`backstage.system`	Systems that group related components
`backstage.domain`	Business domains
`backstage.api`	API definitions

Authentication

Backstage API — Bearer token or unauthenticated access depending on your Backstage configuration

What Gets Collected

Config (tracked): Component metadata, ownership, lifecycle stage, system membership, API specifications
Relationships: Components member_of Systems, Systems member_of Domains, Components provides APIs

Keycloak Collector

The Keycloak collector discovers identity and access management configuration from Keycloak instances.

CI Types Discovered (5)

CI Type	Description
`keycloak.realm`	Identity realms
`keycloak.client`	OIDC/SAML clients
`keycloak.group`	User groups
`keycloak.role`	Realm and client roles
`keycloak.user`	User accounts

Authentication

Keycloak Admin API — Admin credentials or service account token

What Gets Collected

Config (tracked): Realm settings, client configurations, group hierarchy, role assignments, user attributes
Relationships: Clients member_of Realms, Roles member_of Realms, Groups member_of Realms, Users member_of Groups

DNS Collector

The DNS collector discovers DNS zones and records from PowerDNS authoritative servers.

CI Types Discovered (1)

CI Type	Description
`dns.zone`	DNS zones with record inventory

Authentication

PowerDNS API — API key for the PowerDNS Authoritative Server HTTP API

What Gets Collected

Config (tracked): Zone names, SOA records, record types and counts, DNSSEC configuration
Zone records (A, AAAA, CNAME, MX, TXT, SRV, etc.) are tracked within the zone CI

Key Features

FQDN Enrichment — DNS data enriches other CIs with hostname/FQDN information, enabling lookup of infrastructure by DNS name
Zone Change Tracking — Detect when DNS records are added, modified, or removed

Managing Collectors — Collector health and configuration
OS Collection — Agentless operating system discovery
CI Types — Complete CI type reference

Collector Reference: Platform and Services

On this page