Hi Mario/Nic
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.
Thanks
Jerry
Marking the logs during troubleshooting can be helpful for yourself and Atlassian Support. The mark will be applied to all the JIRA log files.
Optional Message:
Hi Jerry,
if you are restricted to privacy policies or you "feel unsafe" you should always obfuscate all hosts and names.
Cheers,
Mario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.