We need to have audit logs for source code, tickets and our documents. And are considering to use the JIRA suite to help (current system doesn't cut it).
I have some questions I hope you will answer
Not really an answer - but I don't see the need for logging read accesses (beside statistical issues). If you want your repository to be read only by certain people you should use access control to restrict the access - as reading is a non-modifying action on the repository, everybody who has granted access to your repo should be allowed to read it (no need for logging here).
For Stash, the audit logs (under STASH_HOME/logs/audit) track selected events only. Have a look at https://confluence.atlassian.com/display/STASH/Audit+events+in+Stashfor a list of events that can be tracked. Note that by default not even all these events are included in the audit log; only the 'high' priority events are logged, but you can configure that in the stash-config.properties. Have a look at https://confluence.atlassian.com/display/STASH/Stash+config+properties#Stashconfigproperties-Auditfor more information on how to do that.
While the access logs don't track repository read access, you could still use the access logs for that. They record every request that's made over HTTP and SSH, complete with the authenticated user. See https://confluence.atlassian.com/display/STASHKB/Stash+Log+Formatsfor a description of the access log format.
Hope this helps!
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs