Definitions
What the numbers on the BYOC dashboards mean.
Who counts​
| Term | Meaning |
|---|---|
| Customer | A company. Accounts are grouped by their company name, so one customer can have several accounts. |
| Account | A BYOC account. Accounts belong to an organization. |
| Organization | The billing/ownership grouping above accounts. A company usually has one organization, sometimes more. |
| Internal account | A CelerData-owned account. Left out of every customer-facing chart. |
| Active account | An account in good standing. BYOC Summary counts active accounts only. |
| Free-tier cluster | A cluster on the free tier. Left out everywhere, so a customer with only free-tier clusters doesn't count as a customer. |
Clusters​
| Term | Meaning |
|---|---|
| Cluster ID | The cluster's unique ID (a UUID). |
| Live cluster (BYOC Summary) | A cluster that exists right now: not deleted, not released, not in error. Stopped clusters count. |
| Live cluster (BYOC Trends) | A cluster that billed at least once in the period. |
| Cluster status | Running, Stopped or Deleted. |
| ELASTIC / CLASSIC | The two cluster types. ELASTIC clusters have FE nodes and warehouses; CLASSIC clusters have FE and BE nodes. |
| Version bucket | 4.0+, pre-4.0, or unknown (no version recorded). "on 3.5.x" is part of pre-4.0. |
| Environment | prod, non-prod (dev/staging/test) or unknown, from the cluster's environment tag. |
| Creation method | MANUAL, QUICK_DEPLOY or TERRAFORM. Older clusters predate the other methods and count as MANUAL. |
| AZ mode | Single-AZ or Multi-AZ, from where the cluster's machines run. "Unknown" until the AZ data is refreshed. |
Usage​
| Term | Meaning |
|---|---|
| CCU | CelerData Compute Units: the billed compute, recorded per cluster per hour. Charts show thousands (K); drills show exact values. |
| Average monthly CCU | A period's CCU scaled to a month: a month as is, a quarter ÷ 3, a week × 52/12. |
| Cores (top-100) | CPU cores of the week's 100 biggest clusters by CCU. Monthly and quarterly figures are the average weekly total. |
BYOC Trends logic​
| Term | Meaning |
|---|---|
| Qualified organization / account | Billed at least Min Live Clusters clusters and at least Min Avg Monthly CCU in the period. With the defaults (1 and 0) that's anyone who billed. |
| Growth % | (this period − previous period) ÷ previous period. Blank for the first period shown. |
| Added / Churned | Qualified this period but not the previous one / the reverse, with the same thresholds as the chart. A customer that stops and later returns is churned, then added again. |
Time​
| Term | Meaning |
|---|---|
| Week / month / quarter | Calendar periods in Pacific time. Weeks start on Monday; Q1 is January–March. |
| Partial period | One that isn't complete: the current, unfinished period, or a first period the date window cuts short. BYOC Trends hides them unless Include Partial Periods is Yes. |
Customer tier​
| Term | Meaning |
|---|---|
| Customer tier | S, A, B or C, from the customer profile (maintained outside these dashboards), matched to accounts by company name and refreshed hourly. |
| Untiered | No profile matches the company, or the profile has no tier. Most small and trial customers. |
| Customer stage | Production, Implementation, POC, TechWin, OnHold, Churned… from the profile. |