Audit functionality in DI

[sathya66]

Hi All,

there are good practices for Audit , control and also bit bucket integration for version control in DIS.

is there a way for proper audit. Ie same one above( audit,control). but also WHAT has changed in the DI jobs in DIS? or any other procedures other than this for DI audit functionality to be turned on in DI. 

https://www.sas.com/content/dam/SAS/support/en/sas-global-forum-proceedings/2018/2098-2018.pdf

Thanks,

SS.

[AnandVyas]

Hi @sathya66 

For version control you can use the GIT plugin added to DIS.

https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-Studio-adds-support-for-a-Git-plug-in/td-p...

I don't understand the question about Auditing. Are you saying audit trail for any changes made in the DI Job?

[sathya66]

Thanks,
Yes,Audit trail for any changes made in the DI job/code.

[Patrick]

The paper you reference pretty much describes how things need to be done.

As for auditing changes to DIS jobs: Isn't that what you could be using GIT for? Just create a package per job and check it into bit bucket whenever you're ready to promote change to the next environment. 

[sathya66]

Git is for version control-but no way to force users to use this.
We have logs for, who updated the job and when but not WHAT.
I am after ,WHAT has changed in the DI job.

[AnandVyas]

Metadata loggers also do update changes in metadata, checkin, checkout etc.

https://documentation.sas.com/?docsetId=bisag&docsetTarget=n0pitzrsxlrvyfn1o967czb2oww2.htm&docsetVe...

Audit.Meta.Updates
is the parent logger for events that are performed on public objects. The logged events include adding, updating, deleting, checking out, checking in, and fetching objects, as well as undoing checkouts.
Audit.Meta.Updates.PublicObjects logs events about public objects in foundation and custom repositories. Audit.Meta.Updates.Project and Audit.Meta.Updates.Project.PublicObjects log information about public objects in project repositories.

[SASKiwi]

@sathya66 - If users won't use version control then you have a management problem that can't be fixed by any technical workaround.