capture creation and deletion events#2363
Merged
Merged
Conversation
lunika
changed the title
Contributor
|
Size Change: 0 B Total Size: 4.32 MB 📦 View Changed
|
AntoLC
approved these changes
May 29, 2026
The posthog information were only available using the POSTHOG_KEY settings. We split it in POSTHOG_KEY and POSTHOG_HOST to use them with the pyhton posthog sdk
lunika
force-pushed
the
backend/capture_event
branch
from
5953104 to
8c3c99b
Compare
Reflect the changes made about posthog by the backend application. The posthog config is split in POSTHOG_KEY and POSTHOG_HOST properties.
lunika
force-pushed
the
backend/capture_event
branch
from
8c3c99b to
e10f9b3
Compare
We want to capture event with posthog. We created a utils for this reposible to send the event or not if posthog is configured.
When a document is created and deleted, we capture an event and we send it to posthog.
We want to capture an event every time a user logs in.
We want to capture an event when a document is duplicated. The document from where come from the duplication is added in the properties.
We want to capture an event when a file is imported. We add in the properties the type of file imported and if it is in the create-for-owner api call.
We want to capture an event when a user flag a document as a favorite.
When an AI action is called from ai_translate, ai_transform and ai_proxy, an event doc_ai_action is captured with a method property giving the information from where it is called.
When an access is created we want to capture an event.
When an access is deleted we want to capture an event.
When a new thread is created, we capture an event related to this thread creation.
When a new comment is created, we capture an event related to this comment creation.
When a document is moved we want to capture an event. The position and target_document_id is added to the sent properties.
When a user leave a document, we want to capture an event.
lunika
force-pushed
the
backend/capture_event
branch
from
e10f9b3 to
1ebc8d5
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Purpose
We want to capture some events in the backend application. We are starting with capturing when a document is created or deleted. For this we use the PostHog SDK, and we created a dedicated helper.
Proposal