> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/reports/configure-the-time-zone-and-format-in-a-report.md).

# Configure the Time Zone and Format in a Report

Configure Cortex XSOAR 6.15 report time zones and date formats, and resolve related display issues.

You can set the time and date format, and a time zone for report widgets by adding a server configuration. When this is not specified, the time/date format and time zone are the local time and location when the report is generated.

{% hint style="info" %}

### Note

Most out-of-the-box reports, time zone and time formats in a widget cannot be changed unless you copy the report. Some reports, such as Open Incidents, include a title widget, which include the date the report is generated. The report is generated according to the system default. You can change the system default by going to the **Time Configuration** section (Settings → ABOUT → **Troubleshooting**).
{% endhint %}

1. Go to Settings → About → **Troubleshooting**.
2. In the **Server Configuration** section, click **Add Server Configuration**.
3. Add the following keys and values:

   | Key                       | Value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
   | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | **`reports.time.format`** | <p>The time/date for your report widgets. For example:</p><ul><li>02 Jan 06 15:05 GMT</li><li>Thursday, 02-Jan-06 15:05 MST</li><li>2006-01-02T15:05:10Z07:00</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>Layouts must use the reference time Mon Jan 2 15:04:05 MST 2006 to show the pattern with which to format/parse a given time/string. For more examples, see <a href="https://www.geeksforgeeks.org/time-formatting-in-golang/">Time Formatting in Go Language</a>.</p></div> |
   | **`reports.time.zone`**   | <p>The time zone for your report widgets. For example:</p><ul><li>Australia/Melbourne</li><li>Canada/Pacific</li><li>America/Los\_Angeles</li><li>America/New\_York</li><li>Asia/Jerusalem</li><li>Asia/Kolkata</li><li>CET</li><li>EST</li><li>GMT</li><li>Europe/Berlin</li><li>Europe/Brussels</li><li>UTC (Default)</li></ul>                                                                                                                                                                                                                                    |
4. Click **Save**.
5. Restart the Cortex XSOAR server by running the following command:

   **`systemctl restart demisto`**

For example, the following table shows the default configuration (Tue, 28 December 2021 06:25:36 UTC).

![reports-time-utc.png](https://content.gitbook.com/content/8xEMUKpU65o1wagTHaO3/blobs/6yBkZkxasEPZN7TQIJ6u/0bd85a77667cceff1ca2946f184ee2b6a9eb3079f63d559af3938b2cb3ae4bab.png)

We add the following **`reports.time.format`** server configuration:

2006-01-02T15:05:10Z07:00

The table now shows the following data:

![reports-time-tz.png](https://content.gitbook.com/content/8xEMUKpU65o1wagTHaO3/blobs/rVZrly2eJoLNqF50VuvB/d5bbe05cc250224da3d3984177a0308a613ba43c7599243ea99b412ed6e43619.png)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/reports/configure-the-time-zone-and-format-in-a-report.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.