CircleCI’s OpenTelemetry integration now includes resource usage data on task spans, making it easier to understand how your jobs consume compute resources at runtime — not just what was allocated. To surface this data, CircleCI emits a new set of com.circleci.resource.usage.* attributes on task spans for build jobs.
The following attributes are now available when usage data is present:
CPU Usage
Values range from 0.0 to 1.0, representing 100% usage across all cores.
| Attribute | Example | Description |
|---|---|---|
com.circleci.resource.usage.cpu.mean |
0.42 |
Mean CPU usage for the task |
com.circleci.resource.usage.cpu.min |
0.01 |
Lowest CPU usage observed |
com.circleci.resource.usage.cpu.max |
0.98 |
Highest CPU usage observed |
com.circleci.resource.usage.cpu.p90 |
0.98 |
90th percentile of CPU usage |
Memory Usage
Values are in bytes.
| Attribute | Example | Description |
|---|---|---|
com.circleci.resource.usage.memory.mean |
1073741824 |
Mean memory usage |
com.circleci.resource.usage.memory.min |
536870912 |
Lowest memory usage observed |
com.circleci.resource.usage.memory.max |
2147483648 |
Highest memory usage observed |
com.circleci.resource.usage.memory.p90 |
1932735283 |
90th percentile of memory usage |
Network Usage
Only present when the value is greater than zero.
| Attribute | Example | Description |
|---|---|---|
com.circleci.resource.usage.network.bytes_received |
10485760 |
Total bytes received during the task |
com.circleci.resource.usage.network.bytes_sent |
5242880 |
Total bytes sent during the task |
Note: All
com.circleci.resource.usage.*attributes are only available onbuildjobs and only when usage data is collected. They complement the existingcom.circleci.resource.cpuandcom.circleci.resource.ramallocation attributes, enabling you to compare allocated vs. actual resource consumption directly in your OTel-compatible observability tooling.