BookmarkSubscribeRSS Feed
sathya66
Barite | Level 11

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.

6 REPLIES 6
AnandVyas
Ammonite | Level 13

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
Barite | Level 11
Thanks,
Yes,Audit trail for any changes made in the DI job/code.
Patrick
Opal | Level 21

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
Barite | Level 11
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
Ammonite | Level 13

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
PROC Star

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

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 6 replies
  • 1105 views
  • 2 likes
  • 4 in conversation