# FOCUS data usage export

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Faccount-management%2Fpayment-and-billing%2Fdata-usage%2Ffocus-export.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Faccount-management%2Fpayment-and-billing%2Fdata-usage%2Ffocus-export.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

A FOCUS data usage export delivers your Coralogix consumption and cost data in the [FOCUS v1.3](https://focus.finops.org/) format — the FinOps Open Cost and Usage Specification that cost-management and FinOps tools ingest directly. Export your usage in this format to bring Coralogix spend into the same reporting pipeline as your other cloud and SaaS costs, without manual transformation.

This page is a reference for what the exported file contains: the columns, their meaning, and the mappings Coralogix applies. To generate the file, use the **Focus report** option in the Generate report drawer on the Data Usage page — see [Focus report](https://coralogix.com/docs/user-guides/account-management/payment-and-billing/data-usage.md#focus-report).

## File format[​](#file-format "Direct link to File format")

A FOCUS export is a single CSV file, packaged as a `.zip` archive. Each row is one line item: a day of usage for one service, at one TCO priority, for one team. Coralogix aggregates usage to daily granularity, so there is one row per day per line item within the exported date range.

Column headers follow the FOCUS specification exactly, including capitalization. Columns whose names begin with `x_cx_` are Coralogix-defined extensions to the specification.

## Cost columns[​](#cost-columns "Direct link to Cost columns")

All cost columns carry the dollar value of the consumed units for the line item, based on your account's per-unit pricing. In this version, the four FOCUS cost columns hold the same value — Coralogix does not model separate list, contracted, and effective rates.

| Column                | Description                                                                               |
| --------------------- | ----------------------------------------------------------------------------------------- |
| `BilledCost`          | Cost of the line item's usage.                                                            |
| `EffectiveCost`       | Amortized cost after applicable discounts. Same value as `BilledCost`.                    |
| `ContractedCost`      | Cost at your contracted unit price. Same value as `BilledCost`.                           |
| `ListCost`            | Cost at list unit price. Same value as `BilledCost`.                                      |
| `BillingCurrency`     | Currency of the cost columns. Always `USD`.                                               |
| `ChargeCategory`      | Nature of the charge. Always `Usage`.                                                     |
| `ChargeClass`         | Set only when a row corrects a previously invoiced amount. Empty for standard usage rows. |
| `ChargeFrequency`     | How often the charge recurs. Always `Usage-Based`.                                        |
| `ChargeDescription`   | Human-readable summary of the line item, combining the feature and its TCO priority.      |
| `InvoiceIssuerName`   | Entity that issues the invoice. Always `Coralogix Ltd`.                                   |
| `ServiceProviderName` | Provider of the service. Always `Coralogix`.                                              |

## Usage and pricing columns[​](#usage-and-pricing-columns "Direct link to Usage and pricing columns")

| Column             | Description                                                                                    |
| ------------------ | ---------------------------------------------------------------------------------------------- |
| `PricingQuantity`  | Number of CX Units consumed by the line item. The cost columns are derived from this quantity. |
| `PricingUnit`      | Unit that pricing is measured in. Always `CX Units`.                                           |
| `ConsumedQuantity` | Raw volume consumed, in the line item's native unit.                                           |
| `ConsumedUnit`     | Native unit for `ConsumedQuantity`. See the mapping below.                                     |

`ConsumedUnit` reflects how each kind of usage is measured natively, before conversion to CX Units:

| Usage kind     | `ConsumedUnit` |
| -------------- | -------------- |
| Processed data | Bytes          |
| Egress data    | Bytes          |
| Metric samples | Samples        |
| Events         | Events         |
| AI evaluations | Tokens         |
| AI tokens      | Tokens         |

## Time period columns[​](#time-period-columns "Direct link to Time period columns")

| Column               | Description                                                                                                    |
| -------------------- | -------------------------------------------------------------------------------------------------------------- |
| `ChargePeriodStart`  | Start of the usage day. Inclusive.                                                                             |
| `ChargePeriodEnd`    | End of the usage day. Exclusive.                                                                               |
| `BillingPeriodStart` | Start of the billing period the row falls in. Inclusive. Reflects the start date you requested for the export. |
| `BillingPeriodEnd`   | End of the billing period. Exclusive. Reflects the end date you requested for the export.                      |

## Account columns[​](#account-columns "Direct link to Account columns")

| Column               | Description                                                                                      |
| -------------------- | ------------------------------------------------------------------------------------------------ |
| `BillingAccountId`   | Your Coralogix organization ID — the top-level billing entity that teams roll up to.             |
| `BillingAccountName` | Name of the organization.                                                                        |
| `SubAccountId`       | Identifier of the team that generated the usage. Teams are sub-accounts within the organization. |
| `SubAccountName`     | Name of the team.                                                                                |
| `SubAccountType`     | Type of sub-account. Always `Team`.                                                              |

`BillingAccountId` identifies the organization; `SubAccountId` identifies the team within it. The extension column `x_cx_organization_id` (see below) carries the same organization identifier for tools that need it as an explicit field — it is empty when the team is not attached to an organization.

## Service classification columns[​](#service-classification-columns "Direct link to Service classification columns")

Coralogix maps each feature group to the FOCUS service taxonomy so your usage lines up with the service categories your FinOps tool expects.

| Column               | Description                                                                             |
| -------------------- | --------------------------------------------------------------------------------------- |
| `ServiceName`        | Coralogix service that produced the usage — for example, `Logs`, `Metrics`, or `Spans`. |
| `ServiceCategory`    | FOCUS service category for the service.                                                 |
| `ServiceSubcategory` | FOCUS service subcategory for the service.                                              |

The mapping Coralogix applies:

| `ServiceName`    | `ServiceCategory`         | `ServiceSubcategory` |
| ---------------- | ------------------------- | -------------------- |
| Logs             | Management and Governance | Observability        |
| Metrics          | Management and Governance | Observability        |
| Spans            | Management and Governance | Observability        |
| Infra Monitoring | Management and Governance | Observability        |
| Alerts           | Management and Governance | Observability        |
| RUM              | Management and Governance | Observability        |
| Profiles         | Management and Governance | Observability        |
| Notifications    | Management and Governance | Observability        |
| Cases            | Management and Governance | Support              |
| AAA              | Security                  | Other (Security)     |
| Data Plans       | Management and Governance | Cost Management      |
| Data Engine      | Analytics                 | Data Processing      |
| Data             | Analytics                 | Data Processing      |
| AI               | AI and Machine Learning   | Generative AI        |

## Region columns[​](#region-columns "Direct link to Region columns")

These columns describe where your Coralogix account is hosted.

| Column             | Description                                                                                             |
| ------------------ | ------------------------------------------------------------------------------------------------------- |
| `RegionId`         | Cloud provider region code for your account's host region — for example, `eu-north-1` or `us-central1`. |
| `RegionName`       | Human-readable region name — for example, `Europe (Stockholm)`.                                         |
| `HostProviderName` | Cloud provider that hosts the region: `Amazon Web Services` or `Google Cloud Platform`.                 |

## Tags and Coralogix extensions[​](#tags-and-coralogix-extensions "Direct link to Tags and Coralogix extensions")

`Tags` is a JSON object of key-value pairs that describe the line item. Coralogix-defined keys use the `cx:` prefix required by the FOCUS specification for vendor-defined tags:

| Tag key               | Description                                 |
| --------------------- | ------------------------------------------- |
| `cx:pillar`           | Observability pillar the usage belongs to.  |
| `cx:entity_type`      | Entity type the usage was recorded against. |
| `cx:measurement_kind` | Kind of measurement the usage represents.   |

The export also includes Coralogix-specific columns, prefixed with `x_cx_`, that carry detail beyond the FOCUS specification:

| Column                   | Description                                                                                                                |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------- |
| `x_cx_cluster`           | Coralogix cluster code for your account — for example, `EU1`, `US1`, or `AP2`.                                             |
| `x_cx_completeness`      | Whether the day was fully aggregated when the export ran: `complete` or `partial`. A row for the current day is `partial`. |
| `x_cx_organization_id`   | Organization the team belongs to. Empty when the team is not attached to an organization.                                  |
| `x_cx_organization_name` | Name of the organization. Empty when the team is not attached to an organization.                                          |
| `x_cx_tco_priority`      | Normalized TCO priority of the usage.                                                                                      |

## Limitations[​](#limitations "Direct link to Limitations")

* **Single region per export.** Each export covers one Coralogix host region. To assemble a global view, export from each region and federate the files in your FinOps tool.
* **US dollars only.** Cost columns are always denominated in `USD`.
* **Daily granularity.** Usage is aggregated per day; the export does not break usage down to sub-day intervals.
* **Date range up to 365 days.** The requested range must be between 1 and 365 days, and the start date must be on or before the end date.
* **Billing period follows the requested range.** `BillingPeriodStart` and `BillingPeriodEnd` reflect the dates you request for the export, not a fixed invoice cycle.
* **No resource columns.** The export omits `ResourceId` and `ResourceName`, because Coralogix bills on consumption rather than provisioned resources.

## Related resources[​](#related-resources "Direct link to Related resources")

* [Data usage](https://coralogix.com/docs/user-guides/account-management/payment-and-billing/data-usage.md) — monitor usage and generate reports, including the Focus report.
* [Quota Rules](https://coralogix.com/docs/user-guides/account-management/payment-and-billing/quota-rules.md) — set the daily unit quota that usage is measured against.
* [Data Usage Service API](https://coralogix.com/docs/developer-portal/apis/data-management/data-usage-service-api.md) — generate reports programmatically.