> 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-user-guide/6.-integration-monitoring.md).
# 6. Integration Monitoring
Read this section to learn how to view the verification status of uploaded diamonds.
## Overview
The **Integration monitoring** page displays the verification status of diamonds that you have uploaded to Tracr. Each integration has a status, which can be ‘Registered’ or ‘Invalid’.
* **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.
## View the verification status of a session
You can view the verification status of diamonds in all submitted sessions or for a specific session.
The Integration Monitoring page showing one registered diamond and one unregistered diamond (invalid).
To view the verification status of all submitted sessions:
* From the Tracr menu, select **Integration > Monitoring**.\
The **Integration monitoring** page displays the integration events for each diamond in all submitted sessions.
{% stepper %}
{% step %}
### View the integration status of a specific session
* From the Tracr menu, select **Integration > Integration Tool**.
* On the **Session history** page, next to a session, select **Action > Monitoring**.\
The **Integration monitoring** page displays the integration events for each diamond in the selected session.
{% endstep %}
{% endstepper %}
### Integration event information
The information on the **Integration monitoring** page provides details about each diamond and its status in the integration process.
* **Integration type** – The integration type selected when the CSV file was uploaded to Tracr.
* **Event date** – The date and time Tracr successfully or unsuccessfully registered the diamond. You can filter on the event date if you only want to display events on a particular date.
* **Participant ID** – The participant’s unique ID for the diamond.
* **Session ID** – The ID allocated to the session by Tracr.
* **Box ID** – The sight box identification by Tracr.
* **Tracr ID** – The ID allocated when Tracr registered the diamond. You can search your inventory using this ID.
* **Status** – The status of the integration event. Tracr displays the status of an integration as either ‘Registered’ or ‘Invalid’.
* **Details** – Provides more information if the status of the event is ‘Invalid’.
{% hint style="info" %}
Searches by ID are case-sensitive. As soon as you type the first three characters in the Filter by ID box, Tracr will list matching diamonds.
{% endhint %}
### Filter integration events
To find events for a specific diamond or a group of diamonds, you can filter by participant ID, box ID, session ID, or Tracr ID.
{% stepper %}
{% step %}
### Filter by ID
* Type the ID that you want to search for into the **Filter by ID** box. As soon as you type the first three characters, Tracr will list the diamonds that match. (Search is case-sensitive.)
* Select **X** to clear the search box to redisplay all events.
{% endstep %}
{% step %}
### Sort results
* To sort the results in ascending/descending order, select any column heading.
{% endstep %}
{% endstepper %}
### Filter by integration type, last updated, or status
You can filter integration events by integration type, last updated, or status.
* To only display events last updated on a particular date, select **Event date**, choose the date from the calendar, and select **Apply**.
* To only display events of a certain integration type or status, select the filter, select the filter value(s) that you want to use, and select **Apply**.
### Clear all filters
To clear all filters and redisplay all events, select **Clear**.
### 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 report
Use the filters to display the events that you want to export.
{% endstep %}
{% step %}
### Export
Select **Export report** and then select **xlsx file**.
{% endstep %}
{% step %}
### Download
Tracr generates the report which is downloaded and saved in your default downloads folder.\
[**View example report**](broken://pages/c648ce1e22de29247b407f1387b749fb5c45b8a6#integration-monitoring-report)
{% endstep %}
{% endstepper %}
## Integration errors
Typical integration errors include:
* **Child diamond cannot be heavier than its parent** – The parent diamond carat weight is less than the subject diamond.
* **No boxes found** – The box ID in the CSV used to upload a rough diamond has not been found for the sight year and number provided.
* **Too many carats** – The total carat weight does not match the expected carat weight as registered against the box by De Beers.
* **Too many diamonds** – You are trying to register more diamonds than De Beers assigned to the box.
* **Diamond is not unique** – The same diamond ID already exists on Tracr.
* **Could not find existing diamond or parent (parent id xxxxxx) for yyyyyy** – You cannot register a split or polish or perform an update because the existing or parent diamond is not registered on Tracr.
{% hint style="info" %}
For help on these and other error messages shown in the **Details** column, contact
{% endhint %}
---
# 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-user-guide/6.-integration-monitoring.md?ask=&goal=
```
`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.