> For the complete documentation index, see [llms.txt](https://docs.datasentinel.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasentinel.io/manual/features/other-features.md). # Other Features - [Agentless Monitoring](https://docs.datasentinel.io/manual/features/other-features/agentless-monitoring.md): Datasentinel offers an agentless approach for remote monitoring of PostgreSQL clusters, eliminating the need for local agent installations. - [Role Based Access](https://docs.datasentinel.io/manual/features/other-features/role-based-access.md): Datasentinel offers Role-Based Access Control, enabling precise restriction of designated users to specific perimeters among the total instances available. - [Execution Plans](https://docs.datasentinel.io/manual/features/other-features/execution-plans.md): Execution plans provide detailed insight into how PostgreSQL executes SQL queries. They describe the steps chosen by the query planner, the access methods used, join strategies, ... - [Changed Parameters](https://docs.datasentinel.io/manual/features/other-features/changed-parameters.md): Datasentinel automatically checks for changes in parameters every hour. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.datasentinel.io/manual/features/other-features.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 `build a script that syncs our docs to a CMS` 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.