feat: Added client side capture rate limiting

[benjackwhite]

Changes

Needs PostHog/posthog#21388

We want to protect ourselves and our users from abnormal client behaviour. This can be anything from an accidental loop in the code to someone running some strange scripts in the browser to a bug.

• Adds the client side check for capture
• Logs a message
• Make the configs configurable
• Persist to storage (which handles page load unload loops)
• Adds a $$ event when the rate limit kicks in

Checklist

• Tests for new code (see advice on the tests we use)
• Accounted for the impact of any changes across different browsers
• Accounted for backwards compatibility of any changes (no breaking changes in posthog-js!)

[github-actions]

Size Change: +5.58 kB (+1%)

Total Size: 968 kB

Filename	Size	Change
dist/array.full.js	231 kB	+1.4 kB (+1%)
dist/array.js	129 kB	+1.4 kB (+1%)
dist/es.js	129 kB	+1.4 kB (+1%)
dist/module.js	129 kB	+1.4 kB (+1%)

ℹ️ View Unchanged

Filename	Size
dist/exception-autocapture.js	12.2 kB
dist/recorder-v2.js	108 kB
dist/recorder.js	108 kB
dist/surveys-module-previews.js	62 kB
dist/surveys.js	58.3 kB

_{compressed-size-action}

[pauldambra]

is it missing a commit? ratelimiter has no "bucket"

[pauldambra]

ran it locally
captured 100k events in a loop
only ingested 291
saw logs in the console

🚀

only "improvement" I can think of is a heavily debounced internal event or custom rrweb event in recording maybe that we throttled to help with support but that's very much polishing and not blocking

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[benjackwhite]

This is a bit stuck in limbo atm due to the inability to filter out these internal events from usage reports... Wondering about changing the logic instead on pipeline filter out the event (maybe make it a specific one called $$ingestion_warning or something).

@xvello ideally I'd leave this more to pipeline to decide on the best approach / point in time to do that filtering. Either I can keep this PR on hold until something like that is ready, or merge without the rate limit event. Thoughts?

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.