> For the complete documentation index, see [llms.txt](https://docs.monspark.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monspark.com/website-monitoring/working-with-monitors/reporting.md).

# Reporting

## PDF Export

PDF reports are incredibly useful for sharing with your internal teams or clients. You have the option to create a PDF report for a single monitor or for multiple monitors.

### Exporting PDF report of a single monitor

{% @arcade/embed flowId="HKE7CsRlWLam6xJhEfqU" url="<https://app.arcade.software/share/HKE7CsRlWLam6xJhEfqU>" %}

***

#### Export PDF

You can configure and export your PDF report of a single monitor.&#x20;

#### Report Type

You can change the report type before exporting it. Choose "Uptime Report" for an inclusive, detailed report. "Summary Report" provides a brief summary of the monitor.

#### Start Date

You can adjust the start date for the uptime report.

#### Report Title&#x20;

You can rename the report, which will change the title and the file name.

#### Report Language

We support 2 languages while exporting reports. You can choose your desired language in this section.

#### Date Format

You can change your date format according to your preference as DD/MM/YYY, MM/DD/YYY, or YYY/MM/DD.

***

### Additional Settings

#### Event Logs

According to your preference, you can include or exclude event logs of the monitor.

#### Monitor Details

You can include or exclude the monitor name, URL, etc.

#### Charts

You can include or exclude monitor charts to the report.

#### URLs

You can include or exclude URLs of the monitor.

#### Favicons

You can include or exclude the favicon of the monitor.

***

## Excel Export

Excel reports are extremely useful for conducting further operations on your monitor's stats, such as creating an internal report based on the monitor's response times. You have the option to create an Excel report for a single monitor or for multiple monitors.

### Exporting Excel report of a single monitor

{% @arcade/embed flowId="PXC3yjFp8PJKbeRCLYzT" url="<https://app.arcade.software/share/PXC3yjFp8PJKbeRCLYzT>" %}

***

#### Export Excel Report

You can configure and export your Excel report of a single monitor.&#x20;

#### Start Date

You can adjust the start date for the report.

#### Report Title&#x20;

You can rename the report, which will change the title and the file name.

#### Report Language

We support 2 languages while exporting reports. You can choose your desired language in this section.

#### Date Format

You can change your date format according to your preference as DD/MM/YYY, MM/DD/YYY, or YYY/MM/DD.

#### Request Settings

You can include or exclude request settings on your Excel report.

#### Notification Settings

You can include or exclude notification settings on your Excel report.


---

# 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 by asking a question.

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

```
GET https://docs.monspark.com/website-monitoring/working-with-monitors/reporting.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 `automate deployments from our CI pipeline` 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.