Like what you see and self-hosting? Update your instance.
First our updates and new features.
Also as you will see below we have added Celery workers, we’ll move tasks to workers to speed up a lot of actions in PostHog so we've updated the upgrade docs too.
Updates and performance improvements this week have focused on making PostHog easier to use in small but powerful ways.
This is perhaps the most exciting change to PostHog in this release, we have explained the important reason for creating a distinction between Actions and Events.
Several users pointed out they shouldn’t have to create a distinct Action for a normal event like a pageview for example – PostHog was making it difficult to get to the information they wanted quickly.
Within Trends users can now filter by events and/or actions, multiplying the data that you can now see and manipulate within Trends.
Since we launched this has been one of our longstanding issues (22 February to be exact) – we had neither the capability to change an existing password or reset if we had forgotten.
These small changes make this possible and should stop people getting stuck for simple reasons.
Coupled with the above you can now authenticate your login through GitHub or GitLab making it even easier to login.
Aaron was so used to typing /logout he did not realize how frustrating not having a logout button can be.
It had been pointed out several times that having a username in the top right corner of PostHog made it seem like it was a logout button, it wasn’t but now is.
We released Stickiness with #1.0.9, whilst it is explained in our docs and youtube channel it is important to make sure people can understand the Trend Graphs whilst they are in front of them.
James thought it wasn’t clear that the repeated action is over a time frame (some actions that are important do not need to be repeated on consecutive days or perhaps over weekends).
So having a sentence here should mean that PostHog users infer the right conclusion from their data.
This is so we can create slack messages, recalculate Actions for large deployments, store events, and prefetch and cache Funnels.
So there will be a couple of things to watch out for this week as a result of this pr, every deployed app will provide a REDIS_URL to posthog. This will be used by celery to run background tasks.
You will also see the below message – as with next week’s release you will need a background worker to get PostHog working properly.
This is one of the most impactful updates to PostHog so far – whenever we did a query involving actions in the frontend, the database had to do a lot of heavy lifting to calculate which events match the action.
This led to long loading times as well as timeouts – now this works much faster and should be a joy to work with even with large Action volumes.
For a full breakdown of the changes and updates, please see our changelog.
This was one of 4 issues raised by jeremynevans at Savvy – it was raised in our community page and resulted in an excellent conversation with Tim resulting in more feature requests which is amazing.
He is also using PostHog for analytics on Crowd Cure to help build the largest clinical trial dataset to yet to help with the Coronavirus crisis – check it out on Producthunt.
As mentioned above this was a long standing issue and big gap. Excellent and quick work from an amazing contributor, thank you Gzog!
We'd love to hear anything you have to say about PostHog, good or bad. As a thank you, we'll share some awesome PostHog merch.
Want to get involved? Email us to schedule a 30 minute call with one of our teams to help us make PostHog even better!
We migrated our docs so we could host them ourselves – using docsify to generate our site. We’re pleased with it so far and have used it again for our company handbook.
PostHog also got a nice mention as part of an “absurdly powerful and productive ‘low code’ stack” on HN, James was ecstatic. It consisted of:
Want to just try it already?
(Sorry for the shameless CTA.)
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。