Sprint - Feb 24 - Mar 7

[marandaneto]

Sprint Planning

List of incidents + any action items that haven't been scheduled yet

Team sprint planning

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

# Team ___

**Support hero:** ___

## OKR

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

## Retro

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

### High priority

-

### Low priority / side quests

-

[dmarticus]

Team Flexible Layers of Authenticated Gating Services (FLAGS)

Retro

We shipped remote config flags with encrypted payload, we are adding quota limiting to our flags platform, the .NET SDK is officially in beta, and new flags is nearly live

What went well

• @haacked
  • Launched the .NET SDK beta release
    • support for local evaluation and encrypted configs
  • lots of yak shaving in our SDKs
• @havenbarnes
  • Launched remote configs with encrypted payloads
    • usage dashboard TODO LINK
  • Made great progress with the Java SDK; fixing up a lot of the tests that broke with the refactor
    • will start landing PRs week of Feb 18th
• @dmarticus
  • new flags blocked a bit on deployment, need to figure out how to connect to GeoIP. Goal of releasing to team 2 pushed back to EOW (Feb 21)
  • implemented quota limiting on the app side, will complete the quota limiting on the client libraries + release this feature by EOW (Feb 21)
• General
  • support SLA response rate was excellent, 0 breaches for escalated tickets.

What could've gone better

• @dmarticus behavioral cohort targeting work not started, quota limiting + challenges of deploying the new flags service took more time. Might be able to start by EOW but there's a chance I miss
• @havenbarnes small bug in remote config release that only affected .NET SDK users for a 24 hour timeframe (context)
• @annikaschmid
  • customer outreach around flags isn't going great – emailed 50 different PostHog users (active within last 30 days) who aren't using flags and asked them for a quick call on why not. Got no responses. Going to attempt more outreach this time and ask for email feedback rather than calls.

This sprint

Themes: Continue rolling out new flags, manage quota limiting rollout, start work on behavioral cohort targeting, land Java SDK, and work on some feature flag UX improvements

• @dmarticus

  • Roll out quota limited flags to everyone
    • customer comms
    • support this on old and new flags
  • Roll out new flags to a meaningful percentage of production traffic
    • only managed to roll this out to team 2 during last sprint.
  • Finish non-production-rollout-blocking tasks for new flags
    • All "necessary for release" tasks from here: Feature Flags Rewrite: List of things to get done #22131
  • Deliver RFC for behavioral cohort targeting
  • Start work on behavioral cohort targeting

• @havenbarnes

  • Launching new posthog-java SDK
  • Working on release conditions UX

• @haacked

  • Wrap up 1.0.0 release of posthog-dotnet.
  • Create a feature-flag sdk library insight
  • Implement optimistic concurrency in feature flag editor

Support

• 2/24 - 03/01 @dmarticus
• 3/01 - 03/07 @havenbarnes

Q1 2025 Objectives

(I'm going to turn these into sub-issues so I don't have to type so much)
✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

🟡 Performance & Reliability

• 🟡 Complete migration of feature flag evaluation traffic from the legacy /decide endpoint to the new /flags endpoint (@dmarticus)
• ⚪ Establish comprehensive monitoring and observability for the feature flag platform (@dmarticus, @havenbarnes)
• ⚪ Enhance Grafana metrics to differentiate between infrastructure failures and logical errors (@dmarticus)
• ⚪ Collaborate with infrastructure team to create infrastructure cost analysis and dependency mapping with Michi (@dmarticus)
• 🟡 Improve observability of the feature flag evaluation process by tying flag evaluation results to the original request context (@havenbarnes)
• ✅ Experiment with sampling request parameters for high-value customers to have better observability for support requests (@havenbarnes)
• ⚪ Implement actionable Sentry alerts in #alerts-feature-flags channel (@havenbarnes)
• ⚪ Integrate PostHog error tracking with new flags endpoint (@dmarticus)
• 🟡 Implement read-only flags (specifics to be defined, see the following RFC) (@havenbarnes)

🟡 Customer-Driven Innovation

• 🟡 Behavioral cohort targeting for flags (RFC here) (@dmarticus)
• 🔴 Feature management (@havenbarnes)
  • should we create a notebook template? Notebooks are kinda buggy at the moment and don't have an owner.
• ⚪ Automatically manage flag staleness (@haacked)
• ⚪ Customer research-driven features (TBD based on the findings of the market research and customer interviews)

⚪ Strategic Research

• Identify and analyze key user segments:

1. Current active users
2. Competitor users
3. Custom solution implementers
4. Potential users unaware of feature flagging

• Conduct customer interviews to identify gaps and growth opportunities
• Document findings and recommendations for product roadmap.
• More context here

🟡 SDK Spike

• 🟡 Evaluate feasibility and tradeoffs around adding feature flags to the Java SDK
• ⚪ Investigate improving the Rust SDK (add feature flag evaluation, implement the suggestions from the open issues etc.)
• 🟢 Research .NET SDK demand + feasibility @haacked
• 🟡 Fix open issues in the Python and Node SDKs: (Python, Node)

🟡 User Experience Improvements

Low-hanging, medium-impact, and largely context-free fruit that can be picked up by any team member during available capacity:

• ⚪ Consolidate boolean and multivariate flag interfaces
• ⚪ Show flag evaluation results more clearly in the flag editor UI
• ⚪ Improve the experience of syncing flags between environments
• 🟡 Anything else from the current feature flag backlog

[marandaneto]

Team Surveys

• Support hero: @marandaneto
• On call weekend: @marandaneto
• 1 day PTO @ioannisj
• 3-4 March PTO @lucasheriques

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

Retro

Retro - Team Notes

• Lost about half the sprint due to illness, and then was slow to recover and pick up. A few replay-related issues popped up on iOS, and since this is now a paid product it made sense to switch focus on those. @ioannisj
• IMO everything went well @marandaneto +1 @lucasheriques

Retro - Tasks

High priority

Surveys:

• 🔴 iOS survey display logic @ioannisj
  • will finish up next sprint
• ⚪ iOS Basic type popup display @ioannisj
  • major focus will be on how to properly present this in the host view hierarchy without breaking navigation
• 🟢 RN - survey display logic and start with survey question branching logic @marandaneto
  • display logic and more is done, question branching is dropped to simply the MVP
• 🟡 Allow a survey to pop up repeatedly @lucasheriques
• 🟢 feat: new filters for surveys answers @lucasheriques (replaced the previous one)
• 🔴 Send intro to up to 5 customers to get feedback based on the questions we prepared @lucasheriques
  • the earlier the better, weekend slows down
  • will send on on Monday/Tuesday of next sprint
• 🟢 When filtering survey responses, the charts are not updated @lucasheriques
• 🔴 🐛 Wrong graph series after changing question order @lucasheriques
  • Figure out if the originalQuestionIndex coming from the BE is persisted since the survey first iteration to fix the responses
  • will roll over to the sprint - we had other bugs that came along so didn't have the time to finish this
• 🟢 🐛 Changes are lost on save when editing a survey that contains errors @lucasheriques
• 🟡 🐛 Required answer on a survey @lucasheriques
  • needs follow up from comment
• 🟡 🐛 Surveys not capturing responses @lucasheriques
• 🟢 Surveys - Increase the number of allowed choices for single and multiple choices questions @lucasheriques
  • let interested people know
  • tell Joe to add -> changelog (15 choices now instead of 5)

Session replay:

• 🟢 Android, iOS, and RN session replay - GA (versions, docs, review billing, etc) @marandaneto
• 🟡 Some iOS related issues reported. Fixed a few issue and investigated others

Low priority / Side quest

• 🟢 🐛 Build fails for React Native when compiled as a static library @ioannisj
• ⚪ Adds referrerURL automatically @ioannisj
  • This popped up this last two weeks. Will investigate
• ⚪ Surveys: customize text color of feedback widget @lucasheriques
• ⚪ 🐛 Session replay won't start/stop if reloadFeatureFlags is called and session recording flag flipped @marandaneto
• 🟡 multiple SDK instances for iOS @ioannisj

Goals

• 🟡 Improve quality
• 🟡 Mobile Surveys
• ⚪ Talk to customers
• ⚪ Finish up WIP features

High priority

• RN surveys - address all edge cases and release the 1st alpha @marandaneto
  • add documentation with samples and limitations
  • are we charging even if it may contain bugs/cause skewed survey data, or are we gonna do something about it?
  • start with android or flutter if time allows
  • add a toggle on the SDK so it is enabled SDK side as well
  • lets wait for behavioral cohorts until we address the issue of surveys being shown on mobile | web -> send an email and let them know about device type config
• Close these iOS crashes @ioannisj
  • Crash in PostHogSessionManager.swift posthog-ios#302
  • Crash in UIView+Util.swift posthog-ios#303
• Focus on iOS survey @ioannisj
  • finish display logic
  • start working on the UI
• Surveys: partial responses @lucasheriques
  • some work has been done, need to see what's missing to fix it
  • see how this is charged, check usage report and survey response events
• Have at least one customer call scheduled @lucasheriques
• 🐛 Wrong graph series after changing question order @lucasheriques
  • compute a stable question index in the BE, use that to allow reordering
• 🐛 Errors on saving a survey form are not displayed @lucasheriques
• 🐛 Don't calculate NPS score for non-NPS questions @lucasheriques
• 🐛 Survey feedback widget events can be more accurate @lucasheriques
• 🐛 Triggering survey doesn't respect condition setted @lucasheriques
• Survey Can't Be Positioned Properly @lucasheriques

Low priority / Side quest

• Session Replay Mask text forces parent element to mask everything posthog-ios#296 @ioannisj
• SwiftUI masked items zindex on top of everything posthog-ios#295 @ioannisj
• Check if any pending issues on flutter session replay and go GA (in 2 weeks time) if not @marandaneto
• 🐛 Surveys - Long questions overflow in list of steps @lucasheriques
• 🐛 Surveys on mobile web are buggy right now @lucasheriques

[daibhin]

Team Error Tracking

Retro

🟢 Fixed a bunch of throughput issues so cymbal now goes brrrr
🔴 Query performance way down since ingesting plugin-server exceptions (unusable for team 2)
🟢 Necessary changes for alerting out the door 🎉

OKR

🟠 Migrate PostHog off Sentry
🟢 Ship the damn thing

High priority

• Onboard Hugues
  • @oliverb123 book flights!!
  • Create onboarding schedule
  • Onboarding week in London
  • Plan source map uploading

Migrate PostHog off Sentry

• Performance wins (query and ingest)
• Track exceptions in EU & US

Ship the damn thing

• Fix known bugs
  • Python exception ordering
  • Cloudflare worker
  • Next.js understanding
  • Cause option not captured
  • Stack traces occasionally missing in Node.js

[annaszell]

Team Product Analytics (Wed Feb 26 - Wed Mar 12)

🎉 @HamedMP joined the team! 🎉

Q1 2025 objectives

1. Main Goal: Make it a no-brainer for customers to use our insights

   • Research and improve insights
     • [Sandy] 🟡 Funnels
       • Filters in exclusion steps
       • Optional Steps
       • Time to convert trends
       • Unordered step UDFs
     • [Thomas] User Paths
       • 🟢 Investigation
       • 🟢 v2 of the FE
       • 🟡 split v2 of the BE
       • 🟡 architecture / changes for BE (UDFs? window functions?)
         • Better path cleaning support
     • [Anirudh] Retention
       • 🟢 filters on start/return event
       • 🟢 custom date ranges/extended lookback for retention periods
       • 🟢 revamp query runner
       • 🟡 graph fixes (display on dashboards/bar charts)
       • 🟡 breakdowns
       • 🟡 custom date ranges for retention return buckets
       • 🟡 related charts
       • 🟡 update docs
       • 🟡 Revenue Retention
       • 🛑 connect to data warehouse
     • Data management / Non-existing tools
   • [Sri] Taxonomic Filter Improvements
     • Better organized, easier to use
     • Information about properties (schema and statistics)
   • Make other non-event sources a first-class citizen of the insight ecosystem
     • [Hamed] Data warehouse data management
   • Metric to track - Reduce usage of HogQL as a workaround/crutch for missing UI features

2. [Anirudh] 🛑 Small Goal: Alerts v2

   • Alerts on funnels
   • Notifications through Slack

3. [Sandy] 🛑 Small Goal: Shared dashboards with passwords

4. [Sandy & Anna] Research Goal: Understand activation and contraction

5. [Sri] RBAC Collaboration

Retro

Support hero: @aspicer @thmsobrmlr

• 🟡 [Thomas] Improve user paths insight:
  • Improve visual styling
  • Implement "Other (i.e. all remaining values)"
  • Improve path cleaning filters
• 🟢 [Thomas] Onboarding Hamed
• 🛑 [Sandy] Funnel Improvements
  • Filters in exclusion steps
  • Optional Steps
  • Time to convert trends
• 🛑 [Sandy] Analyze support load
• 🟢 [Sri] Ramping up and helping with support
  • Actors query fixes for first time user matching
• 🔴 [Anirudh] Breakdowns on retention
• 🟢 [Anirudh] Speeding up load time of large dashboards
• 🟡 [Hamed] Onboarding tasks
  • Fix Hourly graphs label
  • Fix routing for project/team switcher

Sprint Plan

Support hero: @anirudhpillai @Sriram-bk

• [Thomas] Improve user paths insight:
  • Improve visual styling
  • Implement "Other (i.e. all remaining values)"
  • Improve path cleaning filters
• [Sandy] Funnel Improvements
  • Filters in exclusion steps
  • Optional Steps
  • Time to convert trends
• [Sri] Improve stickiness insight:
  • Plan
• [Sri] "Favorite" Taxonomic Filters
• [Sri] RBAC Collaboration Planning
• [Anirudh] Breakdowns on retention
  • Graph fixes
• [Anirudh] Efficiency of cache warming
  • Instrumentation for dashboard cache hits/misses
• [Hamed] Custom columns for events on data management tab
• [Hamed] Loader for Taxonomic Filtering
• [Hamed] Add data warehouse tab in Data Management
• [Hamed] Insight fixes
  • fix label for funnel graphs

[pauldambra]

Team Retain-you

Support hero: @pauldambra

Retro

• i'll just repeat mine
  • OMG support load @pauldambra
  • CI has been horrible @pauldambra
• not convinced we can get through all of our goals given other distractions @annikaschmid
• worried about support and rrweb distractions @veryayskiy

## what we shipped

High priority

• 👩‍🔬 Goal 2: Churn and retention exploration
  • ✅ formalise first version of replay churn metrics @veryayskiy
    • in https://us.posthog.com/project/2/dashboard/26089
• 🟡 🎤 Goal 3: Watch less and get more value shipping chat
  • ✅ get some test users on "chat with replay" @veryayskiy
  • ✅ how do we do "AI" opt-in settings @veryayskiy
• 🟡 🎤 Goal 3: Watch less and get more value making filters better
  • split saved filters and playlists @veryayskiy (with @pauldambra supporting)
    • started
• 💀 Goal 4: Squash distractions @pauldambra
  • move E2E tests from Cypress to Playwright - #DevEx
  • 😵 re-bundle rrweb without post-css so we can test our own built in recording

Side quests and lower priority

• 🟡 🎤 Goal 3: Watch less and get more value
  • 😵 link from analytics (particularly funnels) to replay @pauldambra

OKRs 🟡

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

• ✅ 🚀 Goal 1: Get Alex rocketing
• 🟡 👩‍🔬 Goal 2: Churn and retention exploration
  • talking to users and picking metrics
• 🟡 🎤 Goal 3: Watch less and get more value
  • in the short term, looking at playlists and filters to see what we can get
• 🟡 💀 Goal 4: Squash distractions
  • need support to be less tricky-things-heavy

High priority

• 👩‍🔬 Goal 2: Churn and retention exploration
  • PLAYLIST COUNTERS - can we process all playlists that have filters (Saved filters) once a day so we can say "X new recordings in the last 24 hours" @pauldambra
• 🟡 🎤 Goal 3: Watch less and get more value making filters better
  • split saved filters and playlists @veryayskiy (with @pauldambra supporting)
• 💀 Goal 4: Squash distractions @pauldambra
  • move E2E tests from Cypress to Playwright - @pauldambra
    • get as much as possible done
    • but also get other folk set up to keep this going

Side quests and lower priority

• chat with recordings - getting feeback / fixing bugs

what might we do? -> https://posthog.slack.com/archives/C03PB072FMJ/p1739953734791699

[Twixes]

Team AI PM

Support hero: @Twixes

OKR

Replace 10 full-time data analysts around the world with AI

Retro

• ✅ Side panel Max across the app @Twixes
• 🔁 Natural language "Add insight" on dashboards @Twixes replaced by docs retrieval
• 🟡 Semantic search on actions @skoob13 experimented with approaches, actual implementation path ready
• 👆 Max able to use actions @skoob13
• 🔴 History of conversations @skoob13
• ✅ Investigate Django 5.0 upgrade for straightforward "Stop response" button @skoob13
• ✅ More user feedback @skoob13 @Twixes

High priority

• Semantic search on actions MVP shipped @skoob13
• SQL insights support (based on current code from the SQL editor) @Twixes
• Natural language "Add insight" on dashboards @Twixes
• History of conversations @skoob13
• Fix other issues identified in our Feedback review @Twixes @skoob13

Low priority / side quests

• Prototype integrating @PostHog/team-replay's recordings search into core Max (RFC on how teams can add Max skills)

[joshsny]

Team Growth

Support hero: week 1 - @joshsny , week 2 - @zlwaterfield

OKR

Goal 1: Make it easier for users to onboard into multiple products
Goal 2: Understand better how user's are using multiple products
Goal 3: Make setting up the PostHog SDKs easy

Retro

• 🟡 Redo first page of onboarding (include all sources, highlight invites, search and other improvements)
• ✅ Redo plans page in onboarding and launch experiment for it
• ✅ Clean up growth dashboard (add all onboarding products, fix incorrect funnels & trends)
• 🟡 Remote config for session replay masking
  Support hero - week 1

High priority

• Get to a useful POC of using AI to setup PostHog SDKs @joshsny
• Data warehouse experiment in product analytics onboarding @joshsny
• Finish off session replay privacy in onboarding @joshsny
• Improve/add activation metrics for other products @joshsny
• In-app credit card flow @zlwaterfield

Low priority / side quests

• Explore demo data usage

[fuziontech]

Team ClickHog

Objective

Goals for Q1:

• Query Scheduling Service
  • Paid API use case is covered
  • We should have all queries running through this
  • Basic load shedding
  • Differentiate API queries based on $
• Iceberg continuation
  • Keep on top of Altinity builds for CH
  • Query logs into Iceberg
  • Ingestion pipeline work (monitoring & automation)
• Cluster topology consolidation and cost reductions
  • We are on one cluster
  • Query performance is equivalent
  • Costs are down
  • Schema management
• Ongoing HogQL/Performance improvements
  • Query Scheduling
  • Productizing Performance Tooling
  • Better query attribution (in query comments)
    • By end of query we do not run queries with no annotations
    • Some sort of Type for queries that will run

Board

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

Retro

🔥 Incidents 🔥

Happy cluster. Happy Life.

Last Sprint's Goals

• Duplication investigation @tkaemming ⬇
• Expose estimate for queries on API @orian 🧊
• Expose whether or not a new query is utilizing indexes @orian ⬇
• Start getting users on Query API and iterate & learn @orian ✅
• Clickhouse in K8s @Daesgar ⬇
• Stand up EU Offline replica set @Daesgar ⬇
• Backups to Dagster @fuziontech ⬇
• Metabase dashboard for delete compliance @fuziontech ⬇
• Clean up weekend EU disk alerts @fuziontech @Daesgar ⬇
• Investigate Person Properties into a map (similar to event props) @tkaemming ✅
• Look into slack sensor on Dagster for alerting on compliance job @fuziontech ✅

This Sprint's Goals

TL;DR

• Duplication investigation @tkaemming
• Expose whether or not a new query is utilizing indexes @orian
• Clickhouse in K8s @Daesgar
• Finish standing up EU Offline replica set @Daesgar
• Backups to Dagster @fuziontech
• Metabase dashboard for delete compliance @fuziontech
• Clean up weekend EU disk alerts @fuziontech @Daesgar
• Backfill Person Properties into a map on US @tkaemming
• HogQL printer/ast/visitor improvements @orian
• Turn on/off logic/button for "Query as a Service" @orian

[zlwaterfield]

Team Dollars & Cents

Retro

Retro items

• @zlwaterfield
  • Support week 1
  • RBAC
    • ✅ fully roll out for team 2
    • ✅ misc improvements / fixes from team
    • ✅ roll out to % of new users
    • ✅ think more about enterprise add-on
  • 🏗️ customer.io emails set up for posthog (if time, get 2fa emails flowing)
  • 🏗️ metabase -> posthog move complete, this includes the DW view for invoice with annual
  • 🏗️ explore dagster more for usage reports
• @patricio-posthog
  • Support week 2
  • ✅ Finish Mobile Replay Pricing (backend almost there, needs mostly migrations for current customer, frontend needs some tweaking)
  • ✅ Check again Forecasting, it's jumping too much.

Q1 2025 Objectives

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

• 🟡 Usage dashboard (Pato)
• Pricing changes(Pato)
  • ✅ Finish Mobile Replay pricing
  • 🟡 Clean up billing for identified / unidentified events
  • 🟡 Query API pricing
• 🟡 RBAC (Zach)
• 🟡 Enterprise add-on (Zach)
• ⚪ Improve SAML (Zach)
• 🔴 Move core RevOps flows off of Zapier into the billing system (tbd)

Extras (nice to haves if we have time or feel inspired)

1. 🟡 Postgres (pgbouncer + read replica) - infrastructure handling this
2. 🟡 Self serve account deletion
3. Case insensitive emails
4. 🟡 Move all transactional emails to Customer.io
5. 3D Secure improvements - email flows
6. 🟡 Move revenue dashboards from Metabase into PostHog
7. Get credit cart input experiment over the line
8. Billing endpoint performance improvements (split up)
9. Proper callbacks for time-sensitive checks
10. 🟡 Usage reports in Dagster

This sprint

Time off: Mine (3/3), Pato (3/3-3/4)

• @zlwaterfield
  • on call week 1, with Mine in person for 2 days
  • ✅ get customer.io over the line
  • RBAC
    • ✅ improve pay gates on access control component
    • ✅ fix team config access for members in private projects
    • roll out to 20 more teams/enterprise customers
    • access control bulk changes
  • ✅ support for startup plan extensions
  • check in on startup form
  • improving loading of available features after upgrading
  • 🟡 review logs for quota limiting
  • 🟡 add forecast value to top of billing page to reduce confusion
  • nice to have
    • get v1 of Dagster PR out - waiting on James
    • work on teams unsub - showing features they are using and turning off features
    • 🟡 Metabase to PostHog move
• @patricio-posthog
  • 🟡 fix revenue issues (mostly annual invoices) (w/ Zach's help, need to migrate it to a Python script)
  • 🟡 kick off new pricing for identified events (independent vs anon events) (Had a call with Raquel, going to work on RFC)
  • start improving forecasting with new ideas
  • support Pawel's new query pricing
  • 🟡 how billing limits are working (working on the fix for this)
• @minekansu
  • 🟡 sales growth review [v1 sheet](https://docs.google.com/spreadsheets/d/14GdsNILsIC5gtNa_vxlsxKPiOQSlVtg- V7vZ5zrwgFQ/edit?usp=sharing)
  • 🟡 harmonic contract and implementation to sync with salesforce
  • ⚪ weekly revenue update query cleanup (move all to posthog, share feedback with dw team)
    document basic definitions for revenue lifecycle stages (esp churn)

[mariusandra]

Got confused and forgot to post this a week ago. This is our planning for the current week and the next.

Team Hog XP

OKR

• 🟡 Build a framework where we can have 50+ products? @mariusandra
  • 🟡 Defining and splitting the common layer from the rest of the apps
  • 🟡 Defining and implementing boundaries between apps
  • 🟡 UX changes to support the new structure
  • ⚪ Every product is able to export operations (backend) and widgets (components) => AI, notebooks etc.
  • 🟡 Testing independently - if you change things on one product, we only run tests for that product
• 🟡 Levelling up our product quality. @adamleithp
  • Design system that is self documenting
  • Mobile support
  • Finally figure out (explain) modals vs drawers
  • More standardised components
• 🟢 Anti-goal for Q1: @corywatilo
  • Fixing CI when it randomly breaks (each team owns their tests)
  • Rewrite everything
  • Implement everything ourselves

Retro

• Marius
  • 🟢 Initial PR (or RFC) for "tree view" backend
  • ⚪ Keep on building (most moved to this sprint)
    • Run as many tests tests in CI with turbo affected as we can
    • Extract, bundle and test products separately from the rest of the frontend (and app in general).
    • Package lemon-ui as a separate package
    • Integrate products in languages (python, rust) into turborepo
• Cory
  • 🟢 Work on designs, build higher fidelity mockups (search, sidebar, etc)
• Adam
  • 🟡 Work on implementing designs (did various small tasks and bugfixes)

High priority

This is for the ongoing week and the next one

• Cory
  • Fine tune the new layout / sidebar
• Adam
  • Implement the new layout's frontend (design & interactions, dnd, etc)
• Marius
  • Implement the new layout's backend (file tree backend persistence, new node sync)
  • Make our tests not suck

Low priority / side quests

• Marius
  • Continuous Hog/QL support

[MichaelKutsch-ph]

Team infra

Support: @MichaelKutsch-ph @frankh

Retro

High priority

• ✅ Move Django apps to new chart version: We actually moved all posthog apps, only migrations and non-posthog app related things are left
• 🟡 ArgoCD only workflow @MichaelKutsch-ph : more complex as we thought, but there is a PoC for rollingSync
• ✅ Move Django apps to new chart version: decide @danielxnj
• ✅ continue argoCD alerts with prometheus alerts instead @bciaraldi
• 🟡 Infra Costs @MichaelKutsch-ph
• 🟡 Prep Warpstream for go-live @frankh
• ✅ (not live yet) Kafka failover to s3 @frankh - we're not sure if it's smart to merge it, considering the other measures that we're taking

Low priority / side quests

• ⚪ move old capture to new capture @MichaelKutsch-ph
• 🟡/🔴 Evaluation of Robusta.dev (better alerts, AI and fancy things...) - kill

OKR

1. 🏃 Next level ArgoCD - Continuous Delivery
2. ☁️ 🕸️ Scalable networking
3. 💰 Mr. Bezos, bring down those costs!
4. 🎮 A stable pre-prod environment

High priority

• ArgoCD improve DX for rollingSync @MichaelKutsch-ph
• (maybe) Move apps to RollingSync @MichaelKutsch-ph
• Move non-capture steps to Warpstream @frankh
• Move last services from posthog chart to new chart (migration, ingestion) @danielxnj
• new notifications for deployments in argo @danielxnj
• helping to get dagster up @bciaraldi
• karpenter upgrade among other upgrades @bciaraldi
• plan central grafana / alerting? (maybe)

Low priority / side quests

• move old capture to new capture @MichaelKutsch-ph

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

[robbie-c]

Team Web Analytics

Support hero: @robbie-c + @rafaeelaudibert

OKRs

• 🟡 Finish cookieless mode
• Build marketing analytics
  • 🟡 Add revenue data to web analytics
  • 🟡 Get ad spend data into data warehouse and use it for per-channel analytics
• Build per-page reports
  • 🟢 Core web vitals

Retro

@lricoy joined!

• 🟢 Web analytics cross selling @rafaeelaudibert
• 🟢 CDP destinations for reddit (pixel & conversions API) @robbie-c
• 🟡 Host + device type selector @rafaeelaudibert
• 🟢 Add icons for browser / device type / os @lricoy
• 🟢 Sped up the non-clickhouse part of clickhouse queries by 600-800ms, improved timings measurement @robbie-c

Next sprint

High priority

• dogfood reddit & snapchat pixels, fix problems @robbie-c
• Cookieless next steps - decide endpoint @robbie-c
• Page reports @lricoy
• Finish Host selection UI @rafaeelaudibert
• Clickhouse dictionary for currency @rafaeelaudibert
• add a CDP function to block CIDR IP address ranges @robbie-c

Low priority

• improve docs (e.g. docs on bounce rate) @lricoy
• CSP violation report @lricoy

[benjackwhite]

Team CDP

• Support: @meikelmosby

Retro

• ✅ Onboarding Eli! (everyone)
• 🔴 Delete plugins code @benjackwhite
• 🔴 Delete onevent and webhooks services @benjackwhite
  • 🟢 Migrate Zapier stuff to Hog Functions (this allows us to finally kill webhooks services)
  • 🔴 Desire to validate legacy plugins way more due to issues we had with transforms
• 🟡 Read the new S3 data for comparison and write the relevant data to Clickhouse @pl
  • Some work here but support became the focus
• 🟢 UX improvements to release customisable hog transformations @meikelmosby
  • 🟢 Top 5 common requests that could be solved with new transform templates
  • 🟢 Making editable transformations a reliably experience
• 🔴 Move existing destination templates into nodejs @MarconLP
• 🟡 Put up TikTok and Bing pixel site destinations @MarconLP

Out-of-plan

• Generally detoured into fixing the issues related to the oauth failures and increased support workload
• WS moved up priority due to MSK running out of space
• Property defs API additions as focus for Eli (goal to get it pulled out into its own DB)

Discussion

OKRs

• 😍 People choose us for their CDP first 🟡
• 🖕 Plugins be gone 🟢
• 🚀 Warpstream for events 🟢
• 🎈 Write-optimized session replay ingestion 🟢
• 💪 We make changes and improvements to the Node services with confidence 🟢

High priority

• Rollout Logs and Testing tools for retrying failed functions @benjackwhite @MarconLP
• Get GeoIP moved to using S3 mounted bucket (makes it more deterministic) @benjackwhite
• Return to the purge @benjackwhite
• Make the Hog Function API public and that the documentation isn't too bad @meikelmosby @pl
• Add legacy plugins comparison logic to validate it is all 1-1 @meikelmosby @benjackwhite
• Move over to WS with Infra peeps @benjackwhite
• GET requests for prop defs go via API and not the DB @eli-r-ph
• Focus on finishing integrations @MarconLP
  • Google ads work (nested accounts)
  • Slack app submission finalised
  • Release Reddit / snapchat with warning about rate limit
  • TikTok
  • Intercom
• Move existing templates to Nodejs @MarconLP
• Feature parity with Blobby v1 @pl
  • Get Team 2 reading from Blobby v2
  • Parity with Blobby v1 for events tables
  • Comparison testing to ensure all end data is the same as before
  • Realtime polling from client for S3 data

Low priority

• Load test the hog function based transforms to ensure it is release ready @meikelmosby
• Add RBAC to Hog Functions? @PostHog/team-cdp
• Release polyfilled plugin creation API to stop new plugins being made