CMDB Queries
CMDB queries help you retrieve a focused set of inventory and relationship records for investigation, reporting, automation, and export workflows. A query can be an interactive filter in the CMDB UI, a saved list view, or an API-based request.
When to Use Queries
Use CMDB queries to:
- Find resources by provider, account, subscription, project, region, object type, tag, owner, environment, or lifecycle state.
- Identify coverage gaps, such as assets without monitoring, backups, vulnerability scanning, or required ownership metadata.
- Build reusable scopes for reports, dashboards, exports, and operational reviews.
- Validate relationships between applications, infrastructure, findings, tickets, and other CMDB records.
Query Patterns and Filters
Most CMDB analysis starts with a scoped query. To keep queries accurate and performant:
- Filter by provider, account, subscription, project, region, and object type before adding broader conditions.
- Use tags and metadata, such as owner, environment, application, business unit, and criticality, to focus on relevant assets.
- Combine CMDB Attributes with Enrichment results to find gaps, such as resources that are not monitored, not backed up, or missing vulnerability coverage.
- Use Relationships, such as application ↔ instance ↔ database, to answer impact and dependency questions.
Provider-specific object names, identity fields, and relationship models are documented in the API & Schema.
Query CMDB Data
You can query CMDB data from the Cloudaware UI or through authenticated API access.
CMDB UI
Use the CMDB UI when you need to explore records, validate fields, or save reusable views.
- Use Browse Objects to inspect object fields and build query scopes interactively.
- Create CMDB List Views to save filters and columns for repeated use.
Programmatic Access
Use API-based queries when you need to automate exports, integrate with external systems, or reproduce CMDB scopes outside the Cloudaware UI.
API-based CMDB queries require authenticated access to the Cloudaware account and the underlying Salesforce org.
Before running SOQL or REST API queries from external tools, configure an OAuth app and integration user for Cloudaware CMDB API access. For setup details, see:
- External Client App with OAuth 2.0 Client Credentials Flow
- External Client App with OAuth 2.0 JWT Bearer Flow
Export and Share Query Results
CMDB query results can be shared outside Cloudaware for analysis, audit, or integration workflows.
- Export list views to CSV for ad hoc analysis or stakeholder review.
- Use the Show equivalent option, where available, to get an API query such as SOQL or curl that reproduces a list view programmatically.
- Integrate CMDB data with external analytics platforms, data warehouses, or SIEMs by using Cloudaware APIs and the provider or CMDB schemas documented in the API & Schema.
When exporting or replicating CMDB data, make sure downstream consumers follow CMDB governance requirements, including access controls, data classification, and retention policies.
Use Query Data in Reports and Dashboards
After you define reliable query scopes, you can use them to support reporting and operational reviews.
- Create summary list views by owner, business unit, environment, or region to show where risk, coverage gaps, or spend are concentrated.
- Build Reports and dashboards that track CMDB-backed KPIs, such as monitoring coverage, vulnerability scanning coverage, backup coverage, compliance status, and cost allocation readiness.
- Reuse the same scoped views across modules, such as Compliance Engine, Cost Management, Monitoring, and Vulnerability Management, so stakeholders work from consistent data.
Treat CMDB as the shared source of truth. Avoid creating separate inventory lists in downstream tools unless they are governed, synchronized, and clearly documented.