feat(metrics): Migrate from OpenCensus to OpenTelemetry #9043

khrm · 2025-09-29T10:32:21Z

Changes

Updated pipelinerunmetrics and taskrunmetrics to use OpenTelemetry instruments (histograms, counters, gauges) for creating and recording metrics.
Introduced new OpenTelemetry configurations in config/config-observability.yaml for exporters and protocols..
Rewrote the test suites for pipelinerunmetrics and taskrunmetrics to be compatible with the new OpenTelemetry-based implementation.
Updated knative to 1.19

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
Has Tests included if any functionality added or changed
pre-commit Passed
Follows the commit message standard
Meets the Tekton contributor standards (including functionality, content, code)
Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Breaking Changes in metrics

  1. Infrastructure Metric Renaming
  Infrastructure metrics (Go runtime, Workqueue, K8s Client) have been renamed from the tekton_pipelines_controller_ prefix to standard OpenTelemetry/Knative namespaces.


  ┌────────────┬─────────────────────────────────────────────────────────┬─────────────────────────────────────────┬──────────────────────────────────┐
  │ Category   │ Old Metric Name (OpenCensus)                            │ New Metric Name (OpenTelemetry)         │ Changes                          │
  ├────────────┼─────────────────────────────────────────────────────────┼─────────────────────────────────────────┼──────────────────────────────────┤
  │ Workqueue  │ tekton_pipelines_controller_workqueue_adds_total            │ kn_workqueue_adds_total                   │ Prefix change                    │
  │            │ tekton_pipelines_controller_workqueue_depth                 │ kn_workqueue_depth                        │ Prefix change                    │
  │            │ tekton_pipelines_controller_workqueue_queue_latency_seconds   │ kn_workqueue_queue_duration_seconds         │ Renamed latency -> duration      │
  │            │ tekton_pipelines_controller_workqueue_work_duration_seconds   │ kn_workqueue_process_duration_seconds       │ Renamed work -> process          │
  │            │ tekton_pipelines_controller_workqueue_retries_total         │ kn_workqueue_retries_total                │ Prefix change                    │
  │            │ tekton_pipelines_controller_workqueue_unfinished_work_seconds │ kn_workqueue_unfinished_work_seconds        │ Prefix change                    │
  │ K8s Client │ tekton_pipelines_controller_client_latency                  │ http_client_request_duration_seconds        │ Standard HTTP metric             │
  │            │ tekton_pipelines_controller_client_results                  │ kn_k8s_client_http_response_status_code_total │ Detailed status tracking         │
  │ Go Runtime │ tekton_pipelines_controller_go_*                            │ go_* (e.g. go_goroutines)                 │ Standard Prometheus Go collector │
  └────────────┴─────────────────────────────────────────────────────────┴─────────────────────────────────────────┴──────────────────────────────────┘


  2. Label Changes in Tekton Metrics
  While the core metric names for PipelineRuns and TaskRuns have been preserved, some labels have changed to provide more detail or align with OTel standards.

   * `tekton_pipelines_controller_pipelinerun_duration_seconds`:
       * Added: reason label (e.g., Completed, Succeeded). This allows for more granular breakdown of durations but increases cardinality.
   * `tekton_pipelines_controller_pipelinerun_taskrun_duration_seconds`:
       * Added: reason label.

  3. Removed Metrics
   * `tekton_pipelines_controller_reconcile_count` and `tekton_pipelines_controller_reconcile_latency`: These custom reconcile metrics are no longer emitted. Users should rely on
     kn_workqueue_process_duration_seconds and kn_workqueue_adds_total to monitor controller performance.

  What Remained Compatible
  The following critical metrics have been explicitly preserved to minimize disruption:
   * TaskRun Pod Latency: tekton_pipelines_controller_taskruns_pod_latency_milliseconds remains a Gauge (preserving behavior despite OTel defaults preferring Histograms).
   * Total Counters: tekton_pipelines_controller_pipelinerun_total and tekton_pipelines_controller_taskrun_total retain their original labels (status) and do not include the high-cardinality
     reason label.
   * Bucket Boundaries: Duration histograms (e.g., taskrun_duration_seconds) retain their specific explicit buckets (10s, 30s, 1m, etc.) instead of defaulting to OTel's millisecond-focused
     buckets.

 Upgrade Actions
   1. Update Config: Ensure your config-observability ConfigMap uses metrics-protocol: prometheus (or grpc/http) instead of the old metrics.backend-destination. If prometheus was being used, then no need to do any changes.
   2. Update Dashboards:
       * Replace tekton_pipelines_controller_workqueue_* queries with kn_workqueue_*.
       * Replace tekton_pipelines_controller_go_* queries with standard go_* metrics.
       * Check aggregations on pipelinerun_duration_seconds to account for the new reason label (use sum by (label) if necessary to aggregate away the new dimension).

/kind feature

tekton-robot · 2025-09-29T10:45:22Z

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/pipelinerunmetrics/metrics.go	86.7%	68.8%	-17.9
pkg/reconciler/pipelinerun/pipelinerun.go	91.6%	91.6%	-0.0
pkg/taskrunmetrics/metrics.go	87.3%	72.8%	-14.5

tekton-robot · 2025-09-29T11:06:05Z

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/pipelinerunmetrics/metrics.go	86.7%	68.8%	-17.9
pkg/reconciler/pipelinerun/pipelinerun.go	91.6%	91.6%	-0.0
pkg/taskrunmetrics/metrics.go	87.3%	72.8%	-14.5

tekton-robot · 2025-09-29T11:08:55Z

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/pipelinerunmetrics/metrics.go	86.7%	68.8%	-17.9
pkg/reconciler/pipelinerun/pipelinerun.go	91.6%	91.6%	-0.0
pkg/taskrunmetrics/metrics.go	87.3%	72.8%	-14.5

waveywaves · 2025-09-29T12:25:30Z

/retest

tekton-robot · 2025-09-29T13:05:03Z

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/pipelinerunmetrics/metrics.go	86.7%	68.8%	-17.9
pkg/reconciler/pipelinerun/pipelinerun.go	91.6%	91.6%	-0.0
pkg/taskrunmetrics/metrics.go	87.3%	72.8%	-14.5

waveywaves · 2025-09-29T19:12:54Z

/retest

enarha · 2025-12-15T12:28:39Z

Re knative bump, we discussed multiple times that we want knative/pkg@04fdd0b included in the next bump, even though it only exists in main for now (not even in 1.20). It'll unlock the better finalizer management which proved to be an issue for Tekton deployments with multiple controllers managing the same PR/TR resources. So do we want to bump knative/pkg even higher?

khrm · 2025-12-16T02:57:01Z

/assign @vdemeester @waveywaves

khrm · 2025-12-16T02:57:18Z

@enarha I have updated to latest knative/pkg for now.

khrm · 2025-12-16T02:59:00Z

Why are ci tests being skipped?

khrm · 2025-12-16T03:07:34Z

/kind feature

khrm · 2026-01-12T10:44:25Z

Could you check the metric related to throttled task runs. The values are accumulating in every loop increasing indefinitely instead of capturing the correct current value.

@anithapriyanatarajan Can you recheck this?

anithapriyanatarajan

some tests in test/ folder are still using opencensus. Could you assess that and remove opencensus from go.mod.

anithapriyanatarajan · 2026-01-12T18:17:06Z

cmd/webhook/main.go

 	}

-	var statsReporterOptions []webhook.StatsReporterOption
-	enableNamespace := os.Getenv("WEBHOOK_METRICS_ENABLE_NAMESPACE")


@khrm - Is this a breaking change for users?

anithapriyanatarajan · 2026-01-12T18:27:30Z

pkg/pipelinerunmetrics/metrics.go

The following knative metrics - reconcile_count and reconcile_latency are missing . Could be that knative has deprecated those or are there other equivalents?

tekton_pipelines_controller_reconcile_count (counter) - Number of reconcile operations | reconciler|success|namespace_name
tekton_pipelines_controller_reconcile_latency | histogram | Latency of reconcile operations

anithapriyanatarajan · 2026-01-12T18:32:49Z

go.mod

 	github.com/spiffe/go-spiffe/v2 v2.6.0
 	github.com/spiffe/spire-api-sdk v1.14.0
 	github.com/tektoncd/plumbing v0.0.0-20220817140952-3da8ce01aeeb
 	go.opencensus.io v0.24.0


@khrm Why do we still require opencensus?

It is being used for tracing.

pkg/taskrunmetrics/metrics.go

khrm · 2026-01-14T06:36:54Z

#9043 (comment)

The following knative metrics - reconcile_count and reconcile_latency are missing . Could be that knative has deprecated those or are there other equivalents?

tekton_pipelines_controller_reconcile_count (counter) - Number of reconcile operations | reconciler|success|namespace_name
tekton_pipelines_controller_reconcile_latency | histogram | Latency of reconcile operations

Yes, there's an equivalent - kn.workqueue.work_duration_count must be there.

test/util.go

config/resolvers/config-observability.yaml

aThorp96

Still reviewing but I've left some notes and questions

aThorp96 · 2026-01-14T20:57:58Z

config/config-observability.yaml

    app.kubernetes.io/instance: default
    app.kubernetes.io/part-of: tekton-pipelines
 data:
+  metrics-protocol: prometheus


Is this intentionally included in the configmap since it's already the default?

Yes, it's intentionally introduced in configmap. Default is none which causes no metrics to be emitted but earlier were emitting prometheus metrics by default.

aThorp96 · 2026-01-14T21:18:16Z

config/config-observability.yaml

+    # OpenTelemetry Metrics Configuration
+    # Protocol for metrics export (prometheus, grpc, http/protobuf, none)
+    # Default: prometheus
+    metrics-protocol: prometheus


These new settings all use metrics-* or tracing-* whereas settings previously were metrics.*. Is there any reason for the naming convention change? The unchanged settings are still metrics.* so if possible we should keep the naming consistent

Yes, these changes are due to OTEL migration.

Other metrics configurations are related to Tekton, so I am not sure whether there's any benefit to making breaking changes. Users don't need to make any changes if they were already using Prometheus.

Yes, these changes are due to OTEL migration.

I assume that means OTEL consumes these directly so we can't control their names, which makes sense. Would you be opposed to linking to the OTEL docs in the comments of this section of settings? That should help with both documentation and delineating what settings we "own" and what are inherited.

Other metrics configurations are related to Tekton, so I am not sure whether there's any benefit to making breaking changes.

I agree, makes sense.

Users don't need to make any changes if they were already using Prometheus.

Makes sense. That does make me realize that we currently document stackdriver support. I've never used stackdriver and am not familiar with it, but for users currently using stackdriver what does their migration path look like?

This upgrades knative to latest and other dependent dependencies.

Replaces the legacy knative.dev/pkg/metrics dependency with knative.dev/pkg/observability/configmap to align with the OpenTelemetry migration and ensure correct configuration loading.

This isn't supported after knative otel's migration.

The knativetest.Flags.EmitMetrics flag is no longer supported after the migration to OpenTelemetry. This commit removes the conditional initialisation to align with the new metrics system.

Run hack/update-codegen.sh to update generated client code, deepcopy functions, and CRD manifests. This aligns the generated code with recent dependency updates, including changes to finalizer management and context usage in informers.

Update the expected checksums in Pipeline and Task unit tests to match the new values generated after the knative update: - pkg/apis/pipeline/v1 - pkg/apis/pipeline/v1beta1

khrm · 2026-01-15T12:51:50Z

some tests in test/ folder are still using opencensus. Could you assess that and remove opencensus from go.mod.

This can be covered in separate PR. It's related to tracing. We need to migrate to knative based otel tracing.
@waveywaves @vdemeester

aThorp96 · 2026-01-15T13:12:21Z

config/config-observability.yaml

-    metrics.allow-stackdriver-custom-metrics: "false"
+    # OpenTelemetry Metrics Configuration
+    # Protocol for metrics export (prometheus, grpc, http/protobuf, none)
+    # Default: prometheus


Since we have to specify "prometheus" to make it "default" in our deployment, I think this comment needs to be clarified:

Suggested change

# Default: prometheus

# Default if not specified: "none"

Also: When you say (prometheus, grpc, http/protobuf, none), are the supported values ["prometheus", "grpc", "http/protobuf", "none"] or are the supported values ["prometheus", "grpc", "http/protobuf", ""] ? If "none" is "", then my above suggestion would become

Suggested change

# Default: prometheus

# Default if not specified: "" (none)

It's "none".

This commit migrates the metrics for PipelineRuns and TaskRuns from OpenCensus to OpenTelemetry. The following changes are included: - Updated the observability config to support OpenTelemetry. - Migrated the implementation of PipelineRun and TaskRun metrics to use the OpenTelemetry Go SDK. - Updated the tests to work with the new OpenTelemetry-based implementation.

vdemeester

Thanks for this major migration effort! I've reviewed the metrics implementation and OpenCensus cleanup. The OpenTelemetry migration looks solid overall, but there are some remaining OpenCensus references that need to be addressed before merge.

Summary

Metrics Implementation ✅

The core metrics migration to OpenTelemetry is well-executed:

✅ Proper use of OTel instruments (Histograms, Counters, ObservableGauges)
✅ Backward-compatible metric names preserved
✅ Good thread safety with mutex usage
✅ Observable gauge callbacks implemented correctly

OpenCensus Cleanup ❌

Blocker: OpenCensus is still present in test files and go.mod

Critical Question ⚠️

@anithapriyanatarajan raised a concern on Jan 6 about throttled metrics accumulating instead of showing current values. Looking at the current code (lines 346-380 in pkg/taskrunmetrics/metrics.go), the implementation creates fresh maps on each observation, which should be correct. Has this issue been resolved? If so, it would be helpful to document what was fixed.

Required Changes

1. Remove OpenCensus from test files (Blocker)

The following test files still import and use OpenCensus for tracing:

test/custom_task_test.go line 37:

import "go.opencensus.io/trace"

Used on line 257 and throughout for test span tracking.

test/wait.go line 6:
Same import, used in lines 90, 117, 135, 153, 179, 209 for various wait function spans.

Action Required:
Migrate to OpenTelemetry tracing API:

// OLD (OpenCensus):
import "go.opencensus.io/trace"
_, span := trace.StartSpan(ctx, metricName)
defer span.End()

// NEW (OpenTelemetry):
import "go.opentelemetry.io/otel"
tracer := otel.Tracer("tekton-e2e-tests")
ctx, span := tracer.Start(ctx, metricName)
defer span.End()

2. Clean up go.mod

After migrating the test files, remove the OpenCensus dependency:

go.opencensus.io v0.24.0

Steps:

Migrate test/custom_task_test.go and test/wait.go to OTel
Run go mod tidy
Run ./hack/update-deps.sh to update vendor/
Verify go.opencensus.io is completely removed

Note: If it comes back as an indirect dependency, we'll need to track down which dependency is still pulling it in.

3. Throttled Metrics Question

In pkg/taskrunmetrics/metrics.go lines 346-380, the throttled metrics implementation looks correct to me:

trsThrottledByQuota and trsThrottledByNode are local maps created fresh on each callback
They are populated by iterating current TaskRuns
They are reported once per observation

This should give the current count, not accumulate. Can you confirm:

Was the accumulation bug fixed in a recent commit?
Is the current behavior correct now?

Overall Assessment

The metrics migration is well-implemented. Once the OpenCensus cleanup is complete and the throttled metrics question is clarified, this should be good to merge.

vdemeester

Adding inline comments on the specific files modified in this PR (following up on my previous review).

vdemeester · 2026-01-15T16:06:14Z

pkg/taskrunmetrics/metrics.go

-	"github.com/tektoncd/pipeline/pkg/apis/pipeline"
+	pipeline "github.com/tektoncd/pipeline/pkg/apis/pipeline"
 	v1 "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1"
 	listers "github.com/tektoncd/pipeline/pkg/client/listers/pipeline/v1"


✅ Great OTel Migration

The migration from OpenCensus to OpenTelemetry looks excellent here:

Before (OpenCensus):

"go.opencensus.io/stats" "go.opencensus.io/stats/view" "go.opencensus.io/tag"

After (OpenTelemetry):

"go.opentelemetry.io/otel" "go.opentelemetry.io/otel/attribute" "go.opentelemetry.io/otel/metric"

This is the right approach.

vdemeester · 2026-01-15T16:06:14Z

test/util.go

 		flag.Parse()
 		flag.Set("alsologtostderr", "true")
 		logging.InitializeLogger()
-


OpenCensus Metric Exporter Removed

Good - removed the old OpenCensus metric exporter initialization.

However, test/custom_task_test.go and test/wait.go still import OpenCensus for tracing (not metrics):

import "go.opencensus.io/trace"

These files are NOT modified in this PR but still use OpenCensus. They need to be migrated to OpenTelemetry tracing in a follow-up or this PR:

// Replace with: import "go.opentelemetry.io/otel" tracer := otel.Tracer("tekton-e2e-tests") ctx, span := tracer.Start(ctx, metricName) defer span.End()

vdemeester · 2026-01-15T16:06:14Z

go.mod

 	github.com/pkg/errors v0.9.1
 	github.com/sigstore/sigstore v1.9.5
 	github.com/spiffe/go-spiffe/v2 v2.6.0
 	github.com/spiffe/spire-api-sdk v1.14.0


OpenCensus Dependency Still Present

After the OpenTelemetry migration, this should be removed:

go.opencensus.io v0.24.0

Why it's still here:
The test files test/custom_task_test.go and test/wait.go still use OpenCensus for tracing (see my comment on test/util.go).

To remove:

Migrate those test files to OTel tracing

Run go mod tidy

Run ./hack/update-deps.sh to update vendor/

Verify go.opencensus.io is gone (or only present as indirect dependency)

github-project-automation bot moved this to Todo in Tekton Community Roadmap Sep 29, 2025

github-project-automation bot added this to Tekton Community Roadmap Sep 29, 2025

tekton-robot added kind/feature Categorizes issue or PR as related to a new feature. release-note-none Denotes a PR that doesnt merit a release note. labels Sep 29, 2025

tekton-robot requested review from jerop and pritidesai September 29, 2025 10:32

tekton-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Sep 29, 2025

khrm force-pushed the mig-otel branch 2 times, most recently from bab5a44 to a2ea129 Compare September 29, 2025 10:53

waveywaves mentioned this pull request Sep 29, 2025

WIP: Migration from OpenCensus to OTEL and Knative Bump #8933

Closed

8 tasks

waveywaves self-assigned this Sep 29, 2025

khrm force-pushed the mig-otel branch from a2ea129 to 4b5feb5 Compare September 29, 2025 12:53

vdemeester added this to the v1.7.0 milestone Oct 1, 2025

tekton-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 24, 2025

vdemeester modified the milestones: v1.7.0, v1.8.0 Dec 3, 2025

khrm force-pushed the mig-otel branch from 4b5feb5 to d7f44a8 Compare December 16, 2025 02:56

tekton-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 16, 2025

tekton-robot assigned vdemeester Dec 16, 2025

khrm force-pushed the mig-otel branch from e8431e5 to addca4b Compare January 12, 2026 10:12

tekton-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 12, 2026

khrm force-pushed the mig-otel branch from addca4b to f642630 Compare January 12, 2026 10:16

khrm force-pushed the mig-otel branch from f642630 to 726a0e5 Compare January 12, 2026 13:18

anithapriyanatarajan reviewed Jan 12, 2026

View reviewed changes

infernus01 reviewed Jan 13, 2026

View reviewed changes

pkg/taskrunmetrics/metrics.go Show resolved Hide resolved

tekton-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 13, 2026

aThorp96 reviewed Jan 14, 2026

View reviewed changes

test/util.go Show resolved Hide resolved

aThorp96 reviewed Jan 14, 2026

View reviewed changes

config/resolvers/config-observability.yaml Outdated Show resolved Hide resolved

aThorp96 reviewed Jan 14, 2026

View reviewed changes

khrm force-pushed the mig-otel branch from 726a0e5 to de4e6ef Compare January 15, 2026 10:31

tekton-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 15, 2026

khrm added 6 commits January 15, 2026 16:06

Bump Knative/pkg to latest

b517d29

This upgrades knative to latest and other dependent dependencies.

refactor: use observability package for metrics config name

2f11141

Replaces the legacy knative.dev/pkg/metrics dependency with knative.dev/pkg/observability/configmap to align with the OpenTelemetry migration and ensure correct configuration loading.

Remove old metrics code from watcher

948b1e9

This isn't supported after knative otel's migration.

test: Drop OpenCensus based metric exporter initialisation

82992c8

The knativetest.Flags.EmitMetrics flag is no longer supported after the migration to OpenTelemetry. This commit removes the conditional initialisation to align with the new metrics system.

Update generated code and CRDs

c57ea53

Run hack/update-codegen.sh to update generated client code, deepcopy functions, and CRD manifests. This aligns the generated code with recent dependency updates, including changes to finalizer management and context usage in informers.

fix: update unit test checksums

1dd565c

Update the expected checksums in Pipeline and Task unit tests to match the new values generated after the knative update: - pkg/apis/pipeline/v1 - pkg/apis/pipeline/v1beta1

khrm force-pushed the mig-otel branch 3 times, most recently from 492fef8 to bf58998 Compare January 15, 2026 11:52

khrm force-pushed the mig-otel branch from bf58998 to 009a0b4 Compare January 15, 2026 12:54

aThorp96 reviewed Jan 15, 2026

View reviewed changes

khrm force-pushed the mig-otel branch from 009a0b4 to 222f108 Compare January 15, 2026 13:52

vdemeester reviewed Jan 15, 2026

View reviewed changes

feat(metrics): Migrate from OpenCensus to OpenTelemetry #9043

Are you sure you want to change the base?

feat(metrics): Migrate from OpenCensus to OpenTelemetry #9043

Uh oh!

Conversation

khrm commented Sep 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Submitter Checklist

Release Notes

Uh oh!

tekton-robot commented Sep 29, 2025

Uh oh!

tekton-robot commented Sep 29, 2025

Uh oh!

tekton-robot commented Sep 29, 2025

Uh oh!

waveywaves commented Sep 29, 2025

Uh oh!

tekton-robot commented Sep 29, 2025

Uh oh!

waveywaves commented Sep 29, 2025

Uh oh!

enarha commented Dec 15, 2025

Uh oh!

khrm commented Dec 16, 2025

Uh oh!

khrm commented Dec 16, 2025

Uh oh!

khrm commented Dec 16, 2025

Uh oh!

khrm commented Dec 16, 2025

Uh oh!

khrm commented Jan 12, 2026

Uh oh!

anithapriyanatarajan left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

khrm commented Jan 14, 2026

Uh oh!

Uh oh!

Uh oh!

aThorp96 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

khrm Jan 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

khrm commented Jan 15, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vdemeester left a comment

Choose a reason for hiding this comment

Summary

Metrics Implementation ✅

OpenCensus Cleanup ❌

Critical Question ⚠️

Required Changes

1. Remove OpenCensus from test files (Blocker)

khrm commented Sep 29, 2025 •

edited

Loading

khrm Jan 15, 2026 •

edited

Loading