-
Notifications
You must be signed in to change notification settings - Fork 719
Add Analytics Platform Q1 2026 Objectives #14281
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
Merged
scottlewis-ph
merged 1 commit into
master
from
add-analytics-platform-q1-2025-objectives
Jan 6, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,15 @@ | ||
| ### Q4 2025 objectives | ||
|
|
||
| * Alerts / exports / subscriptions stability <TeamMember name="Andy Zhao" photo /> <TeamMember name="Vasco de Krijger" photo /> | ||
| * Improve observability and alerting | ||
| * Reduce error rate and improve stability using what we learn from the above | ||
| * Unify the insight execution path | ||
| * Schema validation <TeamMember name="Sandy Spicer" photo /> | ||
| * Define and ship a beta / MVP for the schema validation system | ||
| * Query performance <TeamMember name="Robbie Coomber" photo /> | ||
| * Instrument where time is spent while users are waiting for query responses | ||
| * Fix queries that are slow due to JSON property references | ||
| * Implement sessions on events | ||
| * Do everything in the [Query Performance mega-issue](https://github.com/PostHog/posthog/issues/39639) <TeamMember name="Robbie Coomber" photo /> | ||
| * Iterate on schema validation <TeamMember name="Sandy Spicer" photo /> | ||
| * Schema in code | ||
| * Versioning | ||
| * 99.9% uptime for alerts, subscriptions, exports, and query service <TeamMember name="Andy Zhao" photo /><TeamMember name="Vasco de Krijger" photo /> | ||
| * Improve query cache stability <TeamMember name="Andy Zhao" photo /> | ||
| * Move to its own redis cluster | ||
| * Add per-team limits | ||
| * Get on top of support / open github issues <TeamMember name="Vasco de Krijger" photo /> | ||
| * Create high priority list of GitHub issues and do them | ||
| * Re-imagine dashboards <FutureTeamMember href="/careers/product-engineer"/> | ||
| * Let customers define their own dashboard templates | ||
| * Do a hackathon around https://github.com/PostHog/requests-for-comments-internal/pull/941 <TeamMember name="Anna Szell" photo /> | ||
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Do we also want to mention the Terraform provider? Maybe add a bullet: Terraform provider beta hardening / path to GA .
It went into beta last week and showed up in customer requests, so it could fit here but it also fits under “support / open GitHub issues”.
I’m conscious of scope, so this could be a light‑weight “stabilize based on feedback” goal for now to ensure that we can reasonably complete our goals. I have some small improvements I still want to work on (e.g. Github integration) but currently first awaiting the appetite before spending more time here.
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.
We can add it here! With you owning it?
Uh oh!
There was an error while loading. Please reload this page.
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.
Yep, sounds good! 😄