From 35375064bd34f46cc4bef3cc443238c3359ddc3f Mon Sep 17 00:00:00 2001 From: Simon Hellmayr Date: Thu, 28 Nov 2024 11:18:39 +0100 Subject: [PATCH] simplify --- .../dynamic-sampling/extrapolation.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx b/develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx index d4c28c9b2ef0c..d9027465dcdc0 100644 --- a/develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx +++ b/develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx @@ -73,10 +73,10 @@ In new product surfaces, the question of whether to use extrapolated vs. non-ext - Some scenarios, like visualizing metrics over time, are based on aggregates, whereas a case of debugging a specific user's problem hinges on actually seeing the specific events. The best mode depends on the intended usage of the product. ### Switching to Sample Mode -Sample mode is generally to be preferred when the users are investigating specific events. There are primarily two cases when we should nudge users towards sample mode: +Sample mode is best for investigating specific events. Consider switching to it in two cases: -1. When the sample rate and the sample size are low, the extrapolation will be inaccurate and should not be used to draw conclusions. In this case, we should educate users that they can increase the value they can get out of the product by increasing the sample rate. We should also inform users that if they want to investigate individual events, they can switch to sample mode. -2. When the sample rate is high and sample size is low, the user cannot significantly increase the number of samples by increasing the sample rate, so nudging them in this direction will not help. We should refrain from littering the UI with banners. Here all we can do is to provide guidance about sample mode being more useful in this case. +1. When sample rate and size are low: Extrapolation becomes inaccurate here. We recommend either increasing the sample rate or switching to sample mode to examine individual events. +2. When sample rate is high but size remains low: Increasing the sample rate won't help get more data. In this case, sample mode may be the better choice for analysis. ### Opting Out of Extrapolation Users may want to opt out of extrapolation for different reasons. It is always possible to set the sample rate for specific events to 100% and therefore send all data to Sentry, implicitly opting out of extrapolation and behaving in the same way as sample mode. Depending on their configuration, users may need to change Dynamic Sampling settings or their SDK's traces sampler callback for this.