-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: New grouped invocation logs view #29131
Conversation
Size Change: 0 B Total Size: 9.72 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
This PR introduces a new grouped invocation logs view for hog functions, enhancing the logging experience with invocation-based grouping and expanded functionality.
- Added new
HogFunctionLogs
component infrontend/src/scenes/pipeline/PipelineNode.tsx
that groups logs by invocation ID - Implemented expandable rows to load older/newer logs when clicked
- Added filtering capability to show invocations where any result contains the search term
- Fixed bug in
posthog/api/hog_function.py
that was resetting bytecode when the hog field wasn't included in requests - Added retry button functionality for errored events
2 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile
return { | ||
event: { | ||
uuid, | ||
distinct_id, | ||
event, | ||
properties: JSON.parse(properties), | ||
timestamp, | ||
url: '', | ||
elements_chain: '', | ||
}, | ||
person: { | ||
id: person_id, | ||
properties: JSON.parse(person_properties), | ||
url: '', | ||
name: '', | ||
}, | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will break retries for functions that are using group, project, or source values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's true 🤔
Although the intention was to get that stuff done via the API rather than rebuilding everything client side which is a little less reliable.
In reality almost nothing uses those elements but still should fix it...
Problem
The logs view is somewhat limited as it is just a list without any grouping.
This modifies it to allow grouping by instance_id (invocation)
Changes
TODO
FOLLOW UP
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
Does this work well for both Cloud and self-hosted?
How did you test this code?