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.

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

DOC-274 #299

Merged
merged 2 commits into from
Sep 26, 2024
Merged

DOC-274 #299

merged 2 commits into from
Sep 26, 2024

Conversation

markzegarelli
Copy link
Member

No description provided.

Copy link

vercel bot commented Sep 25, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
amplitude-docs ✅ Ready (Inspect) Visit Preview Sep 25, 2024 10:59pm

Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-299.d2yiv7onwgut1v.amplifyapp.com

@@ -11,4 +11,5 @@
- Session quotas reset on the first of every month.
- Use sample rate to distribute your session quota over the course of a month, rather than using your full quota at the beginning of the month.
- To find the best sample rate, Amplitude recommends that you start low, for example `.01`. If this value doesn't capture enough replays, raise the rate over the course of a few days. For ways to monitor the number of session replays captured, see [View the number of captured sessions](/docs/session-replay#view-the-number-of-captured-sessions).
- Replays with [processing errors](/docs/session-replay/session-replay-plugin#troubleshooting) don't cont toward your monthly quota. Replays that show a retention error message counted against the quota when it was still in the retention period.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kickerbear is this specifically "processing errors" or should we say "error messages"?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Processing errors seems okay to me, better than the more generic "error messages". The ones that don't count (under/over tagged) really these are issues related to instrumentation, so if we wanted to say something different I would say "instrumentation errors".

Co-authored-by: SpencerFleury <159941756+SpencerFleury@users.noreply.github.com>
Copy link

@kickerbear kickerbear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@markzegarelli markzegarelli merged commit a0b26f8 into main Sep 26, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants