feat(insights): compare legacy and hogql insights #18628
Conversation
|
Size Change: 0 B Total Size: 2.01 MB ℹ️ View Unchanged
|
|
This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the |
|
This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the |
|
This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the |
|
This PR was closed due to lack of activity. Feel free to reopen if it's still relevant. |
|
This is just a management command that's not run from anywhere, but is useful when comparing HogQL results between teams. Let's get it in, and possibly expand with other queries as we finish them. |
| from posthog.hogql_queries.query_runner import get_query_runner | ||
|
|
||
| insights = ( | ||
| Insight.objects.filter(filters__contains={"insight": "LIFECYCLE"}, saved=True, deleted=False, team_id=2) |
There was a problem hiding this comment.
Why team 2? For me it's 1.
There was a problem hiding this comment.
That's what we have in production on the US cloud. The next version of this query should just check for all teams.
Oh, seems like you found a bug: lifecycle insights with cohort filters fail. Will fix. |
Ah, I just got super confused since it works in the frontend. Turns out it's one of my insights, but not the one I created right before. |
|
Fixed here: #19501 |
Problem
We want to launch HogQL trend and lifecycle insights. We also want to make sure the data is the same between the two.
Changes
Adds a management command that compares a set of lifecycle insight results.
How did you test this code?
I ran this in the python shell directly. I'll keep tweaking and running it like that for now. This PR is just a snapshot and likely won't get merged.