feat(yabeda): Add sentry-yabeda adapter gem

[dingsdax]

Sentry Ruby gem that connects Yabeda metrics to Sentry Metrics.

What it does

• Translates Yabeda metrics into Sentry:
  • counter ➡️ Sentry.metrics.count
  • gauge ➡️ Sentry.metrics.gauge
  • histogram / summary ➡️ Sentry.metrics.distribution
• Adds a background worker that periodically calls Yabeda.collect!
  (needed because Yabeda is pull-based, while Sentry is push-based).
• Provides start_collector! and stop_collector! to control this worker (must run after Sentry.init).

• Histograms and summaries are both treated as distributions.
• The adapter is automatically registered when required.
• Unit handling is basic for now, with plans to improve formatting later (we don't show units in Sentry yet)

Fixes RUBY-161
Fixes #2899

[linear-code]

RUBY-161 Yabeda adapter for Sentry Metrics

[sl0thentr0py]

some cosmetics first

[sl0thentr0py]

in the current start_/stop_collector model this is not very useful. Sentry generally does things automagically so the ideal design is that users just enable/add this gem and then something happens automatically, not that they have to start and stop it wherever in their code.

[dingsdax]

@sl0thentr0py

• CI workflow added
• hooked in after(:configured) instead of explicitly needed starting
• removed app for manual testing
• minimal README.md linking back to root README.md

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Collector thread leaks when re-initializing with metrics disabled
  • Collector teardown is now unconditional before checking enable_metrics, and the masking spec line was removed to verify re-initialization with metrics disabled leaves no collector.

Or push these changes by commenting:

@cursor push 6bf7f66c8d

Preview (6bf7f66c8d)

diff --git a/sentry-yabeda/lib/sentry/yabeda/configuration.rb b/sentry-yabeda/lib/sentry/yabeda/configuration.rb
--- a/sentry-yabeda/lib/sentry/yabeda/configuration.rb
+++ b/sentry-yabeda/lib/sentry/yabeda/configuration.rb
@@ -3,8 +3,10 @@
 module Sentry
   class Configuration
     after(:configured) do
+      Sentry::Yabeda.collector&.kill
+      Sentry::Yabeda.collector = nil
+
       if enable_metrics
-        Sentry::Yabeda.collector&.kill
         Sentry::Yabeda.collector = Sentry::Yabeda::Collector.new(self)
       end
     end

diff --git a/sentry-yabeda/spec/sentry/yabeda/collector_spec.rb b/sentry-yabeda/spec/sentry/yabeda/collector_spec.rb
--- a/sentry-yabeda/spec/sentry/yabeda/collector_spec.rb
+++ b/sentry-yabeda/spec/sentry/yabeda/collector_spec.rb
@@ -28,7 +28,6 @@
 
     it "does not start when enable_metrics is false" do
       Sentry.close
-      Sentry::Yabeda.collector = nil
 
       Sentry.init do |config|
         config.dsn = DUMMY_DSN

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 855c165. Configure here.}

[cursor]

Collector thread leaks when re-initializing with metrics disabled

Medium Severity

The Sentry::Yabeda.collector&.kill call is inside the if enable_metrics guard, so when Sentry is re-initialized with enable_metrics = false, any previously running collector thread is never killed and leaks. The kill and nil-assignment need to happen unconditionally, before deciding whether to create a new collector. The corresponding test masks this bug by manually setting Sentry::Yabeda.collector = nil before re-initialization.

Additional Locations (1)

• sentry-yabeda/spec/sentry/yabeda/collector_spec.rb#L28-L41

 

^{Reviewed by Cursor Bugbot for commit 855c165. Configure here.}

[sl0thentr0py]

for completeness and ensuring no data loss on shutdown, we need:

• a final flush/collect during close
• for this, since this is coming from another gem, we need another callback called :closed registered from the gem and call flush there
• move the kill in the :configured callback to this new :closed callback