You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 4, 2021. It is now read-only.
If we match fully processed events to actions in the plugin server (in parallel with saving the event to DB), we'll be able to again have asynchronous events>actions matching. Even more importantly, we'll be able to support method onAction(action: Action, event: PluginEvent) on plugins, facilitating making webhooks a plugin. In the long run something like PostHog/posthog#3357 may be built on top of this.
The text was updated successfully, but these errors were encountered:
How much effort will this be? I guess we need the entire filtering logic (that is probably already implemented twice in django? Once for postgres and once for clickhouse?)... into JS. Sounds like a lot of meticulous work...
The logic is actually common, because we perform matching on a temporary event created in Postgres (as storing action definitions in ClickHouse is a pain).
If we match fully processed events to actions in the plugin server (in parallel with saving the event to DB), we'll be able to again have asynchronous events>actions matching. Even more importantly, we'll be able to support method
onAction(action: Action, event: PluginEvent)
on plugins, facilitating making webhooks a plugin. In the long run something like PostHog/posthog#3357 may be built on top of this.The text was updated successfully, but these errors were encountered: