Skip to content

Conversation

zvkemp
Copy link
Contributor

@zvkemp zvkemp commented Dec 20, 2024

Still todo:

  • test that metrics aren't included if the option is disabled
  • move a bunch of logic into Instrumentation::Base or an appropriate mixin
  • standardize the logic gating on presence/absence of the metrics-api gem
  • should metrics-api be unconditionally required? I.e does the presence of metrics-api in the bundle mean it should be considered active?
  • test the client middleware
  • any metrics on the other patch modules?
  • Once the logic has been moved to its appropriate home, this PR should be split into at least two parts; 1) for generic metrics support on Instrumentation::Base and 2) concrete metrics on sidekiq

blockers

  • opentelemetry-metrics-api and opentelemetry-metrics-sdk are not in sync (metrics-sdk is newer, and includes methods that aren't implemented by the rubygems version of metrics-api). In tests, I am bundling from github for both of them.
  • Semantic conventions for metrics are not present in the ruby lib
  • messaging.queue.latency should be proposed to semconv
  • resolve question of how to time metrics that correspond to a span — it seems like in most cases a collector should be able to synthesize histograms or counters for anything with a span; unclear why semconv demands some required metrics that also have spans.

@zvkemp zvkemp force-pushed the sidekiq-metrics branch 2 times, most recently from 28a6af8 to 04c4243 Compare January 7, 2025 20:07
@zvkemp zvkemp force-pushed the sidekiq-metrics branch 4 times, most recently from 8e4e07f to 8c18433 Compare January 24, 2025 21:58
Copy link
Contributor

github-actions bot commented Mar 7, 2025

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot

@github-actions github-actions bot added the stale Marks an issue/PR stale label Mar 7, 2025
@kaylareopelle kaylareopelle removed the stale Marks an issue/PR stale label Mar 11, 2025
Copy link
Contributor

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot

@github-actions github-actions bot added the stale Marks an issue/PR stale label Apr 11, 2025
@kaylareopelle kaylareopelle removed the stale Marks an issue/PR stale label Apr 21, 2025
Copy link
Contributor

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot

@github-actions github-actions bot added the stale Marks an issue/PR stale label May 22, 2025
@kaylareopelle kaylareopelle added keep Ensures stale-bot keeps this issue/PR open and removed stale Marks an issue/PR stale labels May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keep Ensures stale-bot keeps this issue/PR open
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants