Implement a way to save audit search to repository

[colindstephenson]

Hi,

We are currently testing out the audit dashlet and so far it looks to provide everything we need from an audit perspective. What would be really beneficial is a way to say the audit searches back to the repository. Not sure how to log this as an enhancement request ...

Thanks, Colin.

[wabson]

Tagged as an enhancement. Are you interested in helping to implement this? The upcoming Global Hackathon would be an ideal time if you need some handholding to help you get started.

[colindstephenson]

I guess the rule of "Don't suggest anything that you are not prepared to do yourself" applies here :) I will check with my "social coordinator" on this.

[romainguinot]

Couple of things to note here :

• The audit API (repository side) only allows exact matches on the audit entry values.
• The audit dashlet config dialog allows to preconfigure a repository-side search using the above API. This is saved in the dashlet config, and this is used to get the JSON result feed that will ultimately be parsed client-side for repo results. Depending on your needs, this may be a way to achieve what you want (see the config parameters description in the README).
• The audit dashlet itself then has a search box that allows more advanced searching such as field filtering, regular expression matching, etc... However, this is a post-processing search that is not run server side, it is excluding non-matching entries from the resultset returned by the repository, and therefore excluding them from being displayed.

I guess one could add a field in the dashlet config so that a client-side post-processing search expression is saved as well in the dashlet's config, but i have a feeling this may not be of general value. This would therefore be best done as part of an integration/customization project on your end.

It could be worth logging an enhancement case for the audit API server-side/repo search capabilities as well, if need be.

Does this help you out ?

[colindstephenson]

Looking at my initial post, there may be some ambiguity. I probably should have said "save audit search results"

After we run the query and have the results in the dashlet, we have a need to save these search results to the repository so that when the auditors reviewing sites, we can demonstrate certain events have occurred to them.

Saving the raw JSON stream to the repository would be fine as then some actions could be applied on top to transform to HTML or some other presentation document.

Thanks, Colin.