Sprint March 4 to March 15, 2024

[mariusandra]

Global Sprint Planning

3 things that might take us down

1. 🍍

Team sprint planning

For your team sprint planning copy this template into a comment below for each team.

# Team ___

**Support hero:** ___

## Retro

<!-- Grab the high and low priority items from last time and add whether that item was completed or not -->

- 

## Hang over items from previous sprint

<!-- For each item, decide to re-prioritise (and add below) or deprioritise -->

- Item 1. prioritised/deprioritise

## OKR

1. OKR, status (red/yellow/green) and action points if yellow/red

### High priority

-

### Low priority / side quests

-

[mariusandra]

Team Product Analytici

Support hero:

• Thomas

Retro

We blew some scheduled plans out the water and focused on support related activities.

• Michael worked on Dashboard copying, which morphed into environments, which morphed into TBD
• Julian worked on making CSV exports reliable again (new sidepanel, xlsx support, woohoo!), and on insight/dashboard frontend bugs (debounced filters).
• Tom did all manner of support
• Still we had the HogQL rewrite happening in parallel (Thomas and Marius)
  • 🟡 Trends - Still working of differences in the edges. (e.g. cohort filters + cumulative graphs, etc)
  • 🟡 Funnels - Ready to start testing next week
  • 🟡 Paths - Mostly done, last part waiting for funnels

OKR Q1 2024

🟢 = done 🟡 = working on, expect to finish 🔴 = might not make it

1. HogQL & Data Exploration (Julian, Marius)

   • 🟡 Convert ALL our insights to use HogQL as their base.
   • 🟡 Write great docs for HogQL and data exploration nodes.
   • 🔴 Improve the type system and get rid of assumeNotNull.
   • 🔴 Proactively monitor query performance.

2. Product Analytics frontend (Thomas, Michael)

   • 🟡 Clean things up now that we have PostHog 3000 and HogQL everywhere.
   • 🟡 Work on the universal "Explore" view.

3. BI (Tom)

   • 🟡 Support non-event data sources on HogQL insights.
   • 🟡 Build the new querying experience, and/or integrate it into the "Explore" view.

Next sprint

• @Gilbert09
  • Data Warehouse tables into Insights.
  • General BI/DW 🫡
• @thmsobrmlr
  • Support 🍄😱
  • (Paths from funnels & funnels testing?)
• @mariusandra
  • Continue the HogQL conversion (testing funnels? more trends?)
  • Sidequest: HogQL type system and null handling
  • Sidequest: Better JSON handling in HogQL
• @Twixes
  • Using dashboards across projects
  • Dashboard loading bugs, filters vs queries.
  • Sidequest: Performance optimisations into HogQL
• @webjunkie
  • Exports (more stability. temporal? bump up 10k row and memory limits?)
  • Async queries (celery autoscaling?)
  • API docs (get them into posthog.com)
  • Sidequest: Django 4.2 upgrade (SQL commenter is blocking?)

Marius TODO:

• figure out how to single thread HogQL conversion
• Probably get Julian to do fewer things at the same time

[pauldambra]

Team Replay-i

Support hero: Manoel

no long leave for anyone so should be a full house mostly

Retro

• lost so much time to this rubbish cough 👎 @pauldambra
• number of mobile issues increasing... good because it means people using it, hard because context switching @marandaneto
• support as a whole is context switching a lot - hard to know if we should commit to less so it feels less bad to be pulled onto support @daibhin

Hang over items from previous sprint

main story

• 🔴 iOS session replay have first captured recording @marandaneto
  • not yet, quicker than Android since we have the basic API in place
  • but working through how to capture safely in iOS
• 🔴 5 Open Source Android apps tested with android replay @pauldambra
  • basically a 1 week sprint for me 😷
  • clearing my plate so I can focus on this
  • this will carry forward
• 🟡 get "show similar recordings" out for our team @daibhin @pauldambra
  • got embeddings generating and learning from that but still confused by the data

side quests

• contribute the network capture back to rrweb - so they don't make one that doesn't work for us - @pauldambra
  • need to do this but ok for it to float behind other "more important" things
• network payload capture on onboarding? @pauldambra
  • need to do this but ok for it to float behind other "more important" things
• ✅ adding billing limits to unsubscribe? @pauldambra
  • already present
  • once controls are generally released we can prompt people the first month they start to pay maybe
• how much embedding/clustering can we do just with session recording metadata (when can we avoid Open AI) @daibhin
  • settings stuff is out
  • what happens if someone wants to use replay without events

OKR

1. OKR, status (red/yellow/green) and action points if yellow/red

• 🟡📱 happy android replay users
  • had feedback from 3 beta testers
  • 1 active user
  • still looking for sweet spot between capturing right info and setting expectations
  • current approach is:
    • Manoel and Paul do some rounds of testing
    • then we go looking for more user testing
    • once we think their testing won't tell us about things we already know about
• 🟡 people love replay even more
  • still more bug reports than we'd like
  • canvas replay is out
  • some rrweb bugs patched directly
  • some folk are using replay as the main product - even wanting no event capture 🙈
• 🟡 first class mobile support
  • not focussed here, focus is on replay
  • but making good progress
  • continuing to crank out improvements & features to mobile SDKs

High priority

• iOS session replay have first captured recording @marandaneto
• 5 Open Source Android apps tested with android replay @pauldambra
  • identify the next set of improvements
• get "show similar recordings" out for our team @daibhin @pauldambra
  • confidence in embedding generation
  • feedback from folk here
  • understanding similarity accuracy based on the data we send

TODO Paul

• Change the similar recordings goal to be 'how do we validate whether it's useful'

Low priority / side quests

• RN release a new major version for node/web/RN SDKs @marandaneto
• ordering for replay listing @daibhin
• capture reporting quota limiting back to replay clients @pauldambra
• hoqgl filtering for replay @daibhin

[robbie-c]

Team Web Analytici

Off: none

Last sprint

• Spent a lot of time on discussions and RFC (see WIP PR for latest on sessions table and person-less events https://github.com/PostHog/product-internal/pull/570 )
• Sessions table PR is ready for review, probably needs Jams (see https://github.com/PostHog/posthog/pull/20462) and designed queries https://posthog.slack.com/archives/C05LJK1N3CP/p1708536198957149

Hang over items from previous sprint

• Sessions table not shipped yet

OKR

1. Finish the beta to-do list
2. Find 5 high-ICP reference customers

High priority

• Write backfilling code for the sessions table, backfill for posthog only for now
• Hook up sessions table to HogQL
• Write queries (behind FF) to use sessions table in HogQL
• Not doing: touching person-less events beyond that RFC, just needed to design it enough to disentangle from sessions table so I could proceed

Low priority

• polish and be responsive to support

[tiina303]

Team Pipeline-i

Off: Tiina (2 weeks), Brett (1 week), Ted (3 days) Support: Ted & Xavier

Retro

High priority

• [x] PoE: Write path for the new distinctId->PersonId overrides - Ted
• [x] Backfill implemented and verified for teams with large number of distinct IDs - Ted
• [x] Ran squash for a single team - Tomas
• [x] Batch Export for cloud to cloud migrations - Brett
• [ ] pipeline UI available for beta testers - Tiina
  • made some progress, but got sidetracked with incidents and other requests

Low priority / side quests

• [ ] Person property updates don't slow down ingestion - Brett
• [ ] backfill topic incident follow-ups - Tiina

OKR

✅=finished 🟢=on track to finish this quarter 🟡=might not finish 🔴=won't finish

• ✅ Wrapped up Webhooks Delivery system - Brett
• ✅ Wrapped up capture-rs posthog-js rollout - Xavier
• 🟢 Wrapped up New Pipeline UI - Tiina
• 🟢 Wrapped up PoE (with backfills and squashes) - Ted
• 🟢 Volume spikes on session reply do not hurt other users - Xavier
• 🟢 Person property updates don't slow down ingestion - Brett
• 🟢 Requested data deletion is complete and reliably executed going forward - Tiina

High priority

• [ ] Launch Person IDs on Events for everyone - Ted
• [ ] Replay overflow implemented (blobby detects, updates redis zset, capture reroutes) - Xavier
• [ ] Improve visibility into pipeline (what's in the queue, what's slow) - Brett

Low priority / side quests

• [ ] Look at how large a squash table can be - Ted
• [ ] Distinct ID tombstoning in PG to fix person reuse - Ted
• [ ] Incident follow-ups

[raquelmsmith]

Team Growthi

Retro

Retro items

Lots of things in progress / left over. Quota limiting, Teams plan.

OKR

✅=finished 🟢=on track to finish this quarter 🟡=might not finish 🔴=won't finish

• 🟡 Improve activation rates for product analytics and session replay
  • ✅ Polish onboarding flow with Cory
  • 🟢 Run 1 experiment per week
  • 🟡 Do an average of 2 customer interviews per week
  • 🟡 Redefine and improve activation rates for PA & SR
• ⚪ Launch pricing for:
  • 🟢 Teams
  • 🟡 Product analytics 21M free

This sprint

High priority

• @raquelmsmith
  • [ ] Teams plan - in progress
  • [ ] 21M events free plan - in progress - need to make RFC for billing, but can start work
    • unless we want to wait until non-identified events are done, but I don't think we need to
  • [ ] Rethink some activation metrics (remove team member invited, double check rates with diff activities) - in progress
  • [ ] Prep for Zach to start 🙌
• @xrdt
  • [ ] Don't drop data for 7 (or maybe 3) days until after it's done - in progress, almost done
  • [x] Experiment - put people directly on insight creation page
  • [ ] Experiment on wording for "upgrade" / "subscribe" / "add a credit card" on billing page
  • [ ] Let people self-serve to new plans, like the new replay plan so they can get access to the controls - start

Low priority / side quests

• [ ] Write two articles for Andy
• [ ] Expired sessions should redirect users to the login page rather than popping lots of error toasts.
• [ ] Overlap in billing gauge projected / current / billing limit lines. https://posthoghelp.zendesk.com/agent/tickets/10070

[neilkakkar]

Team Feature Successi

Support hero: @jurajmajerik Days off: Juraj: 3 days Neil: 1 days

Retro

• Experiments UI create & view overhaul - @jurajmajerik -> Mostly roll over, working on create UI currently. Paywall on experiments took a while to align on + finally remove.
• Explore experiment metrics easily in insights - @jurajmajerik -> Will roll over
• Event based triggers for surveys (RFC here: https://github.com/PostHog/product-internal/pull/556/ )- @liyiy
• Find a good flow for restricting users to exposed users in secondary metrics for experiments - @neilkakkar -> Will roll over. Was unexpectedly sick for 4 days, release condition refactor took much longer, additional survey support, and incident happened.
• Add property filters to event matching in cohorts - @neilkakkar -> will roll
• Filter out internal users bug in experiments - @neilkakkar -> will roll

Hang over items from previous sprint

---

OKRs

1. 🔴 Doubling down on surveys
2. 🟡 Doubling down on experiments

High priority

• Experiments UI create & view overhaul - @jurajmajerik
• Fix common support issues with surveys, so support is minimal here - @jurajmajerik
• Address any incident remediation issues - @neilkakkar
• Filter out internal users bug in experiments - @neilkakkar
• Local evaluation of cohorts in PHP SDK - @neilkakkar

Low priority / side quests

• Explore experiment metrics easily in insights - @jurajmajerik
• Find a good flow for restricting users to exposed users in secondary metrics for experiments - @neilkakkar
• Add property filters to event matching in cohorts - @neilkakkar
• Temporal queues for feature success - @neilkakkar

[benjackwhite]

Team Infra

Support hero: @daniel

(Frank on vacay - will update this on Monday)

Hang over items from previous sprint

1. 🟢 Finalise charts movement and get Argo CD canary deploys working @danielxnj
   • Charts are fully in charts - no more charts-clickhouse
2. 🟡 Rollout all clients to new capture endpoints
   • JS is rolled out (us.i.posthog.com)
   • Remaining issue was array.js which we will solve with a new redirect approach
   • Encountered more issues with IP resolution
3. 🟢 Mr Blobby -> EFS
   • Running in US and EU
   • Virtually no rebalancing costs :shocked_pikachu:
   • Just need to plan the switchover date and ensure autoscaling is in place

OKR

1. 💪 Deploy with confidence 🟡
2. 💰 Keep costs under control ✅
3. 👀 More Observability 🔴
4. 🎯 Soc2 ✅

High priority

1. Rollout redirect approach for static assets @danielxnj
2. More follow up on SOC2 and compliance with customers @danielxnj
3. Get everything onto contour ingress so we can offer Pipeline a way of gradually rolling out capture
4. Job spec out for SRE hire @benjackwhite
5. Attempt Mr Blobby v3 with EBS shared mount volume @benjackwhite @danielxnj

Low priority / side quests

[EDsCODE]

Team Data Warehouse

OKR Q1 2024

Objective

Get EU moved over to new cluster

• Key Results:
  • Terraform, ansible, data migrated over, backups, housewatch
  • Deprecate old cluster

ByConity evaluation

• Key Results:
  • Load up with all clickhouse data and benchmark

5 reference customers with qualities:

• Key Results:
  • Paying a reasonable amount
  • Tell us they’re delighted
  • Not a big edge case
  • Using our in house data import pipeline
  • Weekly queries on a data warehouse connected table
  • Saving queried tables to insights?

Data Warehouse queries are compatible with insights hogQL

Retro

Product

• [ ] @EDsCODE data warehouse data in trends
• [ ] @Gilbert09 View/table linking precursor to linking data warehouse data to person models

Infra @fuziontech is out for 1/2 of next sprint

• [ ] Adapt current Ansible playbooks to new cluster configs starting with Coordinator
• [ ] TF Coordinator and have at least 2 running behind a load balancer

High priority

Product

• [ ] @EDsCODE data warehouse data in trends breakdown frontend
• [ ] @EDsCODE Restore row limit tracking for all integrations
• [ ] @EDsCODE Reach out and do user research on current usage (the goal is to figure out what's needed to increase usage)
• [ ] @Gilbert09 Ship MVP: View/table linking precursor to linking data warehouse data to person models. Able to filter these like person properties in trends

Infra

• [ ] SOC2 support
• [ ] Adapt current Ansible playbooks to new cluster configs starting with Coordinator
• [ ] TF Coordinator and have at least 2 running behind a load balancer