Documentation Page
https://docs.datadoghq.com/database_monitoring/setup_oracle/troubleshooting/
File: content/en/database_monitoring/setup_oracle/troubleshooting.md
Issue Description
The troubleshooting page has a "Custom queries are not working properly" section whose only content is "Ensure that the recommended Agent version is installed." Multiple customers have configured Oracle custom queries correctly but the metric never appeared, with no actionable troubleshooting path available in the docs.
Expand the existing "Custom queries are not working properly" section with:
- YAML structure check:
custom_queries must be nested under instances, not init_config — this is the most common misconfiguration
- How to verify the metric is being collected: check agent logs for query execution errors, then confirm the metric appears in Metrics Summary (not just dashboards) using the configured
metric_prefix
- Permission requirement: the Datadog user needs
SELECT on any view or table referenced by the custom query, beyond the standard setup grants
Evidence: ZD #2457081, #2490479, #2543007, #2407794
Documentation Page
https://docs.datadoghq.com/database_monitoring/setup_oracle/troubleshooting/
File:
content/en/database_monitoring/setup_oracle/troubleshooting.mdIssue Description
The troubleshooting page has a "Custom queries are not working properly" section whose only content is "Ensure that the recommended Agent version is installed." Multiple customers have configured Oracle custom queries correctly but the metric never appeared, with no actionable troubleshooting path available in the docs.
Expand the existing "Custom queries are not working properly" section with:
custom_queriesmust be nested underinstances, notinit_config— this is the most common misconfigurationmetric_prefixSELECTon any view or table referenced by the custom query, beyond the standard setup grantsEvidence: ZD #2457081, #2490479, #2543007, #2407794