Skip to content

fix(workflows): cap get-secrets histogram buckets in MetricViews#23030

Draft
pkcll wants to merge 1 commit into
developfrom
platform-engine-get-secrets-metricviews
Draft

fix(workflows): cap get-secrets histogram buckets in MetricViews#23030
pkcll wants to merge 1 commit into
developfrom
platform-engine-get-secrets-metricviews

Conversation

@pkcll

@pkcll pkcll commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Add an OTel SDK view in MetricViews() for platform_engine_get_secrets_duration_ms with 7 explicit boundaries (8 Prometheus buckets including +Inf), down from the OTel default of 16 buckets.
  • Metric owner change in chainlink (option B): view lives next to the other platform_engine_* histogram views wired via shell.gobeholder.Config.MetricViews.
  • Test asserts the view applies via TestMetricViews_getSecretsDurationBuckets.

Motivation

High-cardinality CRE workflow nodes accumulate series from histogram le labels × workflow count. This instrument had no custom view (unlike the other platform_engine histograms in monitoring.go).

Dashboard impact (Medium)

Capabilities dashboard (Capabilities.json, 13 zones) uses:

  • histogram_quantile(0.50, …platform_engine_get_secrets_duration_ms_milliseconds_bucket…)
  • histogram_quantile(0.90, …)

Fewer buckets may shift p50/p90 slightly vs default boundaries. Validate on staging after deploy.

Test plan

  • go test ./core/services/workflows/monitoring/ -run TestMetricViews_getSecretsDurationBuckets
  • Staging: spot-check Capabilities get-secrets p50/p90 panels vs pre-change baseline

Related

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

platform_engine_get_secrets_duration_ms used OTel default 16 buckets;
add an explicit 8-bucket view next to the other platform_engine views.

Co-authored-by: Cursor <cursoragent@cursor.com>
@pkcll pkcll force-pushed the platform-engine-get-secrets-metricviews branch from a7a9347 to e243d4d Compare July 7, 2026 04:10
@cl-sonarqube-production

Copy link
Copy Markdown

@trunk-io

trunk-io Bot commented Jul 7, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic BadgeStatic Badge

Failed Test Failure Summary Logs
TestFunctionsConfigPoller The test 'TestFunctionsConfigPoller' failed to complete successfully. Logs ↗︎
Test_CCIP_TokenTransfer_LnR_without_TransferRef_EVM2Aptos The test failed due to an issue with the Aptos node API port configuration, which can only be exposed on port 8080, causing container startup or co... Logs ↗︎
Test_CCIP_TokenTransfer_LnR_without_TransferRef_EVM2Aptos The test failed due to an issue with the Aptos node API port configuration or connectivity. Logs ↗︎
Test_CCIP_RegulatedTokenTransfer_EVM2Aptos The test failed because the Aptos node API could not be exposed on port 8080, which caused the test to not run as expected. Logs ↗︎

... and 20 more

View Full Report ↗︎Docs

@pkcll pkcll requested review from jmank88 and patrickhuie19 July 7, 2026 05:16
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