feat: Posthog events bootstrapping #160
Merged
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.
Description
This PR does a few things:
DistinctID
for events. This ID is stored locally in~/.pizza-cli/telemetry.json
. Users can always delete this file or entirely disable telemetry via the global--disable-telemetry
flag-tags telemetry
flag) which bootstraps the events for Posthog. Why is this needed? You can't really make a dashboard in Posthog until an event has landed in the data lake. This simplifies this process by sending the events all at once to Posthog to make dashboard creation easyhttps://us.i.posthog.com
Related Tickets & Documents
Followup to #147
Tier (staff will fill in)