Update recommended maximum database instances #30452
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
rtrieu
approved these changes
Jul 14, 2025
| @@ -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. | |||
There was a problem hiding this comment.
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. |
| @@ -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. | |||
There was a problem hiding this comment.
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. |
| @@ -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. | |||
There was a problem hiding this comment.
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Updates the recommended number of database instances per agent in accordance with most recent testing.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes