feat(system-metrics): cpu usage #24
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Introduce a new system metrics module to periodically record CPU utilization and wire it into Observability; update instrumentation/exporters and headers accordingly.
System
andSystemLive
targets with CPU monitoring:CPUStatistics
,SystemInfo
,CPULoad
,Scheduler
, and live facade to periodically recordsystem.cpu.utilization
withcpu.logical_number
andcpu.mode
attributes.ObservabilityClient
buildsSystemInfo
and starts monitoring on init; falls back toSystemInfo.noOp
on failure.LDSemanticAttribute.System
keys.Instrumentation.noOp
a static value; use non-optionalotelTracer
and simplify span building..init(config: .init(headers: ...))
; update Meter provider views and merge resource attributes into gauge metrics.highlight.project_id
is present incustomHeaders
during registration; enrich resource attributes with SDK version/project id.System
,SystemLive
) intoObservability
target andPackage.swift
.serviceName
in Example app options.Written by Cursor Bugbot for commit bf4fcb4. This will update automatically on new commits. Configure here.