Cloud Explorer#
Cloud Explorer is the inventory view: everything that exists across your connected cloud accounts, in one searchable list. It answers "what do we actually have", which every other page assumes you already know.
Opening it#
Cloud → Explorer. It populates automatically from your connected cloud accounts and needs no configuration.
What it shows#
Every discovered resource with its provider, account, region, type, name, tags, state and the metrics attached to it. Click any resource to open its detail view with its metrics, related resources and recent audit events.
| Provider | Examples of what is discovered |
|---|---|
| AWS | EC2, RDS, Lambda, ECS and EKS, load balancers, S3, CloudFront, API Gateway, DynamoDB, ElastiCache, SQS, SNS |
| Azure | Virtual Machines, AKS, Azure SQL, Storage Accounts, App Service, Load Balancers, Cosmos DB |
| Google Cloud | Compute Engine, GKE, Cloud SQL, Cloud Storage, Cloud Run, Load Balancers, Pub/Sub |
| Linode | Instances, managed databases, NodeBalancers, Object Storage, Volumes |
Filtering#
Filter by provider, account, region, resource type, tag or state, and combine filters. Some questions this answers quickly:
- Untagged resources: filter to a missing tag key to find what is escaping your cost allocation.
- Stopped but not deleted: filter by state to find instances still attracting storage charges.
- Public exposure: filter to resources with a public IP or public access enabled.
- Unmonitored: filter to resources with no metrics, which usually means the service was not enabled on the integration.
Tags#
Tags are collected as they are, and are then usable as filters and as dimensions in Cost Explorer. Consistent tagging is what makes cost allocation work, so Cloud Explorer is normally where a tagging cleanup starts.
Tags are read on each collection cycle. A newly applied tag appears within one interval; it does not retroactively apply to historical cost data, because the provider's own billing records carry the tags as they were at the time.
From inventory to monitoring#
Selecting a resource shows its metrics and lets you create an alert on it directly, without finding the metric name by hand. This is the quickest route from "this instance exists" to "tell me when it has a problem".
Staleness#
Inventory is refreshed on the integration's collection interval. A resource deleted in the cloud disappears at the next refresh, and one created appears the same way. If the list looks wrong, check that the integration is still connected: an expired credential leaves the last known inventory in place, which can look like a live view when it is not.