Hello!

My company, Chroma, is a Posthog user. One of our action items from a recent incident is to better filter our Posthog events. This filter seems to be the recommended way to do so.

We'd like a way to add logical operators in filters, for example to filter if condition_1 OR condition_2 OR (condition_3 AND condition_4). I believe this is the only way for us to get the filtering behavior we want.

(Issue submitted in this repo since the forked repo doesn't seem to have an issues tab)

I've been testing out this plugin to potentially add to a tutorial I'm writing, and no matter the schema I enter, it seems to be filtering all of the events.

It is processing events and not raising any issues. An empty schema is allowing events to be injested, but no matter the what schema I tried (from very basic to multi-step), the app seems to filter all events out.

Some potential issues and fixes:

1. I could be misconfiguring the schema. For example, using pathname to filter an autocaptured event instead of $pathname if the app doesn't handle for that.
2. Instead of defaulting to filtering event if it doesn't pass the checks (or error), you could set it to return the event.
3. Better logging or errors for when an event gets filtered.

Let me know if I'm missing something.

Description

Hi there, I applied the following config:

[
  {
    "property": "$ip",
    "type": "string",
    "operator": "is_not",
    "value": "<some_ip_address>"
  }
]

However all new events are dropped with this configuration. Have I done something wrong?

My goal is to drop events from a particular ip address