5 Replies Latest reply: Mar 5, 2012 11:26 PM by Vinod Gaidhani RSS

How CI Audit works?

Vinod Gaidhani

Hi All,

 

I have enabled audit on one of the attriubute on Computer System class and which is capturing any changes I made through AST:Computer System form. i.e. through Asset Management. Here, I want auditing should also work when Atrium Discovery find's any changes in CI and when reconciliation updates BMC.ASSET dataset, which is not happening with current settings. Please let me know if any additional configuration require for the same.

 

Thanks,

Vinod.

  • 1. How CI Audit works?
    avalveka

    Please check the below settings -

     

    You can do the following settings by class manager through Atrium Explorer -

     

    Step01:

    Set following configuration for BMC_Computer_System

    BMC_Computer_System – Audit type set as COPY

    Attributes Audit configuration:

    • HostName – audit
    • firmware_version – copy
    • Domain – audit & copy
    • Workgroup – none

     

    Step02:

    From aradmin verify the use cases:

    Copy auditing creates a copy of each audited instance. When you enable Copy auditing for a class, each form pertaining to that class is duplicated to create audit forms that hold audited instances. This includes forms from superclasses, because they hold data for instances of their subclasses. The audit forms are automatically named with the suffix :AUDIT.

     

    Step03:

    From aradmin verify following:

    • For BMC_ComputerSystem regular form audit properties
    • For BMC_ComputerSystem join form audit properties
    • For BMC_ComputerSystem:Audit form verify and add hidden fields Audit Join Key, Audit Date, User, and Action

     

    Step04:          

    From Atrium Explorer create instance of BMC_ComputerSystem.

    From view history search for the CI and view audit history for create

     

    Result: Audit record for create should be created with having values for Audit Join Key, Audit Date, User, and Action (4 for create).

     

    Step05:

    Enter value for Hostname (audit type - audit)

    From view history search for the CI and view audit history for modify

     

    Result: Audit record for modify should be created showing value for Hostname and Action as 2.

     

    Step06:

    Enter value for firmware_version (audit type - copy)

    From view history search for the CI and view audit history for modify

     

    Result: No audit record should be created for copy type audit option set for attributes.

     

     

     

    Step07:

    Enter value for Domain (audit type – audit & copy)

    From view history search for the CI and view audit history for modify

     

    Result: audit record should be created for modify showing values for field domain, firmware_version. Value for Hostname should not be visible. Action set as 2

     

    Step08:

    Modify value for only Hostname (audit type - audit)

    From view history search for the CI and view audit history for modify

     

    Result: audit record should be created for modify showing values for changed value for Hostname, previous value for Domain and firmware_version. Action set as 2

     

    Step09:

    Modify value for all attributes HostName, firmware_version, Domain and Workgroup

    From view history search for the CI and view audit history for modify

     

    Result: audit record should be created for modify showing values for all except Workgroup. Action set as 2

     

    Step10:

    Delete the CI from database

     

    Result: audit record should be created for delete operation. Action set as 8

    Issue: All audit record is deleted

  • 2. How CI Audit works?
    Vinod Gaidhani

    Hello Abhijit,

     

    I got this concept of Auditing, but somehow it is not working when I am running Reconciliation jobs. Changes made by Reconciliation job are not captured in Audit log.

     

    Can you please confirm if any settings required for capturing recon job changes. Please let me know.

     

    Thanks,

    Vinod Gaidhani.

  • 3. How CI Audit works?
    Jayant Dusane

    Hi Vinod,

     

    Can you verify if the audit functionality is not working only after recon... Or its not even working after changes made manually.

    Please update us.....

     

    ---------

    JD

  • 4. How CI Audit works?
    Vinod Gaidhani

    Yes, as already specified, it works through Asset Management but not when Reconciliation job runs and changes any of Audit attribute.

  • 5. How CI Audit works?
    Vinod Gaidhani

    Hello All,

     

    Thanks for your replies. Issue is resolved for me now. And No surprise as I was guessing, it is a Known Issue on BMC Knownledge Base as "SW00370909".

     

    Issue Details:

     

    In Class Manager, the audited values do not display properly in the View History of the CI

    when:

      auditing is turned on for the class

      Audit Type is set to Copy

      auditable attribute is changed (for example, Audit Option of attribute is set to Audit &

    Copy)

     

    Workaround:

    1 Open the Server Information window in the AR System Administration Console.

    2 Navigate to the Configuration tab.

    3 Select the Disable Audit Only Change Fields option.

    4 Click OK.

    If you still cannot see the audited values, perform the following additional steps:

    1 In BMC Remedy Developer Studio, open the class form. For example, the form name for the

    BMC_ComputerSystem class is BMC.CORE:BMC_ComputerSystem.

    2 Choose Form > Form Properties.

    3 Select Audit on the left pane.

    4 Set the Audit Only Changed Fields option to No.

    5 Save your changes.

     

    My Comment: First four steps from workarround resolves my issue. FYI.