You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have metrics.posthog.com, which offers crucial performance information, but is a solution separate from PostHog itself. Otherwise we don't offer any metrics, which makes detecting and explaining PostHog instance problems more time-consuming for users and also for the core team.
Describe the solution you'd like
PostHog could use an instance status-type page (accessible only to organization admins on Self-Hosted or is_staff users on Cloud [or is_superuser? this distinction is actually useless for us]). For example, we could easily show database statistics like numbers of rows or table sizes, Redis health, event ingestion load – essentially data that comes up useful when users ask about problems.
Describe alternatives you've considered
Tell users to investigate instance internals themselves.
Additional context
Thought of this when a user needed to know why their PostHog Docker container was taking up so much space. I've told them to query for table sizes:
SELECT relname as"table", pg_size_pretty(pg_total_relation_size(relid)) AS"size"FROMpg_catalog.pg_statio_user_tablesORDER BY pg_total_relation_size(relid) DESC;
but it'd be much simpler if this information was available in the UI.
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered:
* System Status page and API (#1812).
* More resilient to Redis outage. Ensure the table gets loaded.
* Bugfix and reworded.
* Using kea-typegen now and removed a " ".
Is your feature request related to a problem?
We currently have metrics.posthog.com, which offers crucial performance information, but is a solution separate from PostHog itself. Otherwise we don't offer any metrics, which makes detecting and explaining PostHog instance problems more time-consuming for users and also for the core team.
Describe the solution you'd like
PostHog could use an instance status-type page (accessible only to organization admins on Self-Hosted or
is_staff
users on Cloud [oris_superuser
? this distinction is actually useless for us]). For example, we could easily show database statistics like numbers of rows or table sizes, Redis health, event ingestion load – essentially data that comes up useful when users ask about problems.Describe alternatives you've considered
Tell users to investigate instance internals themselves.
Additional context
Thought of this when a user needed to know why their PostHog Docker container was taking up so much space. I've told them to query for table sizes:
but it'd be much simpler if this information was available in the UI.
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered: