Hi,
We are trying to set up the auditing in order to have the history of our report runs.
What I noticed is that we don't get the same level of details when we run it from the GUI or from the WS although they should be similar.
Our configuration (standard):
<entry key="WEB_SERVICES"> <map> <!--key - name of the event type. value - comma separated list of property types--> <entry key="login" value="username,organization,loginFailure,exception"/> <entry key="runReport" value="reportParam,reportRenderingTime,reportRenderingStartTime,queryExecutionTime,queryExecutionStartTime,reportExecutionTime,reportExecutionStartTime,dataSource,sqlQuery,domainQuery,exception"/> </map> </entry> <entry key="GUI"> <map> <!--key - name of the event type. value - comma separated list of property types--> <entry key="login" value="username,organization,loginFailure,exception"/> <entry key="logout" value="exception"/> <entry key="import" value="exception,update,skip-user-update,include-access-events,include-audit-events,include-monitoring-events,include-server-settings"/> <entry key="export" value="exception,roles,users,uris,report-jobs,everything,include-access-events,repository-permissions,role-users,include-audit-events,include-monitoring-events"/> <entry key="runReport" value="reportParam,reportRenderingTime,reportRenderingStartTime,queryExecutionTime,queryExecutionStartTime,reportExecutionTime,reportExecutionStartTime,reportMemorySize,dataSource,sqlQuery,domainQuery,exception"/> ... </map> </entry>
So In both case, reportParam is present.
What we see in the audit though is that for the runReport events, we only see the events reportExecutionStartTime and reportExecutionTime
What could be an explanation and how can we change that?
(we're seeing this behaviour both on jasperserver-pro 6.0.1 and 6.1.1)
Thank you.
0 Answers:
No answers yet
We are experiencing the same problem. By any chance, did you guys find a resolution yet?
We are experiencing the same issue. The reportParam information used to be loged in the audits for reports executed through the API with v5.5.0.
Is this a known bug with version 6.0.0 and later ? Any plans to correct the issue ?