17.11 Platform Insights Planning issue

Planning for groupplatform insights

• Board link

---

Goals

Event Platform

• NATS: Compile an architecture blueprint for NAT... (core#3 - closed) • Ankit Bhatnagar • 17.11
• Platform: Develop initial distribution via Helm... (core#8 - closed) • Ankit Bhatnagar • 17.11
• Platform: Setup pre-staging environment on GKE (core#6 - closed) • Ankit Bhatnagar • 17.11
• NATS: Research and document authentication/auth... (core#5 - closed) • Arun Sori • 17.11
• SendStandbyStatusUpdate should be called period... (gitlab-org/analytics-section/siphon#82 - closed) • Arun Sori • 17.11
• Siphon: research NATS connection options (gitlab-org/analytics-section/siphon#69 - closed) • Arun Sori • 17.11
• Platform: Research & document initial strategy ... (core#4 - closed) • Robert Hunt • 17.11
• Create complex multi-point e2e tests (gitlab-org/analytics-section/siphon#70 - closed) • Max Woolf • 17.11
• Ensure PG connections set application_name (gitlab-org/analytics-section/siphon#110 - closed) • Max Woolf • 17.11
• Memory profiling siphon and track allocation of... (gitlab-org/analytics-section/siphon#112 - closed) • Arun Sori • 17.11

Dashboard Framework

• Spike: Decouple dashboard framework from Analyt... (gitlab-org&16513 - closed) • Robert Hunt
• Persist project selector filter in the URL (gitlab-org/gitlab#520212 - closed) • Daniele Rossetti • 17.11
• Hide Customizable dashboard user flows (gitlab-org/gitlab#525203 - closed) • Jiaan Louw, Daniele Rossetti • 17.11
• Spike: Dashboard Data Exploration (gitlab-org/gitlab#525642 - closed) • Jiaan Louw • 18.0

Technical Roadmap improvements

• Remove ClickHouse Compute nodes from Opstrace p... (gitlab-org/gitlab#505419 - closed) • Arun Sori • 17.11
• Address backlog of flaky tests in Platform Insi... (gitlab-org/gitlab#513347 - closed) • Max Woolf • 17.11
• Fork, rename, and refactor the Opstrace repo to... (gitlab-org/gitlab#521825 - closed) • Ankit Bhatnagar • 17.11
• https://gitlab.com/gitlab-org/gitlab/-/issues/449019+s

Dashboards consultation

• Security:
  • https://gitlab.com/gitlab-com/security-risk-management-stage/-/issues/51+
  • https://gitlab.com/gitlab-com/security-risk-management-stage/-/issues/54+
  • 🎨 Design: Security dashboard: "Status trends" a... (gitlab-org/gitlab#517321 - closed)
  • Build a proof of concept for Security Dashboard... (gitlab-org/gitlab#517842 - closed)
  • Secure: Vulnerability management reporting move... (gitlab-org&16328)
• Optimize:
  • Dashboard designer - Extend built-in visualizat... (gitlab-org/gitlab#508491)
  • Support default panel size from visualization t... (gitlab-org/gitlab#519521)
  • https://gitlab.com/gitlab-org/gitlab/-/issues/505532+
  • Group::Optimize Dashboard consolidation (gitlab-org&15794)
  • Consolidate Productivity Analytics into the das... (gitlab-org&16121)

Open bugs:

To-Do

• Define an approximate scope for the coming release.
• Apply appropriate labels to issues:
  • Priority
  • Department
  • Pricing Tier
• Review the proposed scope with Engineering.
• Review design objectives with UX.
• Get feedback and estimates from Engineering, confirming scope for the release.
• Final verification of issues scheduled for the release.
• Present selected issues in the Manage Kickoff on the 17th!

Previous <= => Next