Best practices for CMDB enabling of audit for fields/tables

[Silvie Cady]

Hi All ,

Our team/s are asking if we could enable full audit history for all CIs, meaning for all classes and its corresponding fields.

Could this have some potential performance impact? Is this recommended? What is the reason that by default the audit its not activated?

What is the best practice ?

Thank you all for answers.

Best,

Silvie

[AbhishekGardade]

Hello Silvie,

Tables do not derive the audit flags from parent or child audited tables.

For example, if you enable auditing for the cmdb_ci table, only CI's stored in that base table are audited. Likewise, if you enable auditing for the cmdb_ci_computer table, only the computer CI records are audited, including any fields on the cmdb_ci_computer table that are derived from the cmdb_ci table.

Caution: Auditing certain system tables that receive a large amount of traffic, such as Workflow Contexts [wf_context], can impact performance and is not recommended.

The solution is to use the audit by whitelisting procedure. Click the following link to read more about this.

https://docs.servicenow.com/bundle/madrid-platform-administration/page/administer/security/task/secu...

Please mark as Correct Answer/Helpful, if applicable.
Thanks!
Abhishek Gardade

[Silvie Cady]

Thanks Abhishek,

ok, So with this haveing in mind, would you recommend to enable full audit on one of the classes in CMDB. for example Server ?

Thank you,

Silvie

[AbhishekGardade · Accepted solution]

With considering my experience on cmdb. if you have lots data coming in server table or other cmdb table, audit table will receive a large amount of traffic and it may can impact performance , may be slowing system down.

Its just my thinking/opinion. I Recommend you to take advice from SNOW support or any cmdb expert.

Please mark as Correct Answer/Helpful, if applicable.
Thanks!
Abhishek Gardade

[Silvie Cady]

Thanks Ahishek, 

I appreciate our input

Best,

Silvie