Skip to content

feat(onboarding): Add missing ProductSolutions for Ruby, Elixir, and Rust#115474

Draft
sentry-junior[bot] wants to merge 1 commit into
masterfrom
johdax/add-ruby-elixir-rust-product-availability
Draft

feat(onboarding): Add missing ProductSolutions for Ruby, Elixir, and Rust#115474
sentry-junior[bot] wants to merge 1 commit into
masterfrom
johdax/add-ruby-elixir-rust-product-availability

Conversation

@sentry-junior
Copy link
Copy Markdown
Contributor

@sentry-junior sentry-junior Bot commented May 13, 2026

Summary

Add missing ProductSolution entries to platformProductAvailability for Ruby, Elixir, and Rust so onboarding correctly shows available feature toggles for these platforms.

Changes

Platform Before Added
ruby, ruby-rack, ruby-rails PERFORMANCE_MONITORING, PROFILING, LOGS METRICS
elixir (not listed) PERFORMANCE_MONITORING, LOGS, METRICS
rust (not listed) PERFORMANCE_MONITORING, LOGS, METRICS

Verification

Feature support cross-checked against sentry-docs HEAD frontmatter (notSupported/supported declarations) for each platform × feature combination:

  • Ruby: metrics/ page exists under ruby/common/ with no exclusions
  • Elixir: logs/, tracing/, and metrics/ pages exist; no profiling/ or session-replay/ pages
  • Rust: logs/, tracing/, and metrics/ pages exist under rust/common/; no profiling/ or session-replay/ pages

Context

Thread: the #discuss-sdk conversation about the SCM-first onboarding flow needing accurate platform → feature mappings.

…Rust

Add Elixir and Rust to platformProductAvailability and add METRICS to
Ruby/Ruby-rack/Ruby-rails entries.

Feature support verified against sentry-docs frontmatter:
- Ruby (ruby, ruby-rack, ruby-rails): add METRICS (already had perf, profiling, logs)
- Elixir: add PERFORMANCE_MONITORING, LOGS, METRICS (no profiling/replay in SDK)
- Rust: add PERFORMANCE_MONITORING, LOGS, METRICS (no profiling/replay in SDK)
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label May 13, 2026
@github-actions
Copy link
Copy Markdown
Contributor

📊 Type Coverage Diff

✅ No new type safety issues introduced. Coverage: 93.51%

@jaydgoss
Copy link
Copy Markdown
Member

Adding options to platformProductAvailability is only a subset of the work required here.

The purpose of the toggles associated with platformProductAvailability in onboarding is to alter the instructions displayed to the user relative to wether a toggle is on / off. Looks like with this change the instructions remain static.

See #115425 as an example of how to make instructions dynamic relative to the toggles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant