Problem Determination Information - 4.x
Description
If requested by our support representative, please follow these steps to turn on debug logging that helps us determine the problem.
Steps to collect debug information
- Read: Confluence logging - how to configure additional temporary logging in Confluence
- Add an entry for DEBUG using org.swift.confluence.macrosecurity
- Temporary logging gets you started without a server restart. It does not carry over after restart.
- Should look like:
- Run a test scenario and then look in the server log. Find the time period close to your test run time and look for entries including text: org.swift.confluence.macrosecurity
- If none found, search for macrosecurity (as logging output can vary)
- Attach one of the following:
- Cut and paste the entries into a comment (if small) or into a file and attach (recommended)
- Ensure the Zip of your server log doesn't contain sensitive information
- Copy your server log and remove earlier entries or other information you may not want to share
Log a request with our support team.
Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.