A CMDB is only as good
as whatever fills it.
CerteroX keeps your ServiceNow configuration database filled with accurate, current device information automatically, so the service desk can trust what it reads.
Windows, macOS and Linux computers arrive with their disks, network adapters, memory modules, volumes, software and software installations. SNMP network devices arrive on the same run.
CMDB sync · scheduled run
IllustrativeCertero ServiceNow Application
Staging cleared, datasources queried, transforms run
- Staging tables cleared before the first query
- done
- Windows computers disks, adapters, memory, volumes
- staged
- macOS and Linux computers the same record types, the same run
- staged
- SNMP network devices their own datasource
- staged
- Transforms into the CMDB one transform map per datasource
- running
History record
pending → running → completed
ServiceNow Partner
Certero inventory synchronised into the ServiceNow CMDB
A record nobody updates is a record nobody trusts.
A configuration database is accurate on the day someone fills it in, then drifts as machines change. Service, security and change decisions end up based on old information, and every clean-up project starts the decay again. CerteroX feeds it automatically on every run, so it stays right without anyone having to remember.
- Cost
Stop paying for clean-up projects.
Accuracy comes from a regular automatic feed rather than periodic manual effort, so the same work is not bought twice.
- Risk
Decisions based on what is really there.
Change, incident and security teams work from current records for Windows, Mac and Linux machines and network devices, not from a snapshot.
- Effort
Nothing depends on memory.
Every run is logged and accounted for, so gaps are visible and fixed rather than found during an incident.
Two of the five disciplines.
Each runs standalone and shares one asset model, so the parts of this that span products need no integration work.
Running the SAM or IT side? The full detail covers how the figures are built, what each part of the platform does and the questions practitioners ask us most.
Show advanced detailOpen a CI.
See what arrived under it.
A sync run walked end to end: staging cleared, each datasource paged out of the API, each transform map writing into the CMDB, and the history record it leaves behind. Tell us which CMDB classes matter most to your service desk and we open those first.
Nothing to connect, and someone on the call who can answer for the datasources and the transform maps.