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.

Sign up for GitHub

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

Jump to bottom

Add a callout for the ingestion queue #9600

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Add a callout for the ingestion queue #9600

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
578172c
Add a callout for the ingestion queue
darkopia Oct 11, 2024
b7faffe
Fix typos
Oct 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions contents/docs/migrate/migrate-from-amplitude.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,6 +213,8 @@ get_entries_from_folder_and_capture(folder_name)

This script may need modification depending on the structure of your Amplitude data, but it gives you a start.

> **Why am I seeing "analytics-python queue is full"?** The default queue size for ingesting is 10,000. If you are importing more than 10,000 events call posthog.flush() every 5000 messages to block the thread until the queue empties out.

> **Why are my event and DAU count lower in PostHog than Amplitude?** PostHog blocks bot traffic by default, while Amplitude doesn't. You can see a full list of the bots PostHog blocks [in our docs](/docs/product-analytics/troubleshooting#does-posthog-block-bots-by-default).

### Aliasing device IDs to user IDs
Expand Down