Skip to content

Common Job spec reporting schema - #432

Draft
skudasov wants to merge 4 commits into
mainfrom
RANE-4655-common-job-spec-metrics
Draft

Common Job spec reporting schema#432
skudasov wants to merge 4 commits into
mainfrom
RANE-4655-common-job-spec-metrics

Conversation

@skudasov

Copy link
Copy Markdown
Contributor

No description provided.

@changeset-bot

changeset-bot Bot commented Jul 24, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 76d3813

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

github-actions Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

The latest Buf updates on your PR. Results from workflow Regenerate Protobuf Files / buf (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed⏩ skippedSep 4, 2026, 2:56 PM

gheorghestrimtu added a commit to smartcontractkit/chainlink that referenced this pull request Sep 4, 2026
… reporter

Fold core/services/cljobinfo into the existing nodestatusreporter/jobspec
service instead of adding a parallel reporter. CLJobInfo is now emitted for
every job regardless of type, alongside the unchanged OCR2-only JobSpecEvent
track. application.go and the [JobSpecReporter] config are unchanged.

Requires: smartcontractkit/chainlink-protos#432
RANE-4655
Add optional Job Distributor provenance to common.v1.CLJobInfo:
feeds_manager_id (50), remote_uuid (51), spec_version (52), proposed_at (53)
and approved_at (54). They are unset for jobs that did not arrive as an
approved job proposal, which is how a consumer distinguishes a JD-managed job
from one created directly via CLI, UI or TOML on disk. remote_uuid is the join
key back to api.job.v1.Job.uuid.

Document why no JD message is reused for the spec itself: neither
cfm.ProposeJobRequest nor api.job.v1.Proposal models a job's contents, both
carry the TOML document as an opaque string alongside identity metadata, so
spec_toml follows JD's own representation rather than inventing a new one.

Also add the changeset this PR was missing, covering the CLJobInfo addition as
a whole.

RANE-4655

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants