Add process cpu count metric

open-telemetry · Mar 1, 2022 · 9060c4b · 9060c4b
1 parent 82deda1
commit 9060c4b
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 0 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -31,6 +31,9 @@ release.
 
 ### Semantic Conventions
 
+- Add `process.cpu.count` metric.
+  ([#9999](https://github.com/open-telemetry/opentelemetry-specification/pull/9999))
+
 ### Compatibility
 
 ### OpenTelemetry Protocol

diff --git a/specification/metrics/semantic_conventions/process-metrics.md b/specification/metrics/semantic_conventions/process-metrics.md
@@ -30,6 +30,7 @@ Below is a table of Process metric instruments.
 | Name | Instrument | Units | Description | Labels |
 |------|------------|-------|-------------|--------|
 | `process.cpu.time` | Asynchronous Counter | s | Total CPU seconds broken down by different states. | `state`, if specified, SHOULD be one of: `system`, `user`, `wait`. A process SHOULD be characterized _either_ by data points with no `state` labels, _or only_ data points with `state` labels. |
+| `process.cpu.count` | Asynchronous UpDownCounter | 1 | The number of CPUs available to the process. |  |
 | `process.memory.usage` | Asynchronous UpDownCounter | By | The amount of physical memory in use. |  |
 | `process.memory.virtual` | Asynchronous UpDownCounter | By | The amount of committed virtual memory. |  |
 | `process.disk.io` | Asynchronous Counter | By | Disk bytes transferred. | `direction` SHOULD be one of: `read`, `write` |