Sentry doesn't group exceptions correctly (React app)












1















We're using Raven & Sentry to track errors from React app
And each deploy produces new js bundle:




  • my_bundle.e1277d4630b7d8cbb771.js

  • my_bundle.844d5be4607494ae004f.js

  • ...


The same bundle can be served from different URL:




  • https://my_website.com/en/my_bundle.e1277d4630b7d8cbb771.js

  • https://my_website.com/fr/my_bundle.e1277d4630b7d8cbb771.js

  • ...


As a result when we have some error on js, with the same stack trace but from different bundles (releases) or from the same bundle but served from different URLs /en/my_bundle.e1277d4630b7d8cbb771.js | fr/my_bundle.e1277d4630b7d8cbb771.js
Sentry group them in a random way:
errors are grouped in some batches: so from 100 events of the same error, we have ~ 40 different issues in sentry.
For example, issues could be grouped in such a way:



First group:




  • /en/my_bundle.e1277d4630b7d8cbb771.js

  • /fr/my_bundle.e1277d4630b7d8cbb771.js

  • /de/my_bundle.844d5be4607494ae004f.js


Second group:




  • /de/my_bundle.e1277d4630b7d8cbb771.js

  • /fr/my_bundle.844d5be4607494ae004f.js


Is there a way to configure Sentry to group errors in the more intelligent way, to group error with same stack trace as one issue?



I've found an approach to normalize file name in Raven before sending data in Sentry:



https://gist.github.com/danharper/a89685cc1028759345b8



But it seems a bit overcomplicated, cause as I see Sentry trying to group error from different files by itself.






javascript reactjs sentry raven







share|improve this question



























    1















    We're using Raven & Sentry to track errors from React app
    And each deploy produces new js bundle:




    • my_bundle.e1277d4630b7d8cbb771.js

    • my_bundle.844d5be4607494ae004f.js

    • ...


    The same bundle can be served from different URL:




    • https://my_website.com/en/my_bundle.e1277d4630b7d8cbb771.js

    • https://my_website.com/fr/my_bundle.e1277d4630b7d8cbb771.js

    • ...


    As a result when we have some error on js, with the same stack trace but from different bundles (releases) or from the same bundle but served from different URLs /en/my_bundle.e1277d4630b7d8cbb771.js | fr/my_bundle.e1277d4630b7d8cbb771.js
    Sentry group them in a random way:
    errors are grouped in some batches: so from 100 events of the same error, we have ~ 40 different issues in sentry.
    For example, issues could be grouped in such a way:



    First group:




    • /en/my_bundle.e1277d4630b7d8cbb771.js

    • /fr/my_bundle.e1277d4630b7d8cbb771.js

    • /de/my_bundle.844d5be4607494ae004f.js


    Second group:




    • /de/my_bundle.e1277d4630b7d8cbb771.js

    • /fr/my_bundle.844d5be4607494ae004f.js


    Is there a way to configure Sentry to group errors in the more intelligent way, to group error with same stack trace as one issue?



    I've found an approach to normalize file name in Raven before sending data in Sentry:



    https://gist.github.com/danharper/a89685cc1028759345b8



    But it seems a bit overcomplicated, cause as I see Sentry trying to group error from different files by itself.






    javascript reactjs sentry raven







    share|improve this question

























      1












      1








      1








      We're using Raven & Sentry to track errors from React app
      And each deploy produces new js bundle:




      • my_bundle.e1277d4630b7d8cbb771.js

      • my_bundle.844d5be4607494ae004f.js

      • ...


      The same bundle can be served from different URL:




      • https://my_website.com/en/my_bundle.e1277d4630b7d8cbb771.js

      • https://my_website.com/fr/my_bundle.e1277d4630b7d8cbb771.js

      • ...


      As a result when we have some error on js, with the same stack trace but from different bundles (releases) or from the same bundle but served from different URLs /en/my_bundle.e1277d4630b7d8cbb771.js | fr/my_bundle.e1277d4630b7d8cbb771.js
      Sentry group them in a random way:
      errors are grouped in some batches: so from 100 events of the same error, we have ~ 40 different issues in sentry.
      For example, issues could be grouped in such a way:



      First group:




      • /en/my_bundle.e1277d4630b7d8cbb771.js

      • /fr/my_bundle.e1277d4630b7d8cbb771.js

      • /de/my_bundle.844d5be4607494ae004f.js


      Second group:




      • /de/my_bundle.e1277d4630b7d8cbb771.js

      • /fr/my_bundle.844d5be4607494ae004f.js


      Is there a way to configure Sentry to group errors in the more intelligent way, to group error with same stack trace as one issue?



      I've found an approach to normalize file name in Raven before sending data in Sentry:



      https://gist.github.com/danharper/a89685cc1028759345b8



      But it seems a bit overcomplicated, cause as I see Sentry trying to group error from different files by itself.






      javascript reactjs sentry raven







      share|improve this question














      We're using Raven & Sentry to track errors from React app
      And each deploy produces new js bundle:




      • my_bundle.e1277d4630b7d8cbb771.js

      • my_bundle.844d5be4607494ae004f.js

      • ...


      The same bundle can be served from different URL:




      • https://my_website.com/en/my_bundle.e1277d4630b7d8cbb771.js

      • https://my_website.com/fr/my_bundle.e1277d4630b7d8cbb771.js

      • ...


      As a result when we have some error on js, with the same stack trace but from different bundles (releases) or from the same bundle but served from different URLs /en/my_bundle.e1277d4630b7d8cbb771.js | fr/my_bundle.e1277d4630b7d8cbb771.js
      Sentry group them in a random way:
      errors are grouped in some batches: so from 100 events of the same error, we have ~ 40 different issues in sentry.
      For example, issues could be grouped in such a way:



      First group:




      • /en/my_bundle.e1277d4630b7d8cbb771.js

      • /fr/my_bundle.e1277d4630b7d8cbb771.js

      • /de/my_bundle.844d5be4607494ae004f.js


      Second group:




      • /de/my_bundle.e1277d4630b7d8cbb771.js

      • /fr/my_bundle.844d5be4607494ae004f.js


      Is there a way to configure Sentry to group errors in the more intelligent way, to group error with same stack trace as one issue?



      I've found an approach to normalize file name in Raven before sending data in Sentry:



      https://gist.github.com/danharper/a89685cc1028759345b8



      But it seems a bit overcomplicated, cause as I see Sentry trying to group error from different files by itself.






      javascript reactjs sentry raven




      javascript reactjs sentry raven






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 28 '18 at 18:38









      IgorIgor

      9510




      9510
























          0






          active

          oldest

          votes












          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53526011%2fsentry-doesnt-group-exceptions-correctly-react-app%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53526011%2fsentry-doesnt-group-exceptions-correctly-react-app%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          -

          Popular posts from this blog

          A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

          Image
          0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{
          Read more

          Calculate evaluation metrics using cross_val_predict sklearn

          Image
          1 In the sklearn.model_selection.cross_val_predict page it is stated: Generate cross-validated estimates for each input data point. It is not appropriate to pass these predictions into an evaluation metric. Can someone explain what does it mean? If this gives estimate of Y (y prediction) for every Y (true Y), why can't I calculate metrics such as RMSE or coefficient of determination using these results? python scikit-learn cross-validation share | improve this question edited Nov 28 '18 at 17:52 desertnaut 20.3k 7 43 79
          Read more

          Insert data from modal to MySQL (multiple modal on website)

          Image
          0 I have problem with inserting data to MySQL from modal. My modal: <a href="#" class="badge badge-pill badge-success">6 komentarzy</a> <a href="#" class="badge badge-pill badge-danger">brak komentarzy</a> <a data-toggle="modal" href="#add_desk_comm_{$desk_['desk_id']}" data-target="#add_desk_comm_{$desk_['desk_id']}" class="ediiit">(dodaj)</a> <div class="modal fade" id="add_desk_comm_{$desk_['desk_id']}" tabindex="-1" role="dialog" aria-labelledby="edit_printer" aria-hidden="true"> <div class="modal-dialog" role="document">
          Read more