Skip to content

[PENDING] refactor(graphrunner): route metrics through observability/metrics#198

Open
xytan0056 wants to merge 1 commit into
pr4-contextfrom
pr7-graphrunner
Open

[PENDING] refactor(graphrunner): route metrics through observability/metrics#198
xytan0056 wants to merge 1 commit into
pr4-contextfrom
pr7-graphrunner

Conversation

@xytan0056

@xytan0056 xytan0056 commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Routes the native graphrunner's metrics through observability/metrics.

  • The graphrunner reads the request emitter from ctx via metrics.FromContext (the orchestrator forwards the same ctx the controller seeds), so it no longer takes a tally.Scope at construction.
  • Substep timers (bazel_query_duration, git_file_hashes_duration, target_hash_duration) and the target-count gauge move to shared metric-name constants under the graph_runner op sub-scope. target_counttargets_count, still a gauge to preserve the time-series shape.
  • The orchestrator stops threading its scope into the runner; it keeps that scope for its own (not-yet-migrated) metrics until the stacked orchestrator PR.

stacking

  1. feat(observability/metrics): add context propagation #184

The graphrunner reads the request emitter from ctx via metrics.FromContext
instead of taking a tally.Scope at construction. The substep timers
(bazel_query_duration, git_file_hashes_duration, target_hash_duration) and
the target-count gauge move to the shared metric-name constants under the
graph_runner op sub-scope. target_count becomes targets_count but stays a
gauge to preserve the time-series shape.

The orchestrator stops threading its scope into the runner; it still uses
that scope for its own (not-yet-migrated) metrics until the next commit.
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.

1 participant