rds.query-insights.list-tablesTables and indexes with findings: sequential scans, unused and duplicate indexes, vacuum overdue
Request syntax
GET /rds/api/instances/{id}/insights/tablesPath parameters
idRequiredstring
Constraints: 3-64 chars, /^(?!ewdoc-)[a-z0-9-]+$/
Response
200 with database, tables (schema, table, rows, deadRows, bytes, seqScans, seqRowsRead, indexScans, lastVacuum, lastAnalyze, findings) and indexFindings.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
databaseAlwaysstring
Database readtablesAlwaysarray of object
Up to 200 tables, largest firsttables[].schemaAlwaysstring
Schematables[].tableAlwaysstring
Tabletables[].rowsAlwaysnumber
Live rows (estimate)tables[].deadRowsAlwaysnumber
Dead rows waiting for vacuumtables[].bytesAlwaysnumber
Size with indexes, bytestables[].seqScansAlwaysnumber
Sequential scanstables[].seqRowsReadAlwaysnumber
Rows those scans readtables[].indexScansAlwaysnumber, may be null
Index scans; null: no indextables[].lastVacuumAlwaysstring, may be null
Last vacuum; null: nevertables[].lastAnalyzeAlwaysstring, may be null
Last analyze; null: nevertables[].findingsAlwaysarray of object
Findings with suggested actionstables[].findings[].kindAlwaysone of slow-average, slow-sometimes, missing-index, spills-to-disk, n-plus-one, seq-scan-large-table, unused-index, duplicate-index, vacuum-overdue, long-running, idle-in-transaction, lock-wait
What was foundtables[].findings[].severityAlwaysone of high, medium, info
How much it matterstables[].findings[].titleAlwaysstring
One line: what was seentables[].findings[].evidenceAlwaysstring
The numbers behind ittables[].findings[].actionAlwaysstring
What to do about ittables[].findings[].sqlWhen presentstring
A statement to copy and run yourself (CREATE INDEX CONCURRENTLY, …); absent when noneindexFindingsAlwaysarray of object
Unused and duplicate indexesindexFindings[].kindAlwaysone of slow-average, slow-sometimes, missing-index, spills-to-disk, n-plus-one, seq-scan-large-table, unused-index, duplicate-index, vacuum-overdue, long-running, idle-in-transaction, lock-wait
What was foundindexFindings[].severityAlwaysone of high, medium, info
How much it mattersindexFindings[].titleAlwaysstring
One line: what was seenindexFindings[].evidenceAlwaysstring
The numbers behind itindexFindings[].actionAlwaysstring
What to do about itindexFindings[].sqlWhen presentstring
A statement to copy and run yourself (CREATE INDEX CONCURRENTLY, …); absent when noneindexFindings[].tableAlwaysstring
Table of the indexindexFindings[].indexAlwaysstring
The index
Checked against the handlers: every route test validates their answers against this schema.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow rds:DescribeDBQueryInsights on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud rds query-insights list-tables idcurl -X GET "https://console.platform-development.deutschecloud.app/rds/api/instances/id/insights/tables" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_rds_query-insights_list-tables.