init: AI Monitoring config should require Tracing to be enabled #484
Description
Summary
AI Monitoring is presented as a standalone feature in the init wizard, but it is functionally a subset of tracing — it works by wrapping AI SDK calls in spans. Selecting AI Monitoring without Tracing produces a config that either silently does nothing or sets trace sample rates the user didn't intend.
Current behavior
AI Monitoring appears as an independent toggle alongside Performance Monitoring (Tracing). A user can select AI Monitoring without selecting Tracing.
Gap
- If Tracing is off, AI Monitoring spans have nowhere to go — the integration is a no-op or produces an unexpected partial config
- The UI doesn't communicate the dependency, so users reasonably assume these are independent features
- The label "AI Monitoring (Track AI model calls, latency, and failures)" gives no hint that traces are required
Options
- Enforce dependency: automatically enable Tracing when AI Monitoring is selected (or block the selection with an inline note)
- Visual grouping: show AI Monitoring as a sub-item indented under Performance Monitoring/Tracing to communicate the relationship
- Warning on confirm: if AI Monitoring is selected without Tracing, show a warning before confirming
Recommendation
Visual grouping (sub-item under Tracing) plus a dependency enforcement on confirm. This is the clearest signal of the relationship without surprising the user mid-selection.
Action taken on behalf of Sergiy Dybskiy.