The story of the introduction of [Sentry
- I put it on the client side this time, but I thought it would be better to put it on the server side as well.
- I realized I should send an additional dialogue ID, both server-side and client-side.
https://keicho.netlify.app/#talk=liJIAQmmJQIuUkKijd6d
What would you like to see happen in this conversation? I want to talk about the introduction of Sentry. What kind of āSentryā is this āSentryā? It is a function that tells the developer when an error occurs in the userās browser. What kind of āuserā is this āuserā? When the user is me and I am operating on a PC, I can see the error log without doing anything, but not at other times, so I needed a system like this. Is there anything else you can tell us about that āuserā? The system does not transmit the contents of errors when they occur, so the system itself has to have a function to tell the user. What kind of āerrorā is this āerrorā? For example, I recently added a function to resume the previous conversation, and Iām having a problem where the error does not occur on my development machine, but only on the userās machine where the āprevious conversationā does not exist. Is there anything else you can tell us about that āerrorā? It also records what kind of operation caused the error, so debugging progress can be made. Where is the āerrorā? In the hands of the user How do you know its āusersā? I donāt know who exactly the user is, but I do know the browser, OS, etc. Where is this āuserā located? So youāre so far away from me that I canāt observe you directly. What is it that you value? The idea is that detailed and prompt notification of errors that occur at a userās fingertips at a distance will make it easier to find and solve problems. How do you know its an āerrorā? You will be notified by e-mail.
-
Iām just saying that detailed and prompt notification of errors that occur at a userās fingertips at a distance will make it easier to find and solve problems.
- Where is this āerrorā? On the userās hand browser, oh, yes, we can have the same notification of errors on the server, so we should do that too. For the value of noticing quickly. What would you like to see happen with respect to that āerrorā? Hopefully this will be resolved quickly. What needs to happen to the āerrorā for that to happen? It would be nice to be notified with a set of information needed to resolve the issue. As for āerrors,ā can you do that? Itās unknown what would suffice as the required information. Those on the server would be better off sending the dialogue ID.
-
On the userās hand browser, oh, yes, we can have the same notification of errors on the server, so we should do that too. For the value of noticing quickly.
- Where do these āusersā come from? Iām not getting a specific user, so I guess Iād better send the dialogue ID in the client version. Where is this āuserā located?
This page is auto-translated from /nishio/Sentryćå°å „ćć話 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. Iām very happy to spread my thought to non-Japanese readers.