Skip to content

Add deep linking support for date ranges and analytic cards in Efficiency tab - #432

Draft
waheed-saroyia wants to merge 7 commits into
ubccr:mainfrom
waheed-saroyia:feature/date-range-efficiency-tab
Draft

Add deep linking support for date ranges and analytic cards in Efficiency tab#432
waheed-saroyia wants to merge 7 commits into
ubccr:mainfrom
waheed-saroyia:feature/date-range-efficiency-tab

Conversation

@waheed-saroyia

Copy link
Copy Markdown

Description

  • Added URL parameter support for start_time , end_time and duration in ISO format (YYYY-MM-DD)
  • Implemented analytic parameter to auto-expand specific metric cards
  • Added graceful fallback to default duration ("Last 30 Days") when:
    • Invalid date format provided
    • Date range is illogical (end before start)
  • Enhanced card expansion logic to handle direct linking

Example URL:
https://localhost:8080/#main_tab_panel:efficiency?start_time=2025-06-01&end_time=2025-06-30&analytic=CPU%20Usage

Motivation and Context

Enables:
🔗 Deep linking to specific analytics for sharing findings
📅 Bookmarkable views with predefined date ranges
🔍 Easier reproduction of performance diagnostics
👥 Streamlined collaboration between analysts and admins

Solves usability issues when:

  • Sharing specific time-bound performance metrics
  • Creating dashboard links for recurring reports
  • Documenting system performance incidents

Tests Performed

Manual Testing

Test Case Admin Account Regular User
Valid date range
Invalid date format
End date before start
Valid analytic parameter
Invalid analytic param
Combined parameters

Key Verifications

  • Date picker reflects URL parameters on load
  • Specified analytic card expands automatically
  • Falls back to duration when dates invalid
  • Maintains existing permission checks
  • Preserves normal tab functionality when no params

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants