feat(extrapolation): add guidance on when to switch to sample mode in extrapolation docs

Author: shellmayr

develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx

@@ -72,6 +72,12 @@ In new product surfaces, the question of whether to use extrapolated vs. non-ext
 - Does the user care more about a truthful estimate of the aggregate data or about the actual events that happened?
     - 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:
+
+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 should educate users towards that they can increase the value they can get out of the product by increasing the sample rate. We should educate uesrs 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, so 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.
+
 ### 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.