ops0ops0

Query Console

Ask questions about your infrastructure in plain English. The Query Console connects to your Oxid PostgreSQL backend and lets you explore resources, dependencies, costs, vulnerabilities, and project relationships without writing any code.


How It Works

Type a question in plain English. The Query Console translates it into a database query, runs it against your Oxid state backend, and returns the results.

Example questions:

  • "Show me all EC2 instances across my projects"
  • "Which resources cost the most per month?"
  • "What depends on my networking project?"
  • "Show resources with critical vulnerabilities"
  • "How many resources does each project manage?"
  • "List all S3 buckets without encryption"

No SQL knowledge required. Just describe what you want to know.


What You Can Explore

Resources and State

Browse all managed resources, their attributes, current state, and metadata across every project.

Dependencies

See cross-resource and cross-project dependencies, module references, and terraform_remote_state links.

Cost Breakdown

View cost estimates per resource, per project, or per cloud provider with cost overlays on results.

Vulnerabilities

Surface Checkov findings and security issues alongside the resources they affect.

Project Connections

See which projects share state, reference outputs from other projects, or deploy to the same accounts.

Resource Attributes

Drill into any resource attribute like tags, regions, instance types, storage sizes, and configurations.


Query Interface

ComponentDescription
Natural Language InputType a question in plain English to explore your infrastructure
Project SelectorScope queries to one or more Oxid-enabled projects
Schema BrowserBrowse available tables, columns, and data types
Cost OverlayToggle cost data alongside query results
Vulnerability OverlayToggle vulnerability findings alongside query results
Results TableSortable, filterable results with pagination

Working with Results

FeatureDescription
Column SortingClick column headers to sort ascending or descending
Column VisibilityToggle which columns are shown
FilteringApply additional filters to narrow result rows
PaginationNavigate through large result sets
Row SelectionSelect rows for bulk operations
Cost ColumnSee estimated monthly cost per resource when cost overlay is enabled
Vulnerability ColumnSee severity and check details when vulnerability overlay is enabled

Saving and Sharing Queries

Save any query for quick access, share it with your team, or mark it as a favorite.

Run Your Query

Type a question and get results.

Click Save

Click the Save button in the toolbar.

Name Your Query

Give it a descriptive name and optional description.

Choose Visibility

Select whether the query is private or shared with your organization.

FieldDescription
NameDisplay name for the saved query
DescriptionOptional description of what the query does
ProjectsWhich projects the query targets
FavoriteMark as favorite for quick access in the sidebar
Usage CountHow many times the query has been run
Last UsedWhen the query was last executed

Exporting Results

FormatUse Case
CSVSpreadsheet analysis, reporting, sharing with stakeholders
JSONIntegration with other tools, scripting, automation

Click the Export button in the results toolbar to download the current result set.


SectionDescription
Recent QueriesYour most recently executed queries
FavoritesQueries you have marked as favorites
Shared QueriesQueries shared by your team
ProjectsBrowse queries grouped by project

Requirements

The Query Console requires Oxid to be enabled on at least one project. Oxid stores your IaC state in a PostgreSQL database, which is what the Query Console reads from.

Oxid Required

Only projects using Oxid as their state backend appear in the Query Console. See IaC Projects to enable Oxid on a project.


Troubleshooting

No Results Returned
Ensure Oxid is enabled on the project and at least one deployment has completed. The Query Console reads from the Oxid PostgreSQL database, which is populated after a successful apply.
Tables Not Showing in Schema Browser
Tables are created during the first Oxid sync. Run a deployment or trigger an Oxid sync to populate the schema.
Query Timeout
Large result sets may take longer. Try asking a more specific question or reduce the number of selected projects.

Next Steps