feat(metrics): Enable AI searchbar on metrics explorer filter

[isaacwang-sentry]

Summary

• Add MetricsTabSeerComboBox component for AI-powered natural language query translation on the metrics filter bar
• Enable enableAISearch in the metrics SearchQueryBuilderProvider, gated behind gen-ai-features and gen-ai-search-agent-translate feature flags
• Follows the same pattern as Logs (LogsTabSeerComboBox) and Traces (SpansTabSeerComboBox)

How it works

• The AI search is per-metric-query (each metric panel has its own filter bar)
• When the user types a natural language query, it sends strategy: 'Metrics' to Seer
• Seer translates the query and returns a filter string
• The filter is applied to the current metric panel via useSetQueryParamsQuery()

Dependencies

• Requires Seer MetricsStrategy: https://github.com/getsentry/seer/pull/5451

Test plan

• Verify AI search icon appears on metrics filter bar when feature flags are enabled
• Verify natural language queries are translated and applied to the filter
• Verify feature flag gating works (no AI search without flags)
• Verify it works per-metric-panel (each filter bar is independent)

🤖 Generated with Claude Code

[sentry]

Bug: Incorrect prop names are passed to AskSeerComboBox and AskSeerPollingComboBox, such as onApplySearchQuery instead of applySeerSearchQuery, which will break the AI search feature.
_{Severity: CRITICAL}

Suggested Fix

In MetricsTabSeerComboBox, rename the props passed to AskSeerComboBox and AskSeerPollingComboBox to match their required interface. Specifically, change onApplySearchQuery to applySeerSearchQuery and mutationOptions to askSeerMutationOptions. Also, add the required analyticsSource and feedbackSource props to both components, referencing other implementations for appropriate values.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: static/app/views/explore/metrics/metricsTabSeerComboBox.tsx#L176

Potential issue: The `MetricsTabSeerComboBox` component passes incorrect props to its
child components. `AskSeerPollingComboBox` receives `onApplySearchQuery` instead of the
required `applySeerSearchQuery`. `AskSeerComboBox` receives `onApplySearchQuery` instead
of `applySeerSearchQuery` and `mutationOptions` instead of `askSeerMutationOptions`.
This will cause a runtime `TypeError` when a user selects an AI search suggestion
because the expected callback function `props.applySeerSearchQuery` will be undefined.
This breaks the AI search functionality. Additionally, both child components are missing
the required `analyticsSource` and `feedbackSource` props.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Wrong prop names passed to ComboBox components

High Severity

The AskSeerComboBox component expects props named applySeerSearchQuery and askSeerMutationOptions, but this code passes onApplySearchQuery and mutationOptions instead. Similarly, AskSeerPollingComboBox expects applySeerSearchQuery but receives onApplySearchQuery. At runtime, the components will destructure undefined for the expected prop names, causing a TypeError when a user selects a query result (props.applySeerSearchQuery(item) is called on undefined). The Logs and Spans implementations correctly use applySeerSearchQuery and askSeerMutationOptions.

Additional Locations (1)

• static/app/views/explore/metrics/metricsTabSeerComboBox.tsx#L173-L181

 

[cursor]

Missing required analyticsSource and feedbackSource props

Medium Severity

Both AskSeerPollingComboBox and AskSeerComboBox require analyticsSource and feedbackSource string props (used for analytics tracking and feedback form attribution), but the metrics implementation doesn't provide either. The Logs variant passes analyticsSource="logs" and feedbackSource="logs_ai_query", and Spans passes analyticsSource="trace.explorer" and feedbackSource="trace_explorer_ai_query". Without these, analytics events will fire with undefined sources and feedback forms won't have proper attribution.

 

[cursor]

Unused currentQuery variable from hook call

Low Severity

currentQuery is assigned from useQueryParamsQuery() but never referenced anywhere in the component. This appears to be a leftover from development. The hook call itself may trigger unnecessary subscriptions or re-renders.

 

[getsantry]

This pull request has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you add the label WIP, I will leave it alone unless WIP is removed ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀