Tracking changes to CIs and relationships
This use case describes how to keep track of the changes to CIs and relationships in the BMC CMDB using the auditing feature of BMC Remedy AR System to track changes to instance data. You enable BMC CMDB auditing on a per-class basis, and you select which attributes trigger an audit and which are written as a result.
If you use BMC Asset Management with BMC CMDB, you could instead track changes with the Compare Dataset reconciliation activity.
Tracking changes to CIs and relationships scenario
Tracking changes to CIs and relationships workflow
Product | Component | Console | User | Action | Reference |
---|---|---|---|
Class Manager | Configuration manager | Selecting the instances and attributes to be included in the audit. | Creating or modifying classes by using Class Manager |
AR System Administrator | Configuration manager | Set up events subscriptions and event channels to receive CI change events. | Receiving CI change events with Event Channels |
Class Manager | Configuration manager | Enable auditing for specific classes to identify changes to CIs and relationships. | Enabling audits for classes and attributes |
BMC Asset Management | Asset manager | Run a compare dataset activity between the sandbox and the BMC Asset. |
Tracking changes to CIs and relationships results
Calbro Service can now track the changes to CIs and relationships.
Tracking changes to CIs and relationships benefits
Tracking changes allows Calbro Services to make sure their business services are monitored for changes thereby empowering them to avoid service interruptions.
Related topics
Differences between auditing and the compare dataset activity
Comments
Log in or register to comment.