Follow

How To Turn On Detailed Logging in Gliffy Diagrams for JIRA

Gliffy support may ask you to product a "Support Zip" to help in troubleshooting an issue.

The process may be different depending on the version of JIRA you use, but the concepts are the same:

  • Turn gliffy logging to DEBUG (by setting 'com.gliffy' = DEBUG)
  • Reproduce the error
  • Generate a support zip

Recent versions of JIRA, allow you to modify logging dynamically via the Administration console. Please follow the instructions here:

https://confluence.atlassian.com/display/JIRA/Logging+and+Profiling#LoggingandProfiling-logging_temp

Once you recreate the issue, please generate a support zip using the instructions here:

https://confluence.atlassian.com/display/JIRA/Getting+Help#GettingHelp-CreatingaSupportZip

 

Older versions of JIRA may require the following instructions:

To turn on detailed logging for the Gliffy JIRA Plugin you must edit the log4j.properties.

http://confluence.atlassian.com/display/JIRA/Logging+and+Profiling

Add the following entry at the bottom of the file:

log4j.logger.com.gliffy = INFO, console, filelog 
log4j.additivity.com.gliffy = false

Then on a restart, they can go to the logging console: 
/secure/admin/ViewLogging.jspa

And change com.gliffy to DEBUG.

Reproduce the issue, then set it back to INFO, to avoid having Gliffy fill your logs with ephemera.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.