feat(analytics): Add Seer feature tracking to issue_details.seer_opened event #104547
Conversation
…ed event Add has_summary, has_root_cause, has_solution, has_coded_solution, and has_pr properties to the "Issue Details: Seer Opened" analytics event to track which Seer features are available when users open the panel. This enables analytics to answer questions like: - When users open Seer, do they already have a root cause? - How often is the panel opened after code changes are generated? - Does having a summary correlate with opening the Seer panel?
| pollInterval: 1500, | ||
| }); | ||
|
|
||
| const {data: summaryData, isPending: isSummaryPending} = useGroupSummaryData(group); |
There was a problem hiding this comment.
Bug: The has_summary analytics property is often false due to useGroupSummaryData reading an unpopulated cache.
Severity: HIGH | Confidence: High
🔍 Detailed Analysis
The has_summary analytics property in the Seer opened event will frequently be false even when a summary is available. This occurs because useGroupSummaryData is called with enabled: false, causing it to only read from the cache. If the GroupSummary component, which actively fetches the data, has not yet populated the cache or completed its fetch, the analytics event will incorrectly report has_summary: false. This leads to systematically inaccurate analytics data for feature tracking.
💡 Suggested Fix
Modify the analytics event to accurately reflect has_summary by ensuring the summary data is fetched and available before the event is fired, or by using the same useGroupSummary hook that actively fetches the data.
🤖 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/issueDetails/streamline/sidebar/seerSectionCtaButton.tsx#L66
Potential issue: The `has_summary` analytics property in the Seer opened event will
frequently be `false` even when a summary is available. This occurs because
`useGroupSummaryData` is called with `enabled: false`, causing it to only read from the
cache. If the `GroupSummary` component, which actively fetches the data, has not yet
populated the cache or completed its fetch, the analytics event will incorrectly report
`has_summary: false`. This leads to systematically inaccurate analytics data for feature
tracking.
Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 6293789
There was a problem hiding this comment.
hmm can deploy and see if this ends up being a real issue
…ed event (#104547) add `has_summary`, `has_root_cause`, `has_solution`, `has_coded_solution`, and `has_pr` properties to the "Issue Details: Seer Opened" analytics event to track which Seer features are available when users open the panel. This PR was created with claude code, given the linear ticket as a prompt via Linear-MCP. Fixes https://linear.app/getsentry/issue/AIML-1994/track-seer-panel-fields-in-seer-opened-event
add
has_summary,has_root_cause,has_solution,has_coded_solution, andhas_prproperties to the "Issue Details: Seer Opened" analytics event to track which Seer features are available when users open the panel.This PR was created with claude code, given the linear ticket as a prompt via Linear-MCP.
Fixes https://linear.app/getsentry/issue/AIML-1994/track-seer-panel-fields-in-seer-opened-event