Skip to main content

History & Audit

History and audit views in CMDB help you answer detailed questions about how a configuration item has changed over time, who made those changes, and when they occurred.

Viewing Change History​

Each CI record includes standard metadata such as creation and last‑modified timestamps, as well as the user or process responsible for the latest change, where applicable. For many key fields, history tracking can record previous values so you can:

  • See a timeline of changes to configuration, tags, ownership, and relationships.
  • Compare current and prior states when troubleshooting incidents or regressions.
  • Confirm that changes occurred within approved maintenance windows.

Where enabled, change history is visible directly from the CI record via a dedicated CHANGE MANAGEMENT tab (the Changes History section) and can be filtered by time range or field.

For the CHANGE MANAGEMENT tab layout and panels, see the Tabs and CI Detail Page Layout.

Audit Trails and Compliance​

For audit and compliance use cases, CMDB change data can help demonstrate:

  • When specific configuration or security controls were enabled or modified.
  • Which user, integration, or process initiated a change.
  • How long a system remained in a non‑compliant or degraded state.

Use CMDB reporting and dashboards to aggregate changes across scopes (applications, accounts, environments, business units) and retain evidence for internal and external reviews.

Exporting History​

When you need to retain change history outside Cloudaware or perform deeper analysis:

  • Use CMDB reporting and export features to download change‑related data for selected CIs or scopes.
  • Where supported, leverage APIs to pull change and history data into external analytics, SIEM, or archival systems.
  • Coordinate with your Cloudaware representative to understand available retention options and platform limits for history and audit logs in your environment.