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

# Integration Monitoring

The **Integration monitoring** page displays the verification status of diamonds that you have uploaded to Tracr using the Integration Tool or Tracr Loader.

The data is presented in a table with details about each diamond and its status in the integration process. Tracr displays the status of an integration as either “Registered” or “Invalid”:

{% hint style="info" %}

* **Registered** – The diamond is verified and on the Tracr Portal.
* **Invalid** – An error has occurred, and Tracr did not register the diamond. Refer to the **Details** column for more information on the error.
  {% endhint %}

## Export an event report

You can export details of all the events currently displaying on the **Integration monitoring** page as a report (xlsx file).

{% stepper %}
{% step %}

### Prepare the events to export

Use the filters on the Integration monitoring page to display only the events you want to include in the export.
{% endstep %}

{% step %}

### Export the report

Select **Export report**, then choose **xlsx file** to download the report.
{% endstep %}
{% endstepper %}


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tracr.com/tracr-help-pages/integration/integration-monitoring.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.