Team Extensibility release 1.25.0 bis

[mariusandra]

Spillover to finish still this week:

• Get rid of event_names: [], event_properties: {}, etc - Improve the events stats database schema posthog#3726 (Marius)
• Get the basic retry queue fully tested and running on cloud (with the postgres backend) - Retry queue #325 (Marius)
• Clean up all the old ingestion code. (Michael)
• Get the plugin logs live (Michael + Karl)

---

Next sprint bigger plugin work:

• Add more retry queue backends (S3, clickhouse) (Marius) Retry queue #325
• Add support for automatic retries of processEvent and other functions (Marius) Kafka last mile batching & retrying processEvent #273
• Split processEvent and onEvent, create onSnapshot (Yakko) Add onEvent #328
• Move event->action mapping to plugin server. Move webhooks over. Implement onAction (Michael) Match actions to events on the fly #235
• Plugins during the onboarding flow? Introduce plugins into the onboarding flow posthog#3764

New plugins and updates: (Yakko & Marius?)

• Downsampling Plugin for pilots/trials that downsamples data posthog#3365
• PostHog to PostHog Plugin request: send event data to a different PostHog instance plugin-repository#19
• Postgres export Plugin request: Postgres plugin-repository#11
• Fix rudderstack export Plugin request: Rudderstack export plugin-repository#15
• Solidify first time event tracker and maybe add to core First time event tracker in core PostHog? #315
• Add session end to session tracker plugin Add a scheduled task to end open sessions session-tracker-plugin#1

Integrations -> Python (Yakko?) & Ruby (Marius?).

• python: $set_once to the python library Add $set and $set_once support posthog-python#23 and sentry support Add python sentry (and sentry & django) integrations posthog-python#13 and other missing features
• ruby: add feature flags, $set and $set_once, modernise what can be modernised

[yakkomajuri]

Ok so I'm happy to pick up what was laid out for me here, but with the caveat of low expectations, given I'm off Monday, will be support hero next cycle and still have onboardings to do.

I'd prioritize:

1. onEvent Add onEvent #328
2. $set_once + Sentry to Python lib
3. Building more plugins if time allows

Other thins I'd like to highlight, for this release or next:

• Session recording enable/disable method? posthog-js#214
• Retry Requests posthog-js#199
• Full API support inside plugins: I need to write up an issue with some ideas for this, probably something I can tackle the cycle after

[yakkomajuri]

As for spillover, I also have #322 and #324. I believe #327 is getting in when tests pass

[Twixes]

Personal list for now, in decreasing order of workload (will see what I manage to cross out on Friday still):

• Definitely can look into an onAction implementation but it not a trivial thing, and not compatible with an MVP approach – it must work just and exactly as well as currently in Django, else it's a regression. So I'll spec this out exactly (one thing that I could have done better when porting ingestion – while the task is simple to describe, the scope of implementation is actually large, and various intricacies matter).
• Make the GeoIP and first event tracking plugins preinstalled, with plugins shown during onboarding.
• Get example plugins in order – hello world and the starter kits I made some time ago (which weren't really very useful).
• Finish data sendoff plugin from PostHog Cloud to playground.
• set_once GeoIP data on persons.

Then from other things, plugin logs and deprecated code removal are done, just need to merge (most importantly logs require coordination with infra before merging – we should be fine with a bit of a wait though).

[mariusandra]

All right, thanks for the input! I have added our combined thoughts into the next release: PostHog/posthog#4089