Skip to content

Update recommended maximum database instances #30452

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 17, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion layouts/shortcodes/dbm-mysql-agent-config-examples.en.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
### One agent connecting to multiple hosts
It is common to configure a single Agent host to connect to multiple remote database instances (see [Agent installation architectures](/database_monitoring/architecture/) for DBM). To connect to multiple hosts, create an entry for each host in the MySQL integration config.
In these cases, Datadog recommends limiting the number of instances per Agent to a maximum of 10 database instances to guarantee reliable performance.
An agent with 4 CPUs and 16GB of RAM can monitor up to 30 databases with the same resources each.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
An agent with 4 CPUs and 16GB of RAM can monitor up to 30 databases with the same resources each.
For example, an Agent running on a host with 4 CPU cores and 16 GB of RAM can usually monitor up to 30 databases.


```yaml
init_config:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
### One agent connecting to multiple hosts
It is common to configure a single Agent host to connect to multiple remote database instances (see [Agent installation architectures](/database_monitoring/architecture/) for DBM). To connect to multiple hosts, create an entry for each host in the Postgres integration config.
In these cases, Datadog recommends limiting the number of instances per Agent to a maximum of 10 database instances to guarantee reliable performance.
An agent with 4 CPUs and 16GB of RAM can monitor up to 30 databases with the same resources each.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
An agent with 4 CPUs and 16GB of RAM can monitor up to 30 databases with the same resources each.
For example, an Agent running on a host with 4 CPU cores and 16 GB of RAM can usually monitor up to 30 databases.

```yaml
init_config:
instances:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ instances:

### One Agent connecting to multiple hosts
It is common to configure a single Agent host to connect to multiple remote database instances (see [Agent installation architectures][1006] for DBM). To connect to multiple hosts, create an entry for each host in the SQL Server integration config.
In these cases, Datadog recommends limiting the number of instances per Agent to a maximum of 10 database instances to guarantee reliable performance.
An agent with 4 CPUs and 16GB of RAM can monitor up to 30 databases with the same resources each.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
An agent with 4 CPUs and 16GB of RAM can monitor up to 30 databases with the same resources each.
For example, an Agent running on a host with 4 CPU cores and 16 GB of RAM can usually monitor up to 30 databases.

```yaml
init_config:
instances:
Expand Down Expand Up @@ -218,4 +218,4 @@ instances:
```

[1005]: https://github.com/DataDog/integrations-core/blob/master/sqlserver/datadog_checks/sqlserver/data/conf.yaml.example
[1006]: /database_monitoring/architecture/
[1006]: /database_monitoring/architecture/
Loading