Repository navigation
Billing: Config [Metering].CapabilityUsageEnabled flag - #23856
Closed
DylanTinianov wants to merge 3 commits into
Closed
DylanTinianov wants to merge 3 commits into
DylanTinianov wants to merge 3 commits into
Conversation
product-security-plaid-production
Bot
requested review from
Tofel,
kalverra and
vyzaldysanchez
September 29, 2026 17:59
…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>
DylanTinianov
force-pushed
the
CRE-6779-compute-usage-records
branch
from
October 6, 2026 17:56
6527b3a to
b11eb78
Compare
Contributor
|
I see you updated files related to
|
Contributor
Author
Contributor
|
✅ No conflicts with other open PRs targeting |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
… MeterRecords
Per-capability workflow billing (CRE-6778) adds METER_ACTION_USAGE records for
compute duration and gas at every capability that bills a workflow execution.
This setting is the single switch for all of those emission points, default
false, so DONs can be moved to the new records one at a time and rolled back
without a redeploy of the emitters.
It is independent of MeterRecordsEnabled, which gates durable resource metering
(active workflow specs) and must not be coupled to this rollout. Passed to LOOP
capability plugins as CL_CAPABILITY_USAGE_ENABLED.