[DBM][Postgres] Adds logical database breakdown for connection metrics#22999
[DBM][Postgres] Adds logical database breakdown for connection metrics#22999aldrickdev wants to merge 16 commits intomasterfrom
Conversation
…ion metrics Signed-off-by: aldrick.castro <aldrick.castro@datadoghq.com>
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🔗 Commit SHA: b7998b2 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback! |
Signed-off-by: aldrick.castro <aldrick.castro@datadoghq.com>
Signed-off-by: aldrick.castro <aldrick.castro@datadoghq.com>
Signed-off-by: aldrick.castro <aldrick.castro@datadoghq.com>
ff804bc to
75b8506
Compare
Signed-off-by: aldrick.castro <aldrick.castro@datadoghq.com>
d82cf60 to
f426d52
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f426d528b3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
The following files, which will be shipped with the agent, were modified in this PR and You can ignore this if you are sure the changes in this PR do not require QA. Otherwise, consider removing the label. List of modified files that will be shipped with the agent |
What does this PR do?
This will add 2 new connection metrics that have a logical database breakdown.
postgresql.database_connectionspostgresql.percent_database_usage_connectionsExample of both metrics below:
Motivation
Customer Request -> SDBM-2452
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged