A log won't expose all your data, but if you're having problems, it may expose snippets as it logs things like "couldn't render field because of data corruption: <text with sensitive data in it> ". Anyone reading the log will get host names, user login ids and patterns of activity and usage from it.
Thanks for your answers. I think both of you are right but as a way forward I will be using build in tools within JIRA for Logging and Profiling. It allows you to mark the location in the log file from where you are interested in logged actions. You are also able to 'Log Rollover' so start your logs in fresh files.
Both functions will help you limit the shared data to the specific point in time or taken actions within JIRA.
Hiding all the sensitive data would be rather impossible.
Marking the logs during troubleshooting can be helpful for yourself and Atlassian Support. The mark will be applied to all the JIRA log files.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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