Glossary

A glossary of key terms used throughout the Cloudchipr platform.

• Live tracked resources: Cloudchipr regularly gathers resource metadata and usage metrics every 15 minutes across all accounts and regions.
• Filtered Resources: Cloudchipr has pre-configured filters that can highlight underutilized resources. In addition, users can define their own filters based on their specific needs, and Cloudchipr will identify the resources that meet those filters. For compute instances, those filters can be defined to catch the ones with low CPU utilization or resources that don't have a specific tag. Users can decide which filters will match their organization's cloud hygiene policy.
• Total Tracked: The total monthly price of all collected resources supported by Cloudchipr. Please note that Monthly prices are calculated based on the on-demand list price of each resource.
• Resource Explorer: Resource Explorer in Cloudchipr helps users analyze multi-cloud billing based on any filter criteria. It offers historical cost, current waste, and cloud grouping by dimensions such as Product Family, Account, Cloud Provider, and more. Resource Explorer has a robust table that lets users filter by dimension to a single resource. For example, it only takes two clicks to group resources by Storage family, navigate down that dimension, and identify the costliest EBS volume
• Scope: Scopes (previously Views) are specific filtered slices of your cloud resources based on filters. For example, you can create a Scope named "Production" and apply filters to display the spend from only Production cloud accounts. After the Scope is created, it's possible to explore Production resources, have a forecasted cost, identify underutilized resources, apply budgets, and create dashboards based on this Scope.
• Account Groups: Account Groups (previously known as Categories) are named groups of cloud accounts that can be used in filters and dashboard widgets. Companies often categorize their cloud accounts based on environment (production/development) or teams. These groups can then be used in filters and widgets to keep the cloud costs under control.
• Filter Templates: Filter Templates are named set of powerful filters that help you apply resource identifier(ID, TAG, Name, etc...) and usage metrics-based (CPU, RAM, Traffil, etc...) filters on your resources. This helps you identify the resources that need attention. For example, you can filter virtual machines that haven't had a CPU spike for the last 7 days and haven't had more than 100Mb of network input and output traffic in the last 30 days. Each resource type has its own metric-based filters. EBS volumes can be filtered based on the resources they are attached to or the amount of IOPS, while databases can be filtered based on their connections.