Use Case

As a... Data Explorer User
I want... The experience to feel fast and snappy taking me straight to productive workflow pages
So that... I can start exploring my data as soon as possible

User Experience

• When navigating to data explorer the page begins connecting to a cluster as soon as possible

Dependencies

• Navigation UI

Risks/Unknowns

What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)

• Users can have data explorer bookmarked subverting this change
• Users can be sent to data explorer through a number of avenues, do we account for all of them?

Acceptance Criteria

Implementation Requirements

• Discourage navigation to data explorer without an intended destination cluster
  • i.e. Remove the top-level nav to DE in favor of cluster specific buttons

Testing Requirements

• TBD

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• Observe the change in Sentry transaction duration experience as cluster connection happens simultaneously with page load for most scenarios