feat(insights): Add prebuilt dashboard rendering for queues landing page

[DominikB2014]

Adds support for rendering the queues prebuilt dashboard on the queues landing page when the insights-queue-dashboard-migration flag is enabled, following the same pattern as HTTP and database modules.

• Adds useHasPlatformizedQueues hook that checks the insights-queue-dashboard-migration feature flag
• Adds PlatformizedQueuesOverview component that renders the BACKEND_QUEUES prebuilt dashboard via PrebuiltDashboardRenderer
• Updates PageWithProviders in the queues landing page to branch on the hook

[linear]

BROWSE-371 Implement basic queues module as dashboard

[DominikB2014]

@cursor review

[sentry]

Bug: The new AREA and LINE widgets in queueCharts.ts are missing the fields property. Other similar widgets in the codebase include fields that mirror aggregates.
_{Severity: MEDIUM}

Suggested Fix

Add a fields property to both the average-duration-widget and throughput-widget in queueCharts.ts. The value of the fields array should be identical to the aggregates array to maintain consistency with other prebuilt chart widgets.

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/dashboards/utils/prebuiltConfigs/queues/queueCharts.ts#L6-L16

Potential issue: The `average-duration-widget` and `throughput-widget` in
`queueCharts.ts` are defined with an `aggregates` property but lack a corresponding
`fields` property. While the `WidgetQuery` type defines `fields` as optional, a
consistent pattern across all other prebuilt AREA and LINE chart widgets in the codebase
is to include a `fields` array that mirrors the `aggregates` array. This inconsistency
could lead to runtime errors or incorrect rendering if the dashboard rendering logic
implicitly relies on the `fields` array, as the established pattern suggests it might.

[cursor]

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

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

[cursor]

Missing analytics event in platformized queues overview

Medium Severity

PlatformizedQueuesOverview does not pass analyticEventName to ModulePageProviders, so the "insight.page_loads.queue" analytics event won't fire when the migration flag is enabled. The non-platformized path passes analyticEventName="insight.page_loads.queue", and the analogous PlatformizedAssetsOverview correctly includes analyticEventName="insight.page_loads.assets". This silently drops page-load analytics tracking for all users with the flag on.

Additional Locations (1)

• static/app/views/insights/queues/views/queuesLandingPage.tsx#L116-L118

 

[cursor]

Destination table uses wrong aggregate for processing time

High Severity

The DESTINATION_TABLE uses avg(span.duration) for the column labeled "Avg processing time," but since the query condition includes both queue.publish and queue.process spans, this averages across both operation types. The original non-platformized table and the summary page's TRANSACTIONS_TABLE both correctly use avg_if(span.duration,span.op,equals,queue.process) to restrict the average to only processing spans. This will display incorrect, inflated or deflated values for "Avg processing time" in the destination table.

Additional Locations (1)

• static/app/views/dashboards/utils/prebuiltConfigs/queues/queues.ts#L32-L33