Skip to content

CMDB connectors

CMDB connectors ingest the authoritative application inventory and team ownership graph.

SCM first dependency

Connectors in this category depend on at least one SCM connector being installed first. Their findings reference silver.repositories.repository_id populated by SCM. Walk the SCM category before installing the CMDB connector.

Capability contract

CMDB sources provide the authoritative application inventory and team ownership graph. Their data model is relational. An application record references its owning team, associated repositories, and dependent services through foreign key attributes or a separate relationship table. The specification requires that related CMDB tables be ingested as separate Bronze tables and joined in Silver rather than resolved at ingestion via relationship APIs. This keeps the ingestion entry point stateless and relationship logic testable without API mocks.

Deployments routinely add custom attributes specific to the organization (for example, compliance scope or data classification). Schema on read at the Bronze layer SHALL absorb these custom fields additively without connector changes.

Authentication is typically basic auth with a service account or OAuth 2.0 client credentials. Pagination is offset based with page sizes in the thousands. Every record exposes an update timestamp column, which the connector SHALL use as the high water mark for incremental ingestion. CMDB data has no severity dimension.

Standardized mapping contribution

CMDB sources populate the Silver application, team, and ownership tables. See Standardized mapping for the full schema.

Skills

Four skills cover the connector lifecycle for CMDB sources, with category specific facts at Skills. The procedural body of each skill is documented at Connector skills.

Connectors in this category