Core Concepts
Key terms and data-model primitives that appear throughout Pelanor.
A clear understanding of these concepts will help you navigate Pelanor and get the most from its cost-optimization features.
Vendor-Specific vs. Vendor-Agnostic Terminology
Pelanor lets you analyse cost data from two complementary angles:
Perspective | When to Use | Examples |
---|---|---|
Vendor-specific | Query or group by each cloud provider’s native fields. |
|
Vendor-agnostic | Apply FOCUS-aligned, cross-cloud terminology that works the same in AWS, Azure, and GCP. | Usage Category · Service Name · Entity Type |
Properties vs. Metrics
Concept | Purpose | Typical Uses | Examples |
---|---|---|---|
Properties | Descriptive metadata collected from Pelanor integrations. |
|
|
Metrics | Numeric measurements—Cost is the primary one. |
|
|
Pelanor auto-collects metrics from its platform and service integrations. You can further extend the metrics list by pushing Custom Metrics into Pelanor.
Resources vs. Entities
Layer | Definition | Examples |
---|---|---|
Resources | Items that appear directly in billing exports. | ARN (AWS) · Global Name (GCP) · Region · Account |
Entities | Logical groupings or subdivisions of resources. |
|
Dimensions & Segments
Dimensions provide business-aligned views of cost data—think “cost per X” (Tenant, Business Unit, Feature, etc.).
Each dimension contains multiple Segments, which define individual values and their selection rules.
After creation, dimensions appear under Custom Dimensions in the property tree and are available for grouping and filtering everywhere in Pelanor.
Ways to Create Dimensions
Method | Best For |
---|---|
Manual | A small, mostly static list (e.g. Departments) |
Tag-based (“Batch”) | Leverage existing tags and properties to auto-populate segments (example: you already have a Tenant tag with a reasonable coverage percentage) |
API | Automating updates or syncing from external systems such as CRMs |
For API details, see the Dimensions & Segments section of the Pelanor API reference.