Skip to end of banner
Go to start of banner

How to Set Temporary Application Logging Level

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Description

When doing problem determination, you may want or be instructed by support to add or set more application logging. Many Atlassian products provide a admin UI to do this. This can be automated by the CLI using the renderRequest action - see How to use renderRequest. This provide a list of known examples. The setting is effective until the next time the server is rebooted. This changes the level of information available in the application log file.

Available levels that are common:

  1. INFO
  2. WARN
  3. ERROR
  4. DEBUG
  5. FATAL

Jira Example

-a renderRequest --request "/secure/admin/ConfigureLogging.jspa" --request "loggerName=org.swift&levelName=DEBUG" --file ""

Confluence Example

-a renderRequest --request /admin/addlog4jentry.action --requestParameters "extraClassName=com.appfire&extraLevelName=DEBUG" --file ""

Bamboo Example

-a renderRequest --request "/admin/addLog4jEntry.action" --request "save=Add&extraClassName=com.appfire&extraLevelName=DEBUG" --file ""
  • No labels