From 614c25002cc18fba21bfdc7111c271729a079bbe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?C=C3=BCneyt=20=C5=9Eent=C3=BCrk?= <cneytsenturk@gmail.com>
Date: Thu, 23 Feb 2023 12:45:13 +0300
Subject: [PATCH] Sentry tracker added replay configuration..

---
 resources/assets/js/exceptions/trackers/sentry.js | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/resources/assets/js/exceptions/trackers/sentry.js b/resources/assets/js/exceptions/trackers/sentry.js
index 9ef760eea..6cb46ce4b 100644
--- a/resources/assets/js/exceptions/trackers/sentry.js
+++ b/resources/assets/js/exceptions/trackers/sentry.js
@@ -6,16 +6,27 @@ export default {
         Sentry.init({
             Vue,
             dsn: exception_tracker.action,
+
             logErrors: true,
+
             integrations: [
                 new BrowserTracing({
                     tracingOrigins: [],
                 }),
+                new Sentry.Replay()
             ],
             // Set tracesSampleRate to 1.0 to capture 100%
             // of transactions for performance monitoring.
             // We recommend adjusting this value in production
             tracesSampleRate: exception_tracker.params.traces_sample_rate,
+
+            // This sets the sample rate to be 10%. You may want this to be 100% while
+            // in development and sample at a lower rate in production
+            replaysSessionSampleRate: 0.1,
+
+            // If the entire session is not sampled, use the below sample rate to sample
+            // sessions when an error occurs.
+            replaysOnErrorSampleRate: 1.0,
         });
 
         Sentry.setUser({