PG: Add sequence metrics

[bonnefoa]

What does this PR do?

Generate metrics reporting the min, max and last_value of sequences. This will allow to monitor if a sequence is about to be exhausted.

Motivation

One issue is that users can't read a sequence's last value without SELECT permission on the sequence. This means a GRANT would be required for all sequences on all databases in order to allow the datadog agent user to read this last value.

Instead, we rely on a new pg_sequences function in the datadog schema that will be owned by the Postgres user, and GRANT it to the datadog-agent user. This will allow the agent to access all sequences, present and future, without having to provide additional GRANT.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: feece89a5f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[datadog-prod-us1-4]

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 96.67%
• Overall Coverage: 92.80% (+5.66%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: cd3428f | Docs | Datadog PR Page | Give us feedback!}

[cit-pr-commenter-54b7da]

Monitor Template Quality Assessment

52 monitors analyzed across 9 integrations.

• 31 monitors have missing sections
• Most common missing sections: WHY, IMPACT, HOW_TO_TROUBLESHOOT

Monitors with missing sections

Integration	Monitor	Missing Sections	Suggested Links
kubernetes	[Kubernetes] Monitor Kubernetes Deployments Replica Pods	IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS	- Logs

• Infrastructure
• Metrics Explorer (kubernetes_state.deployment.replicas_desired)
• Metrics Explorer (kubernetes_state.deployment.replicas_available) |
  | kubernetes | [Kubernetes] Monitor Unschedulable Kubernetes Nodes | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.node.status) |
  | kubernetes | [Kubernetes] Pod {{pod_name.name}} is CrashloopBackOff on namespace {{kube_namespace.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.container.status_report.count.waiting) |
  | kubernetes | [Kubernetes] Pod {{pod_name.name}} is ImagePullBackOff on namespace {{kube_namespace.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.container.status_report.count.waiting) |
  | kubernetes | [Kubernetes] Pod {{pod_name.name}} is OOMKilled on namespace {{kube_namespace.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes.containers.state.terminated) |
  | kubernetes | [Kubernetes] Monitor Kubernetes Failed Pods in Namespaces | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.pod.status_phase) |
  | kubernetes | [Kubernetes] Monitor Kubernetes Pods Restarting | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes.containers.restarts) |
  | kubernetes | [Kubernetes] Monitor Kubernetes Statefulset Replicas | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.statefulset.replicas_desired)
• Metrics Explorer (kubernetes_state.statefulset.replicas_ready) |
  | nginx | [NGINX] 5xx Errors higher than usual | WHY | - Logs
• Infrastructure
• Metrics Explorer (nginx.upstream.peers.responses.5xx) |
  | postgres | [Postgres] Number of connections is approaching connection limit on {{host.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Metrics Explorer (postgresql.percent_usage_connections) |
  | postgres | [Postgres] Replication delay is abnormally high on {{host.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Metrics Explorer (postgresql.replication_delay) |
  | redis | [Redis] High memory consumption | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Metrics Explorer (redis.mem.used)
• Metrics Explorer (redis.mem.maxmemory) |
  | amazon-rds | [AWS] RDS CPU utilization is high | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (aws.rds.cpuutilization) |
  | amazon-rds | [AWS] RDS Anomaly in database connections | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (aws.rds.database_connections) |
  | amazon-rds | [AWS] RDS Storage utilization is high | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (aws.rds.free_storage_space)
• Metrics Explorer (aws.rds.total_storage_space) |
  | amazon-sqs | Queue {{queuename.name}} has a high age of oldest message | WHY | - Logs
• Infrastructure
• Metrics Explorer (aws.sqs.approximate_age_of_oldest_message) |
  | amazon-sqs | Queue {{queuename.name}} has a high number of visible messages | WHY | - Logs
• Infrastructure
• Metrics Explorer (aws.sqs.approximate_number_of_messages_visible) |
  | apm | Abnormal change in p75 latency for $service.value on $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Watchdog Anomaly: {{event.title}} for {{service}} | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | Monitor type is not supported for message generation: event-v2 alert |
  | apm | New issues found for $service on $env | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | High p95 latency for $service on $env | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Abnormal change in Apdex for $service.value on $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Low traffic on $service on $env | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | New issues found for {{service}} on {{env}} | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | Monitor type is not supported for message generation: error-tracking alert |
  | apm | No data for $service.value on $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Increased error rate for $service.value in $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | real-user-monitoring | Crash-Free Session Rate is low | WHY | Unhandled exception while parsing message: parsing metric query failed: Rule 'or_op' didn't match at '.name}.as_count() / ' (line 1, column 38). |
  | system | Disk usage is high for host {{host.name}} on device {{device.name}} | WHY | - Logs
• Infrastructure
• Metrics Explorer (system.disk.free)
• Metrics Explorer (system.disk.total) |
  | system | System load is high for host {{host.name}} | WHY | - Logs
• Infrastructure
• Metrics Explorer (system.load.norm.1) |
  | system | Network traffic (sent) is high on host {{host.name}} | WHY | - Logs
• Infrastructure
• Metrics Explorer (system.net.bytes_sent) |
  | system | Host $host.value not reporting data | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | Monitor type is not supported for message generation: service check |

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.35%. Comparing base (6597bfd) to head (cd3428f).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dd-octo-sts]

Validation Report

All 20 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and Codecov settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run