> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/administration/audit-trails/connectors.md).
# Connectors
The "Connectors" tab tracks changes to connections used by OvalEdge. It captures information whenever a user:
* Establishes a new connection (Add)
* Modifies an existing connection (Update)
* Deletes a connection (Delete)
The audit log records the following details:
* **Connector Details:**
* Name
* Type (e.g., RDBMS, File, Reports)
* **Action:** Add, Update, or Delete
* **Updated By:** The user who made the change
* **Created By:** The user who created the connector (for adds)
* **Audit Date:** Timestamp of the action
**Sorting and Filtering:** Audit details can be sorted/filtered by Connector Name, Connector Type, Action, Date, and Created By.
**Example:** If an S3 connection is established, the following information is audited:
| Connection Name | Connection Type | Action | Updated By | Audit Date | Created Date |
| --------------- | --------------- | ------ | ---------- | ---------------------- | ------------ |
| Connection Name | Connection Type | Action | Updated By | Audit Date | Created Date |
| S3 | File | ADD | Admin | 2023-12-20 06:41:24 PM | Admin |
\
Sample screenshot featuring Audit Trails > Connectors information.
---
# 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.ovaledge.com/release8.3/administration/audit-trails/connectors.md?ask=&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.
