ロギングとプロファイリング

On this page:

ログ

JIRA uses a powerful logging module called log4j for runtime logging.

There are five logging levels available in log4j: 'DEBUG', 'INFO', 'WARN', 'ERROR' and 'FATAL'. Each logging level provides more logging information that the level before it:
'DEBUG' < 'INFO' < 'WARN' < 'ERROR' < 'FATAL'
'DEBUG' provides the most verbose logging and 'FATAL' provides the least verbose logging.

The default logging levels can be changed either;

• temporarily — your change to the logging level will not persist after you next restart JIRA, or
• permanently — your change to the logging level will persist, even after you restart JIRA.

例えばトラブルシューティングの際、ログ レベルを "WARNING" から "INFO" に一時的に変更して、より詳細なエラー メッセージやスタック トレースを取得することができます。必要なログ カテゴリが不明な場合、一般に log4j.rootLogger カテゴリや log4j<category>.com.atlassian カテゴリで有用な情報を取得できます。

To temporarily change the logging level:

1. Log in as a user with the 'JIRA System Administrators' global permission.
2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
3. Under the 'System' sub-menu in the left-hand navigation column, click the 'Logging & Profiling' link.
4. The 'Logging & Profiling' page will display. This lists all the defined log4j categories and their current logging levels. To edit the logging level of a category, click the 'Edit' link next to the category in the list.
5. Choose the new logging level for the category, then click 'Update'.

To permanently change the logging level:

1. Edit the log4j.properties file, which is found in the WEB-INF/classes/ directory under the JIRA web application directory.

   The log4j.properties file that ships with JIRA has the default logging levels specified. For more information about log4j (e.g. how to define new logging categories), and about the format of the log4j.properties file, please refer to the documentation on the log4j site.

2. Jira を再起動します。

プロファイリング

If you are experiencing performance issues with JIRA, it is often helpful to see where the slow-downs occur. To do this you can enable profiling as described below, and then analyse the performance traces that JIRA will produce for every request. An example of a profiling trace is shown below:

[Filter: profiling] Turning filter on [jira_profile=on]
[116ms] - /secure/Dashboard.jspa
  [5ms] - IssueManager.execute()
    [5ms] - IssueManager.execute()
      [5ms] - Searching Issues
  [29ms] - IssueManager.execute()
    [29ms] - IssueManager.execute()
      [29ms] - Searching Issues
        [28ms] - Lucene Query
          [23ms] - Lucene Search

Profiling can be enabled either;

• temporarily — profiling will be enabled until you next restart JIRA, or
• permanently — profiling will remain enabled, even after you restart JIRA.

To temporarily enable profiling:

1. Log in as a user with the 'JIRA System Administrators' global permission.
2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
3. Under the 'System' sub-menu in the left-hand navigation column, click the 'Logging & Profiling' link.
4. The 'Logging & Profiling' page will display. Scroll to the bottom of the screen. The 'Profiling' section will inform you whether profiling is currently turned 'ON' or 'OFF', and will also show or hide the 'Disable profiling' and 'Enable profiling' links respectively.
   • To turn Profiling 'ON', click the 'Enable profiling' link. JIRA will start generating profiling traces in its log.
   • To turn Profiling 'OFF', click the 'Disable profiling' link.

To permanently enable profiling:

1. Edit atlassian-jira/WEB-INF/web.xml (if you are using JIRA Standalone) or webapp/WEB-INF/web.xml in your JIRA installation directory (if you are using JIRA EAR/WAR).
2. 以下のエントリを探します。

           <filter>
               <filter-name>profiling</filter-name>
               <filter-class>com.atlassian.jira.web.filters.JIRAProfilingFilter</filter-class>
               <init-param>
                   <!-- specify the which HTTP parameter to use to turn the filter on or off -->
                   <!-- if not specified - defaults to "profile.filter" -->
                   <param-name>activate.param</param-name>
                   <param-value>jira_profile</param-value>
               </init-param>
               <init-param>
                   <!-- specify the whether to start the filter automatically -->
                   <!-- if not specified - defaults to "true" -->
                   <param-name>autostart</param-name>
                   <param-value>false</param-value>
               </init-param>
           </filter>
       

3. Modify the autostart parameter to be true instead of false. That is:

               <init-param>
                   <!-- フィルターを自動的に開始するかどうか指定 -->
                   <!-- 指定しない場合、デフォルトで "true" となります。 -->
                   <param-name>autostart</param-name>
                   <param-value>true</param-value>
               </init-param>
       

4. Save the file. If you are running JIRA Standalone this is all you have to do. Profiling will be enabled when you restart JIRA.
5. If you are running JIRA EAR/WAR, re-build and re-deploy the JIRA web application using the build script and the instructions for your application server.