> 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/getting-started/installation.md).

# Installation

What to install, in which order, and what to check first: the platform for on-premises use, then agents or agentless connections to your PostgreSQL clusters.

Datasentinel has two parts to set up: the **platform**, which stores and displays the metrics, and the **collection**, which reads them from your PostgreSQL clusters. What you install depends on your deployment.

| Deployment      | Platform                                    | Collection                             |
| --------------- | ------------------------------------------- | -------------------------------------- |
| **On-premises** | You install it, on a dedicated Linux server | Agents, agentless connections, or both |
| **SaaS**        | Hosted by Datasentinel, nothing to install  | Agents, installed on your side         |

See the [Architecture](https://docs.datasentinel.io/manual/getting-started/architecture.md) for the components and the data flows.

## Before you start

| Check                   | Details                                                                                                                                                                                                                                                                             |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **License key**         | Required to use Datasentinel. Get a [60-day trial key](https://docs.datasentinel.io/manual/free-trial.md), or ask support for your customer key.                                                                                                                                    |
| **Platform server**     | Linux only: RHEL, Rocky Linux or AlmaLinux 8 and 9, SLES 15, Debian Bullseye. We advise a dedicated machine, preferably a virtual machine you can resize.                                                                                                                           |
| **Sizing**              | It depends on the number of instances and on the retention. For 1 to 10 instances with a 14-day retention: 4 CPUs, 8 GB of memory, 25 GB of storage. See the full [sizing table](https://docs.datasentinel.io/manual/getting-started/installation/platform.md#system-requirements). |
| **Network**             | Users and agents reach the platform on port **443** by default. See the [security rules](https://docs.datasentinel.io/manual/getting-started/installation/platform.md#security-rules).                                                                                              |
| **SELinux**             | Must be Permissive or Disabled on the platform server.                                                                                                                                                                                                                              |
| **PostgreSQL clusters** | Version 9.4 or later, with the [pg\_stat\_statements](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/extensions/pg_stat_statements.md) extension.                                                                                                          |

## Installation steps

{% stepper %}
{% step %}

### Install the platform

On-premises only. Download the archive and run the installation script: it installs and starts all the components. Then open the user interface and enter your license key.

See [Platform](https://docs.datasentinel.io/manual/getting-started/installation/platform.md).
{% endstep %}

{% step %}

### Prepare your PostgreSQL clusters

Create the monitoring user and install the extensions. One connection per cluster is enough to monitor all its databases.

See [PostgreSQL clusters](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters.md).
{% endstep %}

{% step %}

### Connect the clusters

Choose a collection method for each cluster, as described below.

* **Agent-based**: install an agent on the server and declare the instance. See [Agent](https://docs.datasentinel.io/manual/getting-started/installation/agent.md).
* **Agentless**: declare the connection on the platform. See [Agentless Monitoring](https://docs.datasentinel.io/manual/features/other-features/agentless-monitoring.md).
  {% endstep %}

{% step %}

### Check the result

Open the user interface. The instance appears, and its first metrics follow within minutes. If not, see [Troubleshooting](https://docs.datasentinel.io/manual/implementation/troubleshooting.md).
{% endstep %}
{% endstepper %}

## Agent-based or agentless?

Both methods collect the same metrics, and the dashboards are identical. You can mix them on the same platform.

|                    | Agent-based                                                                 | Agentless                                                                                                                              |
| ------------------ | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **To install**     | One agent per server. An agent monitors all the clusters of its server.     | Nothing on the database server                                                                                                         |
| **Connection**     | The agent sends the metrics to the platform                                 | The platform connects to the cluster                                                                                                   |
| **Network**        | Platform port open to the agents. Agent port **8282** open to the platform. | PostgreSQL port open to the platform                                                                                                   |
| **System metrics** | Collected by the agent                                                      | Need the [system\_stats](https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/extensions/system_stats.md) extension |
| **Best for**       | Self-managed PostgreSQL on physical or virtual servers                      | Cloud-managed databases, containers, large fleets                                                                                      |
| **SaaS**           | Yes                                                                         | No                                                                                                                                     |

The full comparison is in the [Architecture](https://docs.datasentinel.io/manual/getting-started/architecture.md) page.

## Installation pages

{% content-ref url="/pages/NWHE4JQgbY6GLYsMK4qx" %}
[Platform](https://docs.datasentinel.io/manual/getting-started/installation/platform.md)
{% endcontent-ref %}

{% content-ref url="/pages/U9z3vH2aZe9lYoIcMZxd" %}
[Agent](https://docs.datasentinel.io/manual/getting-started/installation/agent.md)
{% endcontent-ref %}

## After the installation

* Organize your instances with [tags](https://docs.datasentinel.io/manual/features/tips-and-hints/tags.md).
* Discover the [Key Features](https://docs.datasentinel.io/manual/features/key-features.md).
* Keep the platform and the agents up to date. See [Upgrade](https://docs.datasentinel.io/manual/implementation/upgrade.md).


---

# 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.datasentinel.io/manual/getting-started/installation.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.
