> 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/file-manager/data-lake-ovalsight/customization-via-system-settings.md).

# Customization via System Settings

| Key                                     | Description                                                                                                                                                                                                                                                                                                 |
| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **no.of.samplefiles.bucketanalysis**    | <p>Set the maximum number of sample file names shown during Bucket Analysis.</p><p></p><p><strong>Parameters:</strong></p><ul><li>Enter a numeric value in the field.</li></ul>                                                                                                                             |
| **enable.folder.ovalsight**             | <p>Enable or disable the Folder OvalSight tab in the Folder Summary page of Data Catalog.</p><p></p><p><strong>Parameters:</strong></p><ul><li>The default value is False</li><li>If set to True, the Folder Analysis tab is visible.</li><li>If set to False, the Folder Analysis tab is hidden.</li></ul> |
| **supported.folderanalysis.connectors** | <p>List the connectors (e.g., CIFS, ADL, NFS, S3, Google Drive) that support folder analysis to determine folder size and count.<br></p><p><strong>Parameters:</strong></p><ul><li>Enter connector names in the field.</li></ul>                                                                            |
| **folder.analysis.api.limit**           | <p>Set the API call limit for Folder Analysis. The system stops making calls after reaching this threshold.<br></p><p><strong>Parameters:</strong></p><p>The default value is 5000</p><p>Enter a numeric threshold value.</p>                                                                               |
| **folder.analysis.user.custom.path**    | <p>Specify the file path to save Folder Analysis output files.</p><p></p><p><strong>Parameters:</strong></p><p>The default value is Empty</p><p>If left empty, the system prompts to provide a valid path.</p>                                                                                              |

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA


---

# 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/file-manager/data-lake-ovalsight/customization-via-system-settings.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.