Capturing Who Modified and Deployed Reports in Audit/Audit Ext

[Jchrisler]

Hi all, I installed and got the Audit Extension going.  Works great... almost. 

I am trying to obtain the what, when and who of report mods.  I've got the what and when. Problem is with the who -  1. who modified reports and 2. who deployed reports from our test to prod environment.   Number 1 is no problem with the Audit > Actions by Object query subject, but number 2 is problematic. 

I can capture what reports and when they were updated in RS or a via a deployment with the Audit Extension.  Problem is the Audit Extension > Content  Audit > Item Details carries only the owner of the report, not the modified by.

Is there something I'm missing or does my suspicion that the Audi and Audit Extension tables suck hold true?   :P
Is there another tool out there that would give me this info?  BSP MetaManager?
Or... should I add to the Report mod process that a report developer takes ownership of the report before modifying it?

Thanks for your help!

[bdbits]

How are your reports getting transferred? My experience is that only administrators, or automated processes, normally have permissions to do content deployments. And there is normally a transfer request process around that, which generates a paper trail.

I would think that if the information is somewhere within the Cognos content store, MetaManager probably has something to report on it.

[cognostechie]

Try to see if there is a query subject which shows who ran the action of 'Import' in Production. That's the person who did the deployment to Production. If you have a generic login for doing this, which some companies have, then it won't help.

[mcc.chernandez]

Something like this against Audit db would give you deployment info:

SELECT *
FROM COGIPF_ACTION a WITH (NOLOCK)
inner join COGIPF_USERLOGON U WITH (NOLOCK)
   on a.COGIPF_SESSIONID = U.COGIPF_SESSIONID and 'Logon' = U.COGIPF_LOGON_OPERATION
where a.COGIPF_TARGET_TYPE = 'IMPORTDEPLOYMENT'
order by a.COGIPF_LOCALTIMESTAMP desc

This can take a long time with a large Audit db. This page here (and others on their blog) has some interesting ideas: http://www.envisn.com/envisn-cognos-blog/bid/103289/Advanced-Tips-for-Cognos-Audit-Data