User property for self-hosted deployment host #2138
Labels
enhancement
New feature or request
Comments
macobo
changed the title
macobo
added a commit
that referenced
this issue
Nov 10, 2020
* Refactor status report task, add tests Also discovered issue #2255 * Refactor status report further * Add DEPLOYMENT env variable to instance status report Related issue: #2138 * Report posthog_event and posthog_session_recordingevent table sizes This will help with doing some product decisions * Fix instance status report person numbers Fixes #2255 * Handle exceptions in status report * count(*) fix
|
We now have this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
As an analytics company, we rely on analytics to drive our product.
We currently know if users are using cloud or are self-hosted, but it would be great if we also knew what platform they were using. This helps us prioritize issues around different deployments or see if some are performing exceptionally well.
Describe the solution you'd like
Each user should have a
deploymentuser attribute, e.g. ascloud,aws-cloudformation,heroku, etc.This can be done by passing a env variable to user properties if user did not opt out of capture.
Describe alternatives you've considered
Measuring "one-click" deploys. However, having both is valuable, even if to see if users finish the deployment.
The text was updated successfully, but these errors were encountered: