# Connector Log

### Overview

The **Connector Log** records all outgoing and incoming API calls between your domain and other integrated applications. This includes calls related to Single Sign-On (SSO) and applications like NetSuite. 

<figure><img src="/files/wnqXQvBBKYPq1Z3NzG6R" alt="" width="563"><figcaption></figcaption></figure>

The Connector Log is a vital tool for troubleshooting SSO issues and other call-related errors between your domain and connected services.

{% hint style="info" %}
MangoApps retains Connector logs from the date of domain creation. The system never deletes audit logs. These logs are accessible anytime to the network admin.
{% endhint %}

***

### Key Features of the Connector Log

**Application To/From:** This filter allows you to select the application involved in the connection. Available options include: MangoApps, OAuth 2.0 Google Apps, OAuth 2.0 Office 365.

**Action:** You can filter the logs based on specific actions such as:

| All            | SLO Initiated (Single Logout) |
| -------------- | ----------------------------- |
| SSO Initiated  | SLO Failed                    |
| SSO Failed     | SLO Successful                |
| SSO Successful | NA (Not Applicable)           |

**Date Range:** Select the date range for which you want to view logs. This allows you to narrow down the log entries to a specific period.

**Request Type:** Filter based on the type of request made, including:

| All                         | Logout-Applications |
| --------------------------- | ------------------- |
| Authentication-Applications | Logout-Connections  |
| Authentication-Connections  |                     |

**Email ID/Login ID:** To search for logs related to a specific user, enter the user’s email address or login ID.

***

### Using the Connector Log

**Search for Logs:** The Connector Log allows admins to efficiently search and filter connector events. To refine a search, users can:

* Choose the **Application To/From** to investigate.
* Select the appropriate **Action** type, such as "SSO Failed" or "SLO Successful."
* Set a **Date Range** to limit the logs to a particular time period.
* Choose the **Request Type** (Authentication, Logout, etc.).
* Enter an **Email ID/Login ID** to focus on a specific user.

**Clear Filters:** To reset the filters and start over, click the **Clear** button.

**View Payload Information:** Click on **Request** and **Response** under the **Payload** column in the results table to view detailed information about the data exchanged in the connection.

***

### Export the Connector Log

To export the filtered results from the Connector Log, first set the desired filters and generating the log results, then click **Export CSV** or **Export PDF** to download the report in the chosen format.

{% hint style="info" %}
A maximum of 1000 records can be exported for a selected period to a .csv file.
{% endhint %}

***

### Troubleshooting with the Connector Log

The Connector Log is particularly useful for troubleshooting issues related to Single Sign-On (SSO) and integrations with external applications. For example, the log can be used to:

* Investigate failed SSO attempts and identify the root cause.
* Verify successful logouts across different applications.
* Analyze the payload data for each connection request and response to troubleshoot further if necessary.

***

The Connector Log provides transparency into the flow of communication between MangoApps and other systems, making it a valuable tool for system administrators.


---

# Agent Instructions: 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:

```
GET https://guides.mangoapps.com/admin-guide/home-1/logs/connector-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.