---
title: "BigPicture logs - divert to a separate file."
canonical: "https://support.appfire.com/space/DLP/297667513/BigPicture%20logs%20-%20divert%20to%20a%20separate%20file."
format: markdown
---
| **Contents:**<br>> Macro (toc) |
| --- |

## Instructions for Jira Data Center and Server 9.5 or newer

> ⚠️ The following instructions apply to **Jira Data Center and Server 9.5 or newer**.

Below you’ll find instructions on setting up a separate log file for BigPicture debug data.

If you are encountering a significant amount of BigPicture debug data being sent to the `atlassian-jira.log` file and would prefer to direct it to a dedicated log file, you can achieve this by modifying the configuration of Jira's `log4j2` file manually.

### Steps

1. Open the `log4j2.xml`* file in the text editor of your choice.
2. Add the following snippet before the `</Appenders>` tag:
3. Add the following snippet before the `</Loggers>` tag:

This will create a separate `bigpicture.log` file for all logs from our App or from the `com.softwareplant` package specifically.

If necessary, you may adjust the pattern according to your needs, such as by adding additional data or presenting it differently.

### Where to find the log4j2.xml file?

Refer to the Atlassian’s guide on where to find the file:

- [Jira application installation directory](https://confluence.atlassian.com/adminjiraserver/jira-application-installation-directory-938847745.html)
- [Change logging levels in Jira Server](https://confluence.atlassian.com/jirakb/change-logging-levels-in-jira-server-629178605.html)

> ℹ️ If you want to set the logging level for a package permanently, you can do so by configuring the `log4j2.xml` file, located in the `$JIRA_INSTALL/atlassian-jira/WEB-INF/classes/` directory.

## Instructions for Jira Data Center and Server 9.4 or earlier 

> ⚠️ The following instructions apply to **Jira Data Center and Server 9.4 or earlier**.

Below you’ll find instructions on setting up a separate log file for BigPicture debug data.

<span style="color: #000000">If you get a sizable amount of BigPicture debugs data sent to </span>`atlassian-jira.log`<span style="color: #000000"> but would instead divert it to a dedicated log file, you can do it by manually changing the configuration of Jira’s </span>`log4j`<span style="color: #000000">file. </span>

### <span style="color: #000000">Steps</span>  


1. Add the following snippet to your log4j.properties* file:
2. <span style="color: #000000">Restart your Jira instance.</span>

<span style="color: #000000">This will create a separate bigpicture.log file for all logs from our app or from the com.softwareplant package specifically). </span>

### <span style="color: #000000">Where to find the log4.properties file?</span>

<span style="color: #000000">The </span>`log4.properties`<span style="color: #000000"> file is located in </span>`WEB-INF/classes/log4j.properties`.

<span style="color: #000000">To find this path:</span>

1. <span style="color: #000000">Go to </span><span style="color: #000000">**Jira Administration **</span><span style="color: #000000">></span><span style="color: #000000">** System **</span>><span style="color: #000000">** **</span>**Logging & Profiling**<span style="color: #000000">. </span>
2. <span style="color: #000000">Scroll down to the </span><span style="color: #000000">**Default Loggers **</span><span style="color: #000000">section.</span>
3. <span style="color: #000000">You can further configure the granularity of the log file by clicking on the </span><span style="color: #000000">**Configure logging level for another file**</span><span style="color: #000000"> option and choosing the desired logging levels.</span>