Hello, thanks for actually listening, I agree with what you said.
The never-ending problem when deploying a react product and customers start using it is that you don’t know what’s going on their side.
Microsoft Clarity gives me a visual idea of what’s going on but when it comes to errors I don’t have what I need to actually debug.
Honestly what I would expect is a full stacktrace the way the local environment would give it to me, not sure if it’s doable but I’m thinking out loud here.
Also if I could see all consoe.logs, it would help me with the exact thing that went wrong.
Usually when debugging together with a customer, you’d need to have the inspector open to see the network requests and the console logs to get a feel on where things stopped working.
So all of that bundled within the incident would make this a very helpful incident.
I won’t lie I think that’s what Sentry is doing - maybe - I haven’t used it extensively cause it costs too much.
Bronze Forest
•
Jul 30, 2024
Hey there! Thanks for the feedback. Wanted to follow up on this — what other context would be helpful here?
A couple contextual improvements that we’ve been considering:
Show number of times this issue occurred
Ability to see relevant source code
Timeline showing what led to this error
Would any of those improvements be useful to you here, and is there anything else that might be valuable to see?
Comments3
Azure Padlock
Jul 31, 2024
Hello, thanks for actually listening, I agree with what you said.
The never-ending problem when deploying a react product and customers start using it is that you don’t know what’s going on their side.
Microsoft Clarity gives me a visual idea of what’s going on but when it comes to errors I don’t have what I need to actually debug.
Honestly what I would expect is a full stacktrace the way the local environment would give it to me, not sure if it’s doable but I’m thinking out loud here.
Also if I could see all consoe.logs, it would help me with the exact thing that went wrong.
Usually when debugging together with a customer, you’d need to have the inspector open to see the network requests and the console logs to get a feel on where things stopped working.
So all of that bundled within the incident would make this a very helpful incident.
I won’t lie I think that’s what Sentry is doing - maybe - I haven’t used it extensively cause it costs too much.
Bronze Forest
Jul 30, 2024
Hey there! Thanks for the feedback. Wanted to follow up on this — what other context would be helpful here?
A couple contextual improvements that we’ve been considering:
Show number of times this issue occurred
Ability to see relevant source code
Timeline showing what led to this error
Would any of those improvements be useful to you here, and is there anything else that might be valuable to see?
Azure Padlock
Jul 30, 2024
Appreciate the feedback. Talking to team now