Sprint - Aug 19 to Aug 30

[marandaneto]

Global Sprint Planning

3 things that might take us down

1. infra inconsistencies EU/US - next sprint to upgrade dev in US to 23.12.something

Team name game score

7 out of 9 are doing great. Noice.

Urgent incident follow-ups

https://github.com/orgs/PostHog/projects/103/views/2

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

-

[marandaneto]

Team Replay Full team!

Support hero: @marandaneto

• @daibhin - 1 day
• @pauldambra working half-ish days for a couple of days until better clarity
• @neilkakkar ?

Retro

• @marandaneto performance issues on iOS although that means more people are trying out.
• @marandaneto Paul and Neil are back next week.

High priority

✅ done
🟢 in progress, on track
🟡 in progress, off track
🔴 missed

• Onboard @neilkakkar into the team 🔴
• Reduce support backlog (<=10 tickets, currently 21) @daibhin 🟢
• Error tracking alpha @daibhin 🟡
  • convert fingerprints to arrays (currently strings) 🟢
  • Add alpha tags in UI and feedback banner 🟢
  • share with customers previously interviewed (no feature preview) 🟡
• Build out SDK support 🔴
  • Manual capture methods for JS and Python SDKs
• iOS session recording performance improvements @marandaneto ✅
  • multiple people complaining about performance hit for screens that are constantly redrawing such as animations, transitions, maps, etc, so this is a priority.
• React Native session recording @marandaneto 🔴
  • PTO, sick leave, and focus on iOS session recording performance improvements

Low priority / side quests

• replay bug investigation tooling @pauldambra 🔴
  • playback snapshot by snapshot
  • Paul is OOO
• convert session recording filtering to RecordingsQuery 🟢

OKR

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

• 📱Goal 1: People think of PostHog as a mobile solution 🟡
• 🪲 Goal 2: Error tracking in people's hands 🟢
• ⁉️ Goal 3: Hiring 🟡
  • Neil's joining the team! 🟢
  • iOS Engineer

High priority

• Onboard @neilkakkar into the team
• Network logs not capturing everything @pauldambra
  • can we capture network more reliably
  • is there a bug maybe alongside fullstory
  • how hard would network recorder be to contribute back to rrweb
  • can we increase message size now we're using vector/other-thing-which-name-i-have-forgotten
• React Native session recording @marandaneto
  • 1st alpha version
• Masking and redacting Jetpack Compose views, issue @marandaneto

Error tracking

• Alpha release @daibhin
  • share with customers previously interviewed (no feature preview)
• Alerting v1 @daibhin / @benjackwhite
  • Integrate "Connected alerts" component into error tracking UI
  • Add masking key functionality to CDP
• Build out SDK support
  • Manual capture methods for JS and Python SDKs @daibhin
  • Exception auto capture - Python - @neilkakkar
• Demangling stack traces - @pauldambra ?

Low priority / side quests

• replay bug investigation tooling @pauldambra
  • playback snapshot by snapshot
• convert session recording filtering to RecordingsQuery @daibhin
• Flutter web using WebASM @marandaneto
• Sample recordings, issue @daibhin
• Hire iOS Engineer @marandaneto
• Mobile session replay user interviews @marandaneto @annikaschmid
• Support ph-no-capture for SwiftUI, issue @marandaneto
• SwiftUI Text view to be detected as a SwiftUI Image view, issue @marandaneto

[benjackwhite]

Team Continuously Deploying Patches

Support: @benjackwhite

Retro

High priority

• 🟡 Property/Event definitions off the critical path @oliverb123
  • Built - just needs deploying and testing now
• 🔴 Exception ingestion @bretthoerner @benjackwhite
  • Nothing done here
• Delivery service V0.2
  • 🟢 Stress test the existing rusty hook system and any improvements for a V0.1
    • Bunch of improvements made here
  • 🟢 "bad function" rate limiting system
    • New system in place seems to work as designed
  • 🟢 Architect V0.2 ("Codename Cyclotron")
    • Strong progress here
• 🟢 Final UX stuff to enable releasing this in some form @benjackwhite
  • Few PRs queued up but its basically ready to go now

OKR

(to be refactored)

High priority

• Release Feature Preview and then general availability of Hog Functions @benjackwhite
• Implement lambdas/closures, add missing STL functions, and support all element property filters @mariusandra
• Support Replay team with Exception alerts using HogFunctions @benjackwhite @mariusandra
• Pricing plan for new functions so that we can actually migrate things over to it
• Get duplicate service up and running on Cyloctron so we can test team by team

[benjackwhite]

Team Infrared

Retro / hangover

• 🟢 Warpstream analytics PoC
  • 🟡 Mirror capture traffic to it @danielxnj
  • 🟢 Connect Clickhouse to it via entire Dev pipeline swapover @Daesgar @frankh
• 🔴 Reverse proxy sharding implementation @frankh
• 🟡 Vector as ingestion api @frankh
  • Some bumps but rolling out for reply prod
• 🟢 CDP has its own redis as to not affect

OKR

1. 🦹 Zero-trust security 🟢
2. 🤓 10x Developer Experience 🟡
3. 💪 Every service lives and dies alone 🟢
4. 💰 Save big on cost 🟡

High priority

• AWS costs exercise @benjackwhite
• Migrate analytics to warpstream @benjackwhite @danielxnj @frankh
• Work with #team-cdp to see if we can migrate the Vector config into rust capture.
• Add to django capture logging of payload shapes to determine long tail issues stopping us migrating to rust capture.

[Phanatic]

Team Feature Success

Support hero: @jurajmajerik

Retro

• Customer support :
  • Hospitable and Tools for humanity had the most issues opened this sprint.
  • Easier than last time.
  • Customers were asking about confusion re: why feature flags were evaluated as they were.
  • Multiple questions about overriding feature flags on the client.

⌛ No-code experiments : @Phanatic
✅ Customer Support, build some metrics @Phanatic
✅ Fixing request parser errors: @dmarticus
✅ Define mid-term success for feature flags rewrite: @dmarticus
✅ Experiment confidence intervals @jurajmajerik
⌛ Release the winning variant

Side Quests

• Updated Go SDK to support fallbacks to /decide endpoints if the Personal API key isn't provided, stood up CI and auto-versioning for this lib, and worked with some customers to merge in 3 new PRs to make the SDK better (good thing we got CI stood up before that!) @dmarticus
• fixed this person popover bug @dmarticus
• fixed the LemonInputSelector component that users were tweeting about @dmarticus

---

OKRs

1. Make sure feature flags can handle 10x current scale
2. No-code experiments
   3. Split out experiments into its own product

High priority

• No-code experiments : @Phanatic
• Feature flags rust rewrite, support person & group properties overrides : @dmarticus
• Supporting multiple experiment goals : @jurajmajerik

[fuziontech]

Team Click Haus, Haus of the Hogs

OKR Q2 2024

Objective

James as a Service -> Clickhouse as a Service

• P0 tasks such as
  • 🟢 Deletes
  • 🟢 Keeping clusters happy
  • 🟢 Provisioning more disks
  • 🟢 Schema Reviews
  • 🟢 Debugging
  • 🟢 Performance < Thanks @tkaemming
  • 🟢 Backups/Restores
• Decide whether ByConity is the way forward
  • 🟢 Load it with data, set up
  • 🟡 Test performance, test the functionality/compatibility gaps
• IF ByConity works, migrate over to it
  • 🟡 Enumerate all functionality that doesn’t work and update the functions/contribute to ByConity
  • 🟡 Syntax
  • 🟡 If it works on metal, put it in k8s with Karpenter 🟢 Already on K8s
  • 🟡 Evaluate which nodes we should use
• IF ByConity doesn’t work, reshard US to look like EU cluster
  • 🟡 All clusters (Dev, US, EU) should be consistent in shape and topology. This will make it easier to manage and maintain the clusters and apply learnings from one cluster to another.
  • 🟡 We want all cluster operations to be automated and managed through some form of infra as code that is available in source control.
  • 🟡 Schema management on ClickHouse should be entirely automated and managed through source control with no exceptions. This includes Coordinator schemas.
  • 🟡 We should be able to spin up and down replicas of any cluster with no manual intervention.
  • 🟢 We should be able to upgrade ClickHouse versions with no manual intervention.
  • 🟡 We should have tooling / runbooks for resharding (if we continue down the current coordinator path)

Board

https://github.com/orgs/PostHog/projects/85/views/2

Retro

@Daesgar - OOO this sprint

@fuziontech - Really great sprint - with @Daesgar focusing on the green field projects I've been able to dive deep into a few things that have needed attention for some time. A lot of progress on deletes (teams and person deletes are working mostly) and incidents have gone relatively fast. Performance work is especially exciting.

Board Snapshot

[EDsCODE]

Team Data <->

OKR Q2 2024

Objective

Query 3000

• Key Results:
  • Autocomplete
  • Increase general BI experience/product BI meta#157
  • Declutter the data warehouse UI and make the features intuitive to find

Data Modeling MVP

• Key Results:
  • Infrastructure decided and implemented
  • Integrating external data with feature flags
  • External data everywhere in insights/persons/cohorts
  • Get billing team to use modeling in posthog for their invoices_with_annual table

Retro

• Data Modeling MVP/experimentation. We have some ideas that need to be tested @tomasfarias
  feat(data-modeling): Data modelling django models and API #24232
• Data warehouse design refresh @EDsCODE
• Get a better view of adoption both absolute and relative to broad posthog sign ups @EDsCODE
• BI continued BI meta#157 @Gilbert09

High Priority

Eric off first week

• Data Modeling MVP/experimentation. Backend foundation is in place. Prioritize UI and materialization layer @tomasfarias @EDsCODE
• Continued quality improvements with data warehousing @Gilbert09
  • more integrations
  • monitoring/improving compaction work
  • first class credential support

[raquelmsmith]

Team Growth

Retro

Retro items

• @raquelmsmith

  • Support this week, Out next week
  • Launch / announce personless
  • Fix shenanigans with session replay pricing update
  • Fix monthly enterprise customers revenue issue - https://posthog.slack.com/archives/C043VJ93L3B/p1721940308706669
  • Set up billing alerts
  • Add LLM usage to usage reports for Lior

• @zlwaterfield

  • sentry profile / perf clean up
  • subscription cancellation reasoning dropdown
  • ICP score research - how is it calculated, where is it stored, when is it accessible, does it align with current views of ICP?
  • billing limit to numbers
  • teams annual plans
  • SAML tests
  • startup plan credits linked to infra cost

• bonus

  • org user syncing to billing

Q3 Goals

✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

1. 🟡 Make onboarding awesome for Product analytics and Data warehouse (Raquel)
2. 🟡 Support self-serve annual commitments (Zach)
3. 🟡 Dive into the data to understand our billing metrics and customers better (Zach)
4. ✅ Launch pricing for data warehouse (Raquel)
5. 🟡 Hire 2 people (one for billing, one for auth/permissions focus)

This sprint

Time off: Raquel out 1 day

• @zlwaterfield

  • Finish up billing limit migration
  • Get the first version for subscription interval support out
  • Complete pre-work for teams annual plans around multiple stripe customers/subscriptions
  • Get teams annual plan in prod (behind flag)
  • Make a plan for self-serve annual commitments (and start on some changes for it)
  • Work w/ Mine to get ICP score flowing back into PostHog
  • Work w/ Infra to get Celery using keda and new queues for rate limiting changes

• Other things on the go

  • migrate from fully free session replay plans
  • migration from mailgun to customer.io w/ Joe

• @raquelmsmith

  • Personless default switch
  • Flag-specific proxy url
  • Start on https://github.com/PostHog/company-internal/issues/1452
  • Fix error that happens after creation, merge feat: add flag and onboarding steps for dashboard templates #23069
  • Set up billing alerts
  • Add LLM usage to usage reports for Lior

(This is probably too much for this sprint.. listed in roughly priority order)

[Twixes]

Team Analytics of the Product

Support hero: Georgiy + Thomas + probably Anirudh
Off: Michael second week, Thomas second week and beyond, Anna 1 day. Also Julian's off for parental leave beyond this sprint.

Retro

We had an offsite, hacked some things together. Retro issue on this pending.

OKR

1. Rock-solid analytics (@thmsobrmlr + @webjunkie + @aspicer + @anirudhpillai)
   1. 🟢 Legacy Minus – removing legacy insights code so that we can move fast
   2. 🟠 Tests Plus – shipping fewer bugs in the first place.
   3. 🟠 Metrics Plus – catching issues before before users report
   4. 🟡 Performance Plus - eliminating UX pain via maximum query performance/reliability, based on Metrics Plus data
   5. 🟢 Support Plus – sparking joy for users when they’re led to report a bug
2. Answering more product questions, deeper (@thmsobrmlr + @webjunkie + @aspicer + @anirudhpillai)
   1. 🔴 Growth Plus - increasing ease of onboarding, and subsequent retention
   2. 🟡 Analysis Plus - answering more product questions, more deeply
3. 🟡 ArtificialHog (@Twixes + @skoob13) – an LLM-based chat-like interface for answering product questions.

High priority

• Alpha version of AI search-like querying for internal testing on Cloud – @skoob13 @Twixes
• Reliability metrics – @anirudhpillai
• Analytics alerts for internal PostHog dogfooding – @webjunkie
• Simplify group analytics billing with @raquelmsmith – @Twixes
• Fix the funnel querying issues affecting high-value customers – @aspicer

Low priority / side quests

• Writeup on async query execution, the caching system & cache warming to-dos @webjunkie

[robbie-c]

Team Analytics of the Web

Support hero: @robbie-c

Retro

Sessions v2 table is backfilled up to last weekend on US, but not ingesting new events: just need some help from team-clickhouse to get the MV back (it was deleted as part of an incident (it didn't cause the incident)).

I started thinking about the saving of filters / web analytics state and realised that I probably want to do conversion events first, plus I've had quite a few customers asking for this recently (and it was already on my roadmap). So I've been doing this first.

Planned Tasks

🟢 Figure out what's going on with cross domain tracking problems - it was user error! Added a way of debugging customer's implementations on their site, even when installed via npm
🔴 Come up with a solution for a few linked issues: people want a default set of filters, and people want it to be easier to separate their sites. Postponed behind conversions
🟡 Conversion events tile and page-level filters
🟡 Finish backfill on US and switch over to sessions v2 for everyone.

Bonus stuff

🟢 Session replay tile in web analytics (and error tracking)
🟢 "Time on page" in posthog-js
🟢 Better bot filtering
🟢 Improve the deprecation modal, use deprecation info that already have in posthog-js repo, add it to web analytics

OKR

1. Make querying fast enough for large customers
2. Heavily requested features
3. Work better with other products
4. Product and growth

High priority

• Conversion events tile and page-level filters
• Come up with a solution for a few linked issues: people want a default set of filters, and people want it to be easier to separate their sites. There's been a lot of dicussion on this in the past, see Make it easier to separate different websites #18863 Create a new "My Sites" scene #12181 Saved filters #20314 <-- I'm leaning towards the first link here but figuring this out is part of the work

Stretch goals

• Add some visual regression tests for web analytics
• Docs changes for the improvements to attribution