disable hogql insight trends #20
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
📸 UI snapshots have been updated64 snapshot changes in total. 0 added, 64 modified, 0 deleted:
Triggered by this commit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR
PostHog is currently transitioning and testing its analytics endpoints to utilize the
/query/endpoint (via hogql). WhenSELF_CAPTUREis set to False, PostHog will invoke the/decide/endpoint, enable thehogql-insights-trendsfeature flag, and utilize this endpoint.Currently, dialogs are only loaded through the
/person/trends/endpoint. This is a temporary fix to consistently use this endpoint while a permanent solution for the new endpoint is being developed.