Billing: emit compute usage MeterRecord per execution by DylanTinianov · Pull Request #23858 · smartcontractkit/chainlink

DylanTinianov · 2026-09-29T18:06:03Z

What

When [Metering].MeterRecordsEnabled is on, the syncer passes the metering identity to every v2 engine, and each engine owns its ResourceManager. After each execution baseEngine.emitComputeUsage emits one METER_ACTION_USAGE record:

Field	Value
resource type	`cre:workflow:compute`, value in ms
`ResourceId`	`<workflow_id>:<execution_id>`
`EventId`	execution id (one compute record per execution, identical on every node; billing builds `cre:workflow:<wf>:<exec>:<exec>`)
`Identity.Service` / `Don.DonId`	`workflow-engine` / local node's workflow DON
`Identity.ResourcePool` / `ResourcePoolId`	`cre:workflow:compute` / `cre:workflow:compute`
`OrgId`	engine's resolved org id

Testing

Verified on Staging compute + gas records are emitted and accepted by ChIP.

github-actions · 2026-09-29T18:06:49Z

✅ No conflicts with other open PRs targeting develop

trunk-io · 2026-09-29T18:35:56Z

_{View Full Report ↗︎ ⋅ Docs}

Copilot

Copilot review overview

🟡 Changes recommended

Failed emissions are logged as successful, and disabled metering leaks confidential execution marks.

Review effort: Balanced
Findings: 1

Open (1)

Consume confidential marks when usage metering is disabled · New

What changed in this PR

Risk Rating: MEDIUM

Adds per-execution compute usage metering for workflow v2 engines, including confidential-execution exclusion and billing reconciliation logs.

Changes:

Wires capability usage metering into workflow engines.
Emits compute usage for successful and failed executions.
Tracks confidential executions to avoid duplicate billing.

Scrupulous human review: ResourceManager failure reporting and confidential tracking lifecycle.

File	Description
`core/services/workflows/v2/config.go`	Adds usage metering configuration.
`core/services/workflows/v2/confidential_module.go`	Tracks confidential executions.
`core/services/workflows/v2/compute_usage_test.go`	Tests compute usage emission.
`core/services/workflows/v2/base_engine.go`	Emits compute usage records.
`core/services/workflows/syncer/v2/handler.go`	Wires and manages the usage meter.
`core/services/cre/cre.go`	Creates the feature-gated ResourceManager.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

…on (CRE-6779) When [Metering].CapabilityUsageEnabled is set, the syncer builds a ResourceManager and every v2 engine emits one METER_ACTION_USAGE record per execution after computeDuration is known: - resource type cre:workflow:compute, value in milliseconds - Utilization.ResourceId "<workflow_id>:<execution_id>", EventId = execution id (identical on every node; billing derives cre:workflow:<wf>:<exec>:<exec>) - Identity.Service workflow-engine, DON id from the local node, org from the engine's resolved org id Emitted for successful and failed executions, outside the legacy metering block so a legacy metering failure cannot suppress it, and skipped when the execution was delegated to the confidential module (ConfidentialModule now tracks the executions it handled; the enclave path meters those). Each emission logs "Emitted capability usage meter record" with executionID, eventID, resourceType, value and orgID. That line is a contract for the billing reconciler and is covered by a unit test. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…ntract Identity.ResourcePool and ResourcePoolID are now "cre:workflow:compute", derived via resourcemanager.WithWorkflowUsagePool, matching the Billing <-> Decentralized stack contract. Bumps chainlink-common. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

… CapabilityUsageEnabled chainlink-common #2428 dropped the separate CapabilityUsageEnabled flag per review: capability usage records share the existing [Metering].MeterRecordsEnabled gate with durable resource metering. The syncer now builds the compute usage ResourceManager when MeterRecordsEnabled is set, next to the spec meter. Bumps chainlink-common to 16997122620e in all modules: CRE-6781-emit-usage-value merged with develop's current pin 8fdc7816. Re-bump to main once #2428 and the develop bump #23910 land. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…ink-common to ae91aba3 (#2457, confidential execution duration) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…nsume confidential mark unconditionally, paralleltest/gci Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>