Your CMDB drifts from what is actually running.
CIs, relationships and topology live in monitoring, discovery and cloud tools, and someone updates the CMDB by hand. Records go stale, and teams stop trusting it for change approvals.
CMDB records drift out of date. Containers and cloud resources scale up and down faster than anyone can update a CI by hand, relationships break silently, and teams stop trusting the CMDB for the change approvals it was built to support.
ZigiOps syncs CIs, relationships and topology between your CMDB and the monitoring, cloud and Kubernetes tools that own the data, two-way and in real time, with no code.
Where this shows up
Specific moments this breaks today, and what changes.
Kubernetes pods scale up and down hundreds of times a day — by the time anyone updates a CI by hand, the workload it describes no longer exists, or a new one does.
A change ticket references an upstream service that was decommissioned long ago, and the CAB approves it anyway because the CMDB never caught up.
The network team updates BMC Atrium, the cloud team updates resource tags in Azure — nobody reconciles the two, so the CI record depends on who you ask.
CIs and relationships that follow what is running
Configuration data stays in step with the tools that own it, without anyone updating records by hand.
CIs, relationships and topology move both ways between your CMDB and the monitoring, cloud and Kubernetes tools that hold the live data.
Map into your existing CI types and relationships visually. ZigiOps enriches what is there and does not replace your data model.
ZigiOps stores none of the data it moves. Run it on-prem or in the cloud. ISO 27001 certified.
How it works
Link ServiceNow CMDB with monitoring, cloud and Kubernetes discovery tools that hold live CI data.
No-code mapping of CI types, attributes and topology relationships between systems.
CI records, relationships and status update in real time as your environment changes.
Integrations that feed the CMDB
Two-way pair pages between ServiceNow and the tools that hold live configuration data.
See the Incident-to-Resolution workflow →
Relevant integrations
Frequently asked questions
Which systems can feed the CMDB?
ServiceNow, BMC Remedy/Atrium, monitoring tools like Dynatrace and Datadog, cloud inventories via Azure Monitor and CloudWatch, and Kubernetes cluster state.
Will this change our existing CMDB structure?
No. ZigiOps maps into your existing CI types and relationships — it enriches what's there rather than replacing your data model.
Can it keep up with ephemeral cloud and container resources?
Yes. Sync runs continuously, so short-lived pods, instances and services are reflected (and retired) as they change instead of lingering as ghost CIs.
Does enrichment run continuously?
Yes. CI records, relationships and status update in real time as your environment changes.
Stop reconciling CMDB data by hand
See CI enrichment sync live across ServiceNow and your monitoring stack.