Skip to content
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

Instance status page #1812

Closed
Twixes opened this issue Oct 6, 2020 · 2 comments
Closed

Instance status page #1812

Twixes opened this issue Oct 6, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@Twixes
Copy link
Member

Twixes commented Oct 6, 2020

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 [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" FROM pg_catalog.pg_statio_user_tables ORDER 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!

@Twixes Twixes added the enhancement New feature or request label Oct 6, 2020
@timgl
Copy link
Collaborator

timgl commented Oct 13, 2020

The list of things we should include

  • Event table size (both in MB and Approximate size)
  • Element table size (both in MB and Approximate size)
  • Redis queue size
  • Possibly memory size of workers?
  • Number of events in last day/week

@timgl timgl mentioned this issue Oct 13, 2020
3 tasks
timgl pushed a commit that referenced this issue Oct 15, 2020
* 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 " ".
@Twixes
Copy link
Member Author

Twixes commented Nov 30, 2020

Closed by #1875.

@Twixes Twixes closed this as completed Nov 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants