# Datasentinel Docs

## Documentation

- [Welcome](https://docs.datasentinel.io/manual/welcome.md): Welcome to Datasentinel's new help center, your ultimate solution for effectively monitoring and analyzing the performance of your PostgreSQL clusters.
- [Free Trial](https://docs.datasentinel.io/manual/free-trial.md)
- [Architecture](https://docs.datasentinel.io/manual/getting-started/architecture.md): Datasentinel offers the flexibility to be used either On-Premises or in SaaS mode, with or without agents, enabling you to choose an architecture that best fits your needs.
- [Installation](https://docs.datasentinel.io/manual/getting-started/installation.md): For on-premises use of Datasentinel, platform installation is required. We advise utilizing a dedicated machine for optimal performance.
- [Platform](https://docs.datasentinel.io/manual/getting-started/installation/platform.md): Installation completes within minutes, ensuring that all components are operational upon completion.
- [Agent](https://docs.datasentinel.io/manual/getting-started/installation/agent.md): Datasentinel offers two monitoring approaches: agent-based and agentless. This guide focuses on the installation of an agent, applicable when you opt for the agent-based monitoring method.
- [PostgreSQL clusters](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters.md): Datasentinel has the capability to monitor hundreds of PostgreSQL clusters, and a single connection to a cluster is sufficient for overseeing all the existing databases within it.
- [Extensions](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/extensions.md): Datasentinel harnesses the power of multiple PostgreSQL extensions to deliver in-depth monitoring metrics on specific areas.
- [pg\_stat\_statements](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/extensions/pg_stat_statements.md): The pg\_stat\_statements extension allows to trace the execution statistics of all queries. It is an essential extension in understanding the activity of a PostgreSQL cluster.
- [pg\_store\_plans](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/extensions/pg_store_plans.md): The PostgreSQL extension pg\_store\_plans is a contrib module that provides a way to store execution plans generated by the query planner.
- [system\_stats](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/extensions/system_stats.md): system\_stats is a PostgreSQL extension that provides functions to access system level statistics that can be used for monitoring
- [pg\_buffercache](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/extensions/pg_buffercache.md): pg\_buffercache is a PostgreSQL contrib module offering a real-time method for inspecting activities within the shared buffer cache.
- [Monitoring User](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/monitoring-user.md)
- [Adding Connection](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/adding-connection.md)
- [Internal Function](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/internal-function.md): An optional read-only function that gives Datasentinel access to planner statistics and execution plans without granting SELECT on application tables.
- [FAQs](https://docs.datasentinel.io/manual/getting-started/faqs.md)
- [Platform FAQ](https://docs.datasentinel.io/manual/getting-started/faqs/platform-faq.md)
- [Agent FAQ](https://docs.datasentinel.io/manual/getting-started/faqs/agent-faq.md)
- [Key Features](https://docs.datasentinel.io/manual/features/key-features.md)
- [Session History](https://docs.datasentinel.io/manual/features/key-features/session-history.md): Datasentinel periodically samples active sessions, enabling in-depth analysis of your workload.
- [Top Queries](https://docs.datasentinel.io/manual/features/key-features/top-queries.md): The Top Queries feature allows you to identify the most consuming queries according to a chosen dimension.
- [Top Tables](https://docs.datasentinel.io/manual/features/key-features/top-tables.md): Datasentinel facilitates hourly collection of relations, supporting a Dimension-Based Analysis approach
- [Lock Explorer](https://docs.datasentinel.io/manual/features/key-features/lock-explorer.md): Lock explorer makes it easy to identify blocking sessions during blocked session issues, along with the associated queries and locks.
- [Cluster & System Metrics](https://docs.datasentinel.io/manual/features/key-features/cluster-and-system-metrics.md): Datasentinel gathers real-time PostgreSQL cluster metrics on a minute-by-minute basis, alongside database-specific measures encompassing transactions, cache hits, IO operations, among others.
- [Live360](https://docs.datasentinel.io/manual/features/key-features/live360.md): Datasentinel offers a direct connection feature to PostgreSQL instances, enabling real-time retrieval of information.
- [Reporting](https://docs.datasentinel.io/manual/features/key-features/reporting.md): Turn any time window of your PostgreSQL activity into a PDF report: download it, email it once, or schedule it, from the web interface, the API, or an AI assistant.
- [Alerting](https://docs.datasentinel.io/manual/features/key-features/alerting.md): The alerting functionality empowers you to effectively oversee your PostgreSQL instances, enabling prompt notifications in the event of any issues.
- [Settings](https://docs.datasentinel.io/manual/features/key-features/alerting/settings.md)
- [Templates](https://docs.datasentinel.io/manual/features/key-features/alerting/templates.md): Defining notification templates is the next step after enabling Alerting at the platform level.
- [Silences](https://docs.datasentinel.io/manual/features/key-features/alerting/silences.md): Activating a silence period deactivates the alerting mechanism for one or multiple instances. This proves particularly beneficial during maintenance tasks.
- [Manager](https://docs.datasentinel.io/manual/features/key-features/alerting/manager.md): Various methods exist for both viewing and managing notifications.
- [Other Features](https://docs.datasentinel.io/manual/features/other-features.md)
- [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.
- [Tips & Hints](https://docs.datasentinel.io/manual/features/tips-and-hints.md)
- [User Interface](https://docs.datasentinel.io/manual/features/tips-and-hints/user-interface.md): Built as a specialized plugin for the Grafana framework, Datasentinel offers an intuitive interface that allows users to become adept within minutes
- [Tags](https://docs.datasentinel.io/manual/features/tips-and-hints/tags.md): A tag is comprised of both a key and a corresponding value, working together to represent a distinct property.
- [Metric Correlation](https://docs.datasentinel.io/manual/features/tips-and-hints/metric-correlation.md): This ability to correlate metrics greatly enhances analytical capabilities by effortlessly revealing potential relationships and patterns between separate measurements.
- [Consolidated View](https://docs.datasentinel.io/manual/features/tips-and-hints/consolidated-view.md): One of the standout features of Datasentinel is its ability to provide a consolidated view of multiple instances concurrently.
- [Graphical Annotations](https://docs.datasentinel.io/manual/features/tips-and-hints/graphical-annotations.md): The main dashboards employ graphical annotations to spotlight significant events, delivering an instant visual summary.
- [Predefined Providers](https://docs.datasentinel.io/manual/features/tips-and-hints/predefined-providers.md): DataSentinel allows users to associate their monitored PostgreSQL instances with specific providers.
- [Wait Event Description](https://docs.datasentinel.io/manual/features/tips-and-hints/wait-event-description.md): A wait event in PostgreSQL is a fundamental concept used in performance monitoring and tuning.
- [Read Replicas](https://docs.datasentinel.io/manual/features/tips-and-hints/read-replicas.md): Datasentinel offers efficient monitoring of PostgreSQL Read Replicas through read-only access. It supports both local agent-based and agentless setups, ensuring flexible and seamless integration.
- [Agentless & System Metrics](https://docs.datasentinel.io/manual/features/tips-and-hints/agentless-and-system-metrics.md): One of the features of Datasentinel is its ability to offer comprehensive monitoring of PostgreSQL clusters without the need for installing agents on your database servers.
- [Query Identifier](https://docs.datasentinel.io/manual/features/tips-and-hints/query-identifier.md): From the beginning, Datasentinel has relied on an MD5 hash of the query text to compute query identifiers.
- [Simplified pg\_instance Display](https://docs.datasentinel.io/manual/features/tips-and-hints/simplified-pg_instance-display.md): Created by Datasentinel, the pg\_instance tag is a unique identifier for your instance across the platform.
- [Platform Usage](https://docs.datasentinel.io/manual/implementation/platform-usage.md)
- [Configuration](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration.md)
- [License](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/license.md): The license is provided in the form of a token with a restricted time of validity.
- [LDAP](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/ldap.md): Datasentinel seamlessly integrates with LDAP for user authentication.
- [SMTP](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/smtp.md): SMTP (Simple Mail Transfer Protocol) is required for sending email notifications and workload reports. It ensures reliable delivery of messages, enabling real-time alerts and efficient report sharing
- [Audit](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/audit.md): Datasentinel can audit the actions performed by your declared users on the platform.
- [Default RBAC Behavior](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/default-rbac-behavior.md)
- [Users & Roles](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/users-and-roles.md): Datasentinel employs a multi-layered approach to secure user access to its platform and control who can access monitored PostgreSQL instances.
- [Backend](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/backend.md)
- [API Reference](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference.md)
- [Access Token](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/access-token.md): To enable interaction with the Platform API, it is necessary to generate an access token.This access token is subsequently used when making calls to the API.
- [Connection](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/connection.md): The Connection API is available solely through an on-premises installation and is reliant on the decision to use the Agentless feature.
- [Role](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/role.md)
- [User](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/user.md)
- [Reporting](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/reporting.md)
- [Workload](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/workload.md): The Workload API provides you with the option to download comprehensive metrics in either JSON or CSV format.
- [Alerting](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/alerting.md)
- [Tooling](https://docs.datasentinel.io/manual/implementation/platform-usage/tooling.md): Datasentinel provides tooling to help you troubleshoot problems or gather information about system configurations.
- [Log Files](https://docs.datasentinel.io/manual/implementation/platform-usage/log-files.md): Datasentinel generates logs, which are located in the /datasentinel/log directory, except for the NGINX log file.
- [Agent Usage](https://docs.datasentinel.io/manual/implementation/agent-usage.md)
- [Release Notes](https://docs.datasentinel.io/manual/implementation/agent-usage/release-notes.md): All releases are cumulative. Upgrading to the latest version includes all previous changes, so it's sufficient to install or run only the most recent release.
- [CLI](https://docs.datasentinel.io/manual/implementation/agent-usage/cli.md): The agent offers a CLI for conveniently modifying attributes and connections.
- [API Reference](https://docs.datasentinel.io/manual/implementation/agent-usage/api-reference.md): The agent's setup is adjustable using direct API invocations, facilitating interactive information retrieval and interaction.
- [Collection Level](https://docs.datasentinel.io/manual/implementation/agent-usage/collection-level.md): The Agent version 3.2, which was released in February 2023, introduces the Collection Level feature allowing you to choose the metrics to monitor.
- [Internals](https://docs.datasentinel.io/manual/implementation/agent-usage/internals.md)
- [Upgrade](https://docs.datasentinel.io/manual/implementation/upgrade.md)
- [Platform](https://docs.datasentinel.io/manual/implementation/upgrade/platform.md): Procedure to upgrade your on-premises platform.
- [Agent](https://docs.datasentinel.io/manual/implementation/upgrade/agent.md): Upgrading an agent involves completely replacing the old version with the new version.
- [Troubleshooting](https://docs.datasentinel.io/manual/implementation/troubleshooting.md)
- [Platform Diagnostics Tools](https://docs.datasentinel.io/manual/implementation/troubleshooting/platform-diagnostics-tools.md): Starting with version 2025.11, two new diagnostic scripts are available to help identify issues and assist the support team.
- [Unexpected Agent Termination](https://docs.datasentinel.io/manual/implementation/troubleshooting/unexpected-agent-termination.md): In some cases, the Agent may stop running without any visible error or warning.
- [Error message: “502 Bad Gateway”](https://docs.datasentinel.io/manual/implementation/troubleshooting/error-message-502-bad-gateway.md)
- [The UI is not displaying any metrics for my new instance.](https://docs.datasentinel.io/manual/implementation/troubleshooting/the-ui-is-not-displaying-any-metrics-for-my-new-instance..md)
- [UI dashboard is encountering loading errors](https://docs.datasentinel.io/manual/implementation/troubleshooting/ui-dashboard-is-encountering-loading-errors.md)
- [InfluxDB](https://docs.datasentinel.io/manual/implementation/troubleshooting/influxdb.md): InfluxDB is an open-source time series database used by Datasentinel to store collected metrics and manage data retention.
- [SELinux](https://docs.datasentinel.io/manual/implementation/troubleshooting/selinux.md): Security-Enhanced Linux (SELinux) is a Linux kernel security module that provides a mechanism for supporting access control security policies, including mandatory access controls (MAC).
- [NGINX](https://docs.datasentinel.io/manual/implementation/troubleshooting/nginx.md): NGINX sits at the edge of a Datasentinel deployment and acts as a reverse proxy. All inbound HTTPS traffic terminates at NGINX before being forwarded to the internal Datasentinel services.
- [How to Contact Us](https://docs.datasentinel.io/manual/support/how-to-contact-us.md): Need Assistance? Encountered a Bug?

## Changelog

- [2026](https://docs.datasentinel.io/manual/changelog/2026.md): All releases are cumulative. Upgrading to the latest version includes all previous changes.It's sufficient to install or run only the most recent release.
- [2025](https://docs.datasentinel.io/manual/changelog/2025.md): Datasentinel releases from 2025.
- [2024](https://docs.datasentinel.io/manual/changelog/2024.md): Datasentinel releases from 2024.
- [2023](https://docs.datasentinel.io/manual/changelog/2023.md): Datasentinel releases from 2023.
- [2022](https://docs.datasentinel.io/manual/changelog/2022.md): Datasentinel releases from 2022.
- [2021](https://docs.datasentinel.io/manual/changelog/2021.md): Datasentinel releases from 2021.
- [2020](https://docs.datasentinel.io/manual/changelog/2020.md): Datasentinel releases from 2020.
- [2019](https://docs.datasentinel.io/manual/changelog/2019.md): Datasentinel releases from 2019.

## AI Connector

- [AI Connector](https://docs.datasentinel.io/manual/ai-connector/readme.md)
- [Test with the sandbox platform](https://docs.datasentinel.io/manual/ai-connector/test-with-the-sandbox-platform.md): Try AI Connector against Datasentinel's public sandbox platform, with shared read-only credentials and no platform to install.
- [Install the Skill](https://docs.datasentinel.io/manual/ai-connector/install-the-skill.md): Download the Datasentinel Skill and install it in any assistant: extract it into a Skills folder, upload it, or pass it as a system prompt. Where each assistant reads it, how to check it, and how to u
- [MCP Server Setup](https://docs.datasentinel.io/manual/ai-connector/server-setup/mcp-server-setup.md): How the Datasentinel MCP server is started, configured and secured with OAuth 2.1 in production, plus manual setup steps for sites upgrading from an older release.
- [How authentication works](https://docs.datasentinel.io/manual/ai-connector/server-setup/how-authentication-works.md): What happens when an assistant connects to the Datasentinel MCP server: you sign in once in your browser and the assistant keeps the session alive; scripts use a user token instead.
- [Manage assistant sessions](https://docs.datasentinel.io/manual/ai-connector/server-setup/manage-assistant-sessions.md): How an administrator lists and ends the AI assistant sessions of the Datasentinel MCP server with the mcp\_oauth\_sessions.sh script: who is signed in, with which assistant, and how to disconnect a user
- [Configure Claude Code](https://docs.datasentinel.io/manual/ai-connector/connect-a-cli-assistant/configure-claude-code.md): Connect the Claude Code CLI to your Datasentinel MCP server, sign in, install the Datasentinel Skill, and verify the configuration.
- [Configure GitHub Copilot CLI](https://docs.datasentinel.io/manual/ai-connector/connect-a-cli-assistant/configure-copilot-cli.md): Connect the GitHub Copilot CLI to your Datasentinel MCP server on Linux, sign in, install the Datasentinel Skill, and verify the configuration.
- [Configure Mistral Vibe CLI](https://docs.datasentinel.io/manual/ai-connector/connect-a-cli-assistant/configure-mistral-vibe-cli.md): Connect the Mistral Vibe CLI to your Datasentinel MCP server on Linux, sign in, install the Datasentinel Skill, and verify the configuration.
- [Configure Google Antigravity CLI](https://docs.datasentinel.io/manual/ai-connector/connect-a-cli-assistant/configure-antigravity-cli.md): Connect the Google Antigravity CLI and desktop app to your Datasentinel MCP server, sign in, and install the Datasentinel Skill.
- [Configure OpenAI Codex CLI](https://docs.datasentinel.io/manual/ai-connector/connect-a-cli-assistant/configure-codex-cli.md): Connect the OpenAI Codex CLI to your Datasentinel MCP server on Linux, sign in, install the Datasentinel Skill, and verify the configuration.
- [Connect a compatible assistant](https://docs.datasentinel.io/manual/ai-connector/connect-a-cli-assistant/connect-a-compatible-assistant.md): The general pattern for connecting any MCP-and-Skill-capable assistant to Datasentinel, sign-in included, with Deep Agents Code and Hermes Agent as worked examples.
- [Configure the Claude desktop app for Windows](https://docs.datasentinel.io/manual/ai-connector/connect-a-desktop-app/configure-claude-desktop-windows.md): Connect the Claude desktop app on Windows to your Datasentinel MCP server, sign in, install the Datasentinel Skill, and verify the configuration.
- [Configure the ChatGPT desktop app](https://docs.datasentinel.io/manual/ai-connector/connect-a-desktop-app/configure-chatgpt-desktop-app.md): Connect the ChatGPT desktop app, with ChatGPT and Codex, to your Datasentinel MCP server, sign in, and install the Datasentinel Skill.
- [Configure the Microsoft Copilot app](https://docs.datasentinel.io/manual/ai-connector/connect-a-desktop-app/configure-microsoft-copilot-app.md): Use Datasentinel from the Microsoft Copilot app: Copilot Cowork, Copilot Studio agents, and the other paths.
- [Configure Microsoft Copilot Studio](https://docs.datasentinel.io/manual/ai-connector/connect-a-desktop-app/configure-copilot-studio.md): Connect a Microsoft Copilot Studio agent to your Datasentinel MCP server with OAuth sign-in, install the Datasentinel Skill, and reach a private platform from Microsoft's cloud.
- [Configure the Google Gemini desktop app](https://docs.datasentinel.io/manual/ai-connector/connect-a-desktop-app/configure-gemini-desktop-app.md): Use Datasentinel from the Google Gemini desktop app: add the MCP server as a custom app, sign in, and upload the Datasentinel Skill.
- [Configure Visual Studio Code](https://docs.datasentinel.io/manual/ai-connector/connect-an-ide/configure-vscode.md): Connect Visual Studio Code to your Datasentinel MCP server through GitHub Copilot agent mode, sign in, install the Datasentinel Skill, and verify the setup.
- [Configure Cursor](https://docs.datasentinel.io/manual/ai-connector/connect-an-ide/configure-cursor.md): Connect Cursor to your Datasentinel MCP server, sign in, install the Datasentinel Skill, and verify the setup.
- [Skill commands reference](https://docs.datasentinel.io/manual/ai-connector/use-the-assistant/skill-commands.md): Every command the Datasentinel Skill answers to, what each one does, what it needs, and the plain-language phrases that trigger the same analysis.
- [Check your session with whoami](https://docs.datasentinel.io/manual/ai-connector/use-the-assistant/whoami-command.md): The whoami command shows your session at a glance: who you are connected as, your rights, the token, the Skill copy in use, and the session settings.
- [Generate and share reports](https://docs.datasentinel.io/manual/ai-connector/use-the-assistant/generate-reports.md): Turn an analysis into a document you can share: a PDF built by the platform, or an HTML or Markdown report built by the assistant.
- [Explore the documentation from your assistant](https://docs.datasentinel.io/manual/ai-connector/use-the-assistant/explore-the-documentation.md): Give your assistant read access to the Datasentinel documentation through the MCP server that GitBook publishes for it, next to your platform.
- [What you can analyze](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/what-you-can-analyze.md): Almost any analysis you can phrase is possible: these guides are starting points, not a catalog.
- [Work with several platforms](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/work-with-several-platforms.md): Connect several Datasentinel platforms to one assistant, switch between them, and get an overview across all of them.
- [Browse and navigate your fleet](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/browse-your-fleet.md): Display your monitored PostgreSQL inventory at a glance, then narrow it down by tag until you reach the instance you want to work on.
- [Analyze across multiple instances](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/analyze-across-instances.md): Run cross-instance analyses over a group of servers selected by tag.
- [Analyze a workload over a time window](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/analyze-a-workload.md): Explain what happened on one instance during a past time window: session load, waits, top queries, hot tables, and blocking, in one read.
- [Optimize your top queries](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/optimize-top-queries.md): Surface the queries consuming the most time and resources, then act on them.
- [Diagnose a live performance spike](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/diagnose-live-spike.md): Run a real-time analysis to find what is slowing an instance down right now.
- [Investigate a blocking scenario](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/investigate-blocking-scenarios.md): Untangle blocking chains, live or in the past: root blockers, locked objects, and the queries involved.
- [Investigate a workload regression](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/investigate-workload-regression.md): Compare the workload before and after a change to pinpoint what regressed.
- [Explain execution plans](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/explain-execution-plans.md): Get the plan the planner would choose right now for a statement you paste, or for a query already analyzed, without executing anything.
- [Review tables, indexes and autovacuum](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/tables-indexes-and-autovacuum.md): Review the physical health of your tables and indexes: bloat, missing or unused indexes, and whether autovacuum keeps up.
- [Compare two workloads](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/compare-workloads.md): Compare workloads across time periods, instances, or applications.
- [Track drift over time](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/track-drift-over-time.md): Proactively spot slow drift before it becomes an incident: query times creeping up, bloat building, indexes going unused.
- [Run recurring analyses](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/recurring-analyses.md): Schedule repeatable analyses like daily health checks or weekly digests.
- [Claude Artifact](https://docs.datasentinel.io/manual/ai-connector/dynamic-dashboards/claude-artifact.md): Publish a live Datasentinel dashboard as a Claude Artifact, then shape it to your needs by asking Claude. Requires a public MCP server.
- [Build a Python agent with deepagents](https://docs.datasentinel.io/manual/ai-connector/developers/build-a-python-agent-with-deepagents.md): Use the Datasentinel MCP server and Skill from a Python script with LangChain deepagents, and run it against your platform.
- [Refresh the user token automatically](https://docs.datasentinel.io/manual/ai-connector/developers/refresh-user-token.md): A standalone script that keeps a valid Datasentinel user token cached for scheduled and scripted runs.
- [Analyze a workload and open a ServiceNow ticket](https://docs.datasentinel.io/manual/ai-connector/developers/analyze-and-open-a-servicenow-ticket.md): A Python agent built with LangChain deepagents that answers your prompt about one instance through AI Connector and opens a ServiceNow incident when it finds a problem.
- [The Skill did not load](https://docs.datasentinel.io/manual/ai-connector/troubleshooting/skill-not-loaded.md): The assistant answers about your databases but without the Datasentinel Skill: no banner, no next-step menu, raw output. How to tell, how to load the Skill by hand, and how to stop it from happening a
- [Find the cause in mcp.log](https://docs.datasentinel.io/manual/ai-connector/troubleshooting/read-the-mcp-log.md): When a sign-in or a tool call fails, read mcp.log on the platform host first. It names the cause in one line, where the assistant only shows a generic error.
- [MCP servers on a private network](https://docs.datasentinel.io/manual/ai-connector/troubleshooting/private-network-mcp-servers.md): Which assistants work with a platform that has no public endpoint, and how to keep it private.
- [Self-signed and untrusted TLS certificates](https://docs.datasentinel.io/manual/ai-connector/troubleshooting/ssl-certificates.md): Your assistant rejects the connection because the platform serves a self-signed or internal-CA TLS certificate. Fix it per assistant, without turning verification off.
- [TLS hostname mismatch on API calls](https://docs.datasentinel.io/manual/ai-connector/troubleshooting/tls-hostname-mismatch.md): Every MCP tool call fails with "Hostname mismatch" during the TLS handshake. Set DS\_MCP\_PUBLIC\_URL on the datasentinel\_mcp service to fix it.
- [Sign-in problems](https://docs.datasentinel.io/manual/ai-connector/troubleshooting/sign-in-problems.md): What to do when the sign-in to the Datasentinel MCP server stalls, expires, or comes back after it worked.
- [Sign-in fails on an unknown host name](https://docs.datasentinel.io/manual/ai-connector/troubleshooting/sign-in-unknown-host.md): The sign-in fails with "getaddrinfo ENOTFOUND" or another DNS error on a name you never typed. Set DS\_MCP\_PUBLIC\_URL on the datasentinel\_mcp service to fix it.

## Guides

- [Guides](https://docs.datasentinel.io/manual/guides/readme.md): Each guide is designed to walk you through a specific task, from initial setup to advanced operations, with clear explanations and practical examples.
- [Connect an AI Assistant to Datasentinel](https://docs.datasentinel.io/manual/guides/readme/connect-an-ai-assistant.md): From a fresh install or an upgrade to your first conversation with an AI assistant: MCP server, metrics, users, and first analyses.
- [Generate, Email, and Schedule PDF Reports](https://docs.datasentinel.io/manual/guides/readme/pdf-reports.md): Produce, email, and schedule PDF reports of your PostgreSQL workload. Keep them as long-term snapshots without paying the storage cost of extended metric retention, and use two reports as a before/aft
- [Install On-Premises and Configure Agentless Connections](https://docs.datasentinel.io/manual/guides/readme/install-on-premises-and-agentless.md): Install the Datasentinel platform on a single Linux server, then connect your PostgreSQL instances agentlessly, with no agent to deploy on the database hosts.
- [Onboard Your First PostgreSQL Cluster](https://docs.datasentinel.io/manual/guides/readme/onboard-your-first-cluster.md): The golden path from a brand-new PostgreSQL instance to a fully monitored cluster: extensions, monitoring user, network access, connection, and tags.
- [Automate with the API](https://docs.datasentinel.io/manual/guides/readme/automate-with-the-api.md): Drive Datasentinel programmatically — provision monitored instances, manage users and roles, export metrics, schedule reports, and control agents through the REST API.
- [Monitor Cloud-Managed Instances](https://docs.datasentinel.io/manual/guides/readme/monitor-cloud-managed-instances.md): Datasentinel supports monitoring of managed PostgreSQL instances from major cloud providers, including Amazon Web Services, Google Cloud, and Microsoft Azure, among others.
- [Monitor High-Availability Clusters](https://docs.datasentinel.io/manual/guides/readme/monitor-high-availability-clusters.md): Datasentinel supports monitoring high-availability (HA) PostgreSQL clusters, allowing activity analysis across primary and replica instances from a single, consolidated view.
- [Manage Users and Role-Based Access](https://docs.datasentinel.io/manual/guides/readme/manage-users-and-role-based-access.md): Datasentinel provides role-based access control (RBAC) to restrict user access to PostgreSQL instances based on tags.
- [Organize Content using Tags](https://docs.datasentinel.io/manual/guides/readme/organize-content-using-tags.md): Label instances with custom tags to filter dashboards, consolidate workloads, and scope user access.


---

# 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
This site has an agentic ask interface you may use to 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/index.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.
