Skip to content

Track instrumentation config option coverage and declarative_name population#21

Merged
jaydeluca merged 1 commit into
mainfrom
copilot/add-additional-metrics-instrumentation
Apr 17, 2026
Merged

Track instrumentation config option coverage and declarative_name population#21
jaydeluca merged 1 commit into
mainfrom
copilot/add-additional-metrics-instrumentation

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 17, 2026

instrumentation-list.yaml config options now carry a declarative_name field. We need metrics to monitor how completely that field is populated across all instrumentations over time.

New metrics

  • instrumentation.libraries.with_configurations – count of instrumentation libraries that declare at least one config option
  • instrumentation.configurations.total – total config options across all instrumentations
  • instrumentation.configurations.with_declarative_name – config options where declarative_name is set

Changes

  • InstrumentationMetricsParser.__init__ – three new counters for the above
  • update_metrics – iterates each library's configurations list; increments libraries_with_configurations once per library and per-entry counts for total_configurations / configurations_with_declarative_name
  • fetch_instrumentation_metrics – emits the three new gauges and logs their values

@jaydeluca jaydeluca marked this pull request as ready for review April 17, 2026 19:41
@jaydeluca jaydeluca merged commit e951c9d into main Apr 17, 2026
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