Currently we are more focused on after the de

Question

< U02HK6286KV> Currently we are more focused on after the deployment use case where you need to monitor how your deployed apps are doing But you are right shouldn t be very difficult to get into the during development use case Curious what are the main use cases fo you use Sentry currently for

Uku Taht · Answer

I actually use Sentry in production that s where most of the value is Basically it gives me a list of all the errors that happened in prod in the last 14 days It has some pretty good logic to deduplicate errors into unique ones provide the stacktrace and enumerate all the times it has happened

Uku Taht · Answer

Here s a screenshot I check this page on a regular basis to see what errors have come up that I missed in unit tests

Uku Taht · Answer

It also notifies me via email when a new error pops up that has never been seen before

Uku Taht · Answer

IDK Maybe this is already built into Signoz Sorry I still haven t played with it I m imagining some sort of errors tab on the left that lists unique errors like this I understand that unique is pretty vague and there s a lot of technical detail on how they achieve this based on the language framework

Ankit Nayan · Answer

We planned to have this as separate menu item on left side as independent page These details seem interesting You want to add this at <https github com SigNoz signoz issues 101>

Ankit Nayan · Answer

Open Telemetry gives exceptions and stacktrace and m not sure of headers and userId like stuff

Ankit Nayan · Answer

shouldn t userId like params be masked off to honour privacy

Uku Taht · Answer

Maybe We pass the user id on with the exception it has helped me debug data issues multiple times Of course it increases the footprint of our data but I thought it was a worthwhile tradeoff

Ankit Nayan · Answer

hmmm got it